Preserve lock-resolved browser provenance in release archives - #2198
Merged
Conversation
…nt, test, and verify this browser-provenance repair. Chris Huber remains responsible for every line.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
package-lock.jsonwith npm-supportednpm-shrinkwrap.json, so release consumers retain the exact resolved dependency graphnpm ci, include lifecycle inputs, and emit browser provenance for the resolved Playwright/Chromium revision, platform/architecture, and dependency-manifest SHA-256Closes #2197. Related to #2185.
Verification
npm run test:playwright-browser-provenancenpm run test:browser-runner-templatenpm run test:editor-actionsnpm run test:editor-validate-blocksnpm run buildnpm run test:release-package-coveragenpm run checkreached the shared smoke suite and failed atcommand-registry-smoke:wordpress.collect-workload-result outputShape should mention outputSchema id. The failure is outside this patch; all focused contracts above passed.AI assistance: gpt-5.6-sol via OpenCode was used to diagnose, implement, test, and verify this browser-provenance repair. Chris Huber remains responsible for every line.