chore(release): 1.6.3 - #214
Merged
Merged
Conversation
Patch release over v1.6.2, carrying the one unreleased fix on main: - fix(schema): restore application name alongside canonical id (#213) Bumps package.json and ANALYZER_VERSION in lockstep — the release workflow fails fast when the tag version and package.json disagree, and ANALYZER_VERSION is stamped into the cache so an upgrade invalidates stale per-file Modules. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01ERd8HAa8fbyX7YUfauwUyn
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
2 participants
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.
Version bump for the v1.6.3 patch release. Merge this, and the
v1.6.3tag goes on the resultingmainHEAD.What ships
One unreleased commit sits on
mainabovev1.6.2(900d01c):125fa69— fix(schema): restore application name alongside canonical id (fix(schema): Restore TypeScript application name #213)A schema-output fix with no contract move, so a patch bump is the right increment.
The change
Two files, because the version lives in exactly two places:
package.jsonpackage.json— the guard that catches a tag/bump mismatch before anything is published.src/utils/version.ts(ANALYZER_VERSION)analyzer.versionon the wire envelope and into the cache, so upgrading invalidates per-file Modules whose extracted shape may differ across analyzer versions.The PyPI wheel version needs no edit —
build_wheels.shstamps__init__.py's__version__fromPKG_VERSION, which the workflow derives from the tag.Verification
bun run typecheck— clean.bun test— 375 pass, 8 skip, 0 fail (this is the same gate the release workflow runs; a red run there deletes the tag).bun run gen:schemaandbun run gen:readmeproduce no diff, so the workflow's pre-release doc sync will be a no-op rather than a push tomain.