Sync STACK_VERSION with package.json for 0.2.0 - #9
Merged
Conversation
The version lives in two places and #8 only bumped one, so main shipped package.json at 0.2.0 with STACK_VERSION still reading 0.1.3. The export contract test asserts the two match and fails on main. It passed in the PR because the suite was run before the version bump and not again after it. Adds a comment on the constant so the next release does not repeat the sequence. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01H5K2AxX2QZ98JW1Exe5wup
ThreatCrush Security Scan0 finding(s) No findings. |
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.
The version lives in two places and #8 only bumped one, so
maincurrently haspackage.jsonat 0.2.0 withSTACK_VERSIONstill reading0.1.3. The export contract test asserts the two match, and it fails on main right now.It passed in #8 because the suite was run before the version bump and not again after it — my error. Added a comment on the constant so the next release does not repeat the sequence.
Blocks cutting 0.2.0.
Testing: 266/266 pass,
tsc --noEmitclean,tsupbuilds.🤖 Generated with Claude Code
https://claude.ai/code/session_01H5K2AxX2QZ98JW1Exe5wup