Repository navigation
chore: bump version to 1.18.2-1 - #114
Merged
Merged
Conversation
Fork-only re-release between upstream syncs: the first fork build of upstream 1.18.2. Produced with `bun bump`, so the manifests and the regenerated bun.lock land together. Co-Authored-By: Claude Fable 5 <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
Fork-only re-release between upstream syncs, per the README's Bumping the version: appends the revision suffix to the bare upstream version,
1.18.2→1.18.2-1(the first fork build of upstream 1.18.2).Produced with
bun bump— every workspace manifest updated in lockstep plus the regeneratedbun.lock; the script verified nothing was missed. NoDIVERGENCES.mdentry needed (theversionfield defers to upstream on sync). After merge, publish withbun release.🤖 Generated with Claude Code