ci: workflow-driven CalVer release for the extension#17
Merged
Conversation
The release workflow now owns version assignment instead of verifying a hand-edited manifest version against the tag. It computes YYYY.M.D.<github.run_number>, patches extension/src/manifest.json in CI, builds, uploads to S3, and creates the GitHub Release itself — so every release gets a strictly-increasing version that Chrome's auto-update recognizes, with no manual version bump in the source tree. Adds scripts/cut-release.sh for dispatching the workflow from a clean main, and skills/agent-browser-shield-release/SKILL.md documenting the flow. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
This was referenced Jun 7, 2026
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
.github/workflows/release-extension.ymlfromrelease: published(build-on-tag) toworkflow_dispatch(workflow creates the release). CI computesversion = YYYY.M.D.${{ github.run_number }},jq-patchesextension/src/manifest.jsonin the runner, builds, uploads to S3, and callsgh release createitself.extension/src/manifest.jsonversion(0.1.0) is now a permanent dev placeholder for unpacked loads — CI overwrites it. No manual version bump is needed to cut a release.scripts/cut-release.shfor dispatching the workflow from a cleanmain(preflights gh auth, branch, dirty tree, sync with origin;--watchtails the run).skills/agent-browser-shield-release/SKILL.mdcovering the version format, the cut-release flow, and rollback (re-dispatch on an older SHA).Why CalVer + run_number
manifest.versionnumerically segment-by-segment with a 4-segment max.2026.6.1 > 2026.5.31and2026.5.30.43 > 2026.5.30.42both hold.github.run_numberis monotonic per-repo and never resets, so every release is guaranteed to look newer than the previous one — including multiple same-day releases.Test plan
scripts/cut-release.sh --watchfrom a cleanmainand confirm the workflow:YYYY.M.D.<run_number>and the matchingv…tag.extension/src/manifest.json(visible in the "Patch manifest version" step log via the trailingjq '{version, name}').s3://agent-browser-shield/${tag}/extension.zipands3://agent-browser-shield/latest/extension.zip.GITHUB_SHAwith the ZIP attached and auto-generated notes.manifest.jsonversionmatches the tag (minus thevprefix).chrome://extensionsand confirm the displayed version matches.scripts/cut-release.shimmediately and confirm the second release gets a higherrun_numbersegment, and Chrome treats it as an update.🤖 Generated with Claude Code