Fix: sync bun.lock to repair frozen-lockfile on main#188
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.
Summary
The squash-merge of #187 included
package.json(withreact-markdown+remark-gfm) but not thebun.locksync commit, leavingmaindesynced.bun install --frozen-lockfilenow fails on main (Lighthouse CI and any frozen-lockfile deploy step).This commits the regenerated
bun.lockso manifest and lockfile agree again.Test Plan
bun install --frozen-lockfile→ "no changes" (the exact CI check)bun.lockchangedNote: the
E2E Testscheck is failing on main independently of this (Playwright picks upbun:-scheme test files → "No tests found"); it has failed on #185/#186/#187 alike and is out of scope here.🤖 Generated with Claude Code