Repository navigation
chore: regenerate bun.lock for 1.17.18-1 - #62
Merged
Merged
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Jul 14, 2026
quickbeard
added a commit
that referenced
this pull request
Jul 15, 2026
The README's fork-only bump was four manual steps: a sed over every manifest, a bun install that's easy to forget (the mistake PR #62 had to fix), and a grep to verify. The sed was also GNU-only, so it silently failed on macOS. Add a fork-only script/bump-version.ts wrapping the same procedure behind `bun run bump [version]`. packages/opencode/package.json stays the single source of truth — the script reads the current version from it, so an upstream sync still just works. Packages on an independent version (codev-gateway) don't carry the shared value and are skipped without a hardcoded exclude list. Verified against PR #100: the script's output is byte-identical to the hand-done 1.17.18-2 → 1.17.18-3 bump. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
quickbeard
added a commit
that referenced
this pull request
Jul 15, 2026
The script runs bun install, so the step can no longer be skipped. The warning was aimed at the manual procedure it replaced; what's left is the live constraint (bun.lock records workspace versions, don't hand-edit it). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
quickbeard
added a commit
that referenced
this pull request
Jul 15, 2026
"records workspace versions" already says why the bun install is load-bearing; the PR number is provenance the reader doesn't need. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
quickbeard
added a commit
that referenced
this pull request
Jul 15, 2026
* chore: add a bump-version script and point the README at it The README's fork-only bump was four manual steps: a sed over every manifest, a bun install that's easy to forget (the mistake PR #62 had to fix), and a grep to verify. The sed was also GNU-only, so it silently failed on macOS. Add a fork-only script/bump-version.ts wrapping the same procedure behind `bun run bump [version]`. packages/opencode/package.json stays the single source of truth — the script reads the current version from it, so an upstream sync still just works. Packages on an independent version (codev-gateway) don't carry the shared value and are skipped without a hardcoded exclude list. Verified against PR #100: the script's output is byte-identical to the hand-done 1.17.18-2 → 1.17.18-3 bump. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs: use the bun bump shorthand `bun <script>` is the form the rest of the README already uses (bun dev, bun release, bun typecheck), so bun run bump was the odd one out. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs: drop the source-of-truth path from the README bump section The path was only there because the old step 1 was a manual grep of it. The script reads it now, so naming packages/opencode/package.json just sends the reader down a "why opencode?" detour to answer a question the bump workflow never raises. The fact still lives where it's load-bearing: script/bump-version.ts and release.ts. Keeps the lockstep note — that one is decision-relevant, since it's why a bump touches every manifest and moves bun.lock. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs: drop the PR #62 citation from the README bump section The script runs bun install, so the step can no longer be skipped. The warning was aimed at the manual procedure it replaced; what's left is the live constraint (bun.lock records workspace versions, don't hand-edit it). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * chore: drop the PR #62 citation from the bump script comment "records workspace versions" already says why the bun install is load-bearing; the PR number is provenance the reader doesn't need. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs: fix the explicit-target example contradicting the sync rule The example used 1.17.19 — the same value the bullet above cites as the plain upstream value that arrives via sync and must not be bumped by hand. Under a "for a fork-only bump" heading it demonstrated the one thing the section forbids. Use a suffixed target instead. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (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
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
main's version bump to1.17.18-1(chore: bump version to 1.17.18-1 #52) updated every workspacepackage.jsonbut notbun.lock; this regenerates the lockfile viabun install(per DIVERGENCES.md: never hand-merge it).🤖 Generated with Claude Code