Repository navigation
JWB-949: Compare update versions with Bun.semver and drop v1 execution config - #94
Merged
Merged
Conversation
…on configuration (JWB-949) The update check now orders versions with Bun.semver.order after strict SemVer validation. Version 1 execution-configuration snapshots are no longer resolved; reading one refuses with the run and the last release that reads it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… failing the tick (JWB-949) A version 1 snapshot on any run made lanes() throw, stopping every completion and launch. The refusal is now carried on that lane and reported as its failure only when completion needs the configuration. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
# Conflicts: # src/app/claim/release.ts # src/app/pickup/runtime.ts # test/configuration/schema.test.ts
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.
Summary
checkForUpdateorders versions withBun.semver.order; the strict SemVer regex stays only to reject malformed tags (Bun.semver is lenient, e.g. accepts1.0) and to read prerelease identifiers.executionTargetv1 branch, map-scoped pickable statuses, and v1-onlyprojectrenaming insavedT3Configuration.claim releasetakes the repository from the recorded v2 configuration instead of the planning receipt.Evidence
v1 ledger refusal: real CLI path
Ledger seeded with a run and a v1
execution_configurationsrow, thenbun src/main.ts runs export interlock-run:historical --state <ledger> --json:Before (858f3e1):
After (c7297b6):
Prerelease ordering
test/distribution/update.test.ts: "each prerelease in SemVer precedence order is offered the next one" walks the SemVer §11 chain (1.0.0-alpha<alpha.1<alpha.beta<beta<beta.2<beta.11<rc.1<1.0.0), and "a stable installation is never offered a prerelease of its own version".Checks at c7297b6
🤖 Generated with Claude Code