fix: sync bun.lock for surface-render 0.3.0 release - #200
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.
The render-v0.3.0 release run failed at
bun install --frozen-lockfile(run 29555220054): #199 bumped surface-render's package.json to 0.3.0 but the committed bun.lock retained the 0.2.0 workspace entry, plus a pre-existing stale notes-ui→surface-client range (^0.3.3 vs ^0.3.4).Regenerated with plain
bun install. Three hunks, all expected:^0.2.0caret no longer matches the 0.3.0 workspace, so bun falls back to the registry. This is the intended caret gate (notes-ui opts into 0.3.0 deliberately, later) — flagged so nobody reads it as an accident.After merge: re-point render-v0.3.0 (never published, safe to move) and let the release run publish.
🤖 Generated with Claude Code
https://claude.ai/code/session_01XLZtmuSs1RirWGMGyCB1QB