fix: pin ghostty-web SHA in opencode build to preserve frozen-lockfile#1458
Merged
Conversation
abcxff
added a commit
that referenced
this pull request
Jun 3, 2026
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
pnpm buildfails on@rivet-dev/agent-os-opencodewitherror: lockfile had changes, but lockfile is frozenfrombun install --frozen-lockfile.packages/app/package.json(in the v1.3.13 source tarball) pins"ghostty-web": "github:anomalyco/ghostty-web#main"— a moving branch ref — while the bundledbun.locksnapshots commit4af877d. Oncemainadvances (currently20bd361), frozen-lockfile install can no longer satisfy resolution.bun install, rewrite theghostty-webref inpackages/app/package.jsonto the SHA the lockfile already records (4af877d).--frozen-lockfileis preserved, so any drift on either side still fails loudly — we're not silently absorbing whatever new HEADmainadvances to (which would be a supply-chain footgun if that branch were force-pushed or compromised).