Repository navigation
Keep runtime versions correct after version-only updates - #3
Merged
Merged
Conversation
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.
When a release changed only the package version or documentation, its built files retained the same hash. Restarting then reused the previous immutable runtime snapshot, including its old package version. Include package identity and version in the build hash so each release receives the correct snapshot while repeated builds of that release remain reusable.
The regression test builds identical application sources at two versions and checks that both immutable snapshots retain their own versions. It failed before the fix and now passes. All 128 tests, TypeScript/OXC checks, and the packaged CLI smoke test pass. Version 0.9.6 ships the fix through trusted publishing.
Note
Include package name and version in release hash to keep runtime versions correct after version-only updates
Fixes a bug where bumping the package version without changing source files produced the same release hash, so the wrong runtime snapshot was reused. The build release hash routine in build.ts now feeds the package name and version into the SHA-256 input alongside the generated CLI, server, and client artifacts. Adds an integration test in build-release.test.ts that builds two versions from identical source, confirms distinct build identifiers and runtime directories, and verifies that rebuilding the same version reuses its snapshot.
Macroscope summarized eb63eda.