feat: automate manifest version stamping for extension uploads#28
Merged
Conversation
Extracts manifest version stamping into a pure, testable function. Appends a CI build number as the 4th version segment so every Chrome Web Store upload has a unique, always-increasing version. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
build.mjs now appends BUILD_NUMBER env var as the 4th version segment to dist/manifest.json. Sets version_name for human-readable display. Local builds default to X.Y.Z.0. Uses --experimental-strip-types to import stamp-version.ts directly into the Node ESM build script without a separate compile step. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Every workflow that builds and uploads the extension now passes github.run_number as BUILD_NUMBER. Snapshot builds also set SNAPSHOT=true for version_name labeling. Direct node build.mjs calls updated with --experimental-strip-types to support the .ts import in build.mjs.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
stampVersionpure function that appends a CI build number as the 4th segment of the Chrome extension manifest version (MAJOR.MINOR.PATCH.BUILD)build.mjssodist/manifest.jsongets stamped at build time viaBUILD_NUMBERenv varrelease.yml,publish-extension.yml) to passgithub.run_numberasBUILD_NUMBERSNAPSHOT=truefor human-readableversion_namelabelingHow it works
0.1.0.00.1.0.<run_number>0.1.0-snapshot.<run_number>0.X.Y.<run_number>0.X.YThe source
manifest.jsonis never modified — onlydist/manifest.jsongets the stamped version. To bump the base version, manually editmanifest.json.Test plan
stampVersion(local dev, snapshot, release, boundary, NaN, negative)0.1.0.0BUILD_NUMBER=42 SNAPSHOT=trueproduces0.1.0.42+version_name🤖 Generated with Claude Code