Move the toolchain to bun 1.4, and cut 2.9.2 - #112
Merged
Conversation
setup-bun follows packageManager when no bun-version is given, so this one line is what moves CI, and it is the only thing that does. Bun 1.4 does not rewrite a v1 lockfile: a plain install and a frozen install both report no changes against the committed lock, so nothing here migrates to lockfileVersion 2 and older bun can still read it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Waterfalled rather than left for a follow-up pass: the SDK published minutes ago in this same sweep, so commerce lands on it now instead of shipping 2.9.2 against 2.7.4 and needing a second release to catch up. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Summary
Bumps
packageManagertobun@1.4.0and cuts 2.9.2.oven-sh/setup-bunfollowspackageManagerwhen nobun-versionis given, so this one line is what moves CI, and it is the only thing that does.Bun 1.4 does not rewrite a v1 lockfile: a plain install and a frozen install both report
no changesagainst the committed lock, so nothing migrates tolockfileVersion2 and older bun can still read it.Type of change
Public API
None. No exported type, signature, or wire format changed.
Test plan
Full gate set under bun 1.4.0:
lint,typecheck(both tsconfigs),test(1817 passed, 4 skipped),knip,build. No test changes, because no behavior changed.Dependency sweep for this repo, so a held version does not read as an oversight:
eslint/@eslint/js10 andtypescript7 are held majors in the registry. Not taken.viem2.55.19 andmppx0.8.18 are exact-pinned members of the coupled settle set. A move there owes the registry's standing all-rails live settle against a real storefront, so it gets its own pass rather than riding a toolchain bump.@agent-score/sdk2.7.6 is available and 2.7.7 is in flight in this same sweep. Taking it here would be churn; it comes in the second pass once the SDK publishes, which is the ordering the sweep runbook prescribes.Checklist