Repository navigation
Add verified release workflow and RC packages - #3
Merged
Merged
Conversation
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
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.
Adds a dedicated release workflow triggered only by pushed version tags: stable tags (
vX.Y.Z) and release candidates (vX.Y.Z-rc.N). It runs its own validation, tests, build, and packaging, with no workflow_dispatch, workflow_call, or dependency on the CI workflow.The build job is read-only. Only the publishing job has
contents: write; it downloads the tested artifact and checks its SHA-256 checksum without checking out or executing repository code. Actions remain pinned to verified SHAs. Tag identity and package/manifest version mismatches fail before publication. RCs are marked as prereleases and do not replace the latest stable release.Supports the repository's enabled release immutability: create a draft, upload all assets, download and verify the uploaded ZIP against its checksum, then publish. Published tags and assets are never replaced; failures leave an unpublished draft and should be followed by a new RC. Future signatures must be attached before publication.
Chrome's built manifest retains a numeric
versionand receives the tag's display version throughversion_name. Packaging derives the ZIP filename from that metadata and produces a checksum file. The README documents tagging, checksum verification, and unpacked Chrome installation. Build and publish remain separate to support adding cosign signing in a future change; signing and OIDC permissions are not part of this PR.Updates Playwright to 1.65.0: the previous installer reproducibly stalled after downloading Chromium with Node 26; the current installer completes successfully and the six extension tests pass with Chromium 158.
Validation on Node 26.13.0: actionlint, ShellCheck, typecheck, formatting, 15 unit tests, Bash release validation/packaging tests, 6 real Chromium extension tests with the RC manifest, ZIP inspection, dependency audit (0 vulnerabilities), and checksum verification passed.