Repository navigation
Release version 0.4.0-alpha - #248
Merged
Merged
Conversation
…lving the lockfile Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
update-version-minimal.sh missed the workspace manifests (which the release gate requires to equal the tag), the server start-up log, a second MCP contract test, the web .env example and the installer fallback, and only matched -alpha versions. It now edits manifests and their lockfile entries in place (npm version re-resolved the lockfile and dropped dev flags) and replaces every other recorded copy exactly; tests/toolchain/version-contract.mjs lists them all and fails CI if one is stale. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Set by scripts/update-version-minimal.sh 0.4.0-alpha: all manifests and their lockfile entries (version fields only), the web/MCP/server runtime versions, local image tags, installer fallback and README badge. Drop hard-coded version prose from the report footer and CLAUDE.md overview. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
🧪 Comprehensive Test Suite
Full-stack smoke gate runs in the CI workflow. |
1 similar comment
🧪 Comprehensive Test Suite
Full-stack smoke gate runs in the CI workflow. |
Member
Author
|
Maintainer verification of
Merging. |
This was referenced Nov 8, 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
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.
Prepares the first tag-gated release,
v0.4.0-alpha. The release workflow (#241) refuses a tag unless every workspace manifest carries the tag version.Version contract (new):
tests/toolchain/version-contract.mjslists every recorded copy of the version and fails if any differs from the rootpackage.json. It covers:package-lock.jsonentries;APP_VERSIONand.env.example;gd-core-*image tags;Negative control: bumping only the root version fails it.
Script fix:
scripts/update-version-minimal.shused to:-alphaversions.It now edits manifests and lockfile entries in place.
npm versionre-resolved the lockfile and droppeddevflags from three packages, so it isn't used. Every other copy gets an exact-string replacement, and the script runs the contract at the end. It validates its input and is idempotent.Bump:
0.3.1-alpha→0.4.0-alphaacross 19 files. The lockfile diff is exactly 6 version fields.Local, Node 22:
npm run build4/4;test:unified:lib289/289;tests/toolchain/*.mjs13/13;health-server.test.ts13/13.Next, after merge: promote
dev→mainwith a merge PR, letmainCI (including the production gate) pass, then tagv0.4.0-alphaon thatmainmerge commit.🤖 Generated with Claude Code