🤖 fix: pin Bun and freeze installs to avoid lock churn#3072
Merged
Conversation
Pin Bun 1.3.5 in the repo package manifests, align the remaining GitHub Actions jobs to that same version, and switch the local/workflow install entrypoints that were mutating lockfiles to use --frozen-lockfile instead. This makes lock drift fail fast instead of silently rewriting bun.lock during validation or publish automation. --- _Generated with `mux` • Model: `openai:gpt-5.4` • Thinking: `xhigh` • Cost: `$2.29`_ <!-- mux-attribution: model=openai:gpt-5.4 thinking=xhigh costs=2.29 -->
Collaborator
Author
|
@codex review |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
|
Codex Review: Didn't find any major issues. Breezy! ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
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
2 participants
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
Pin Bun 1.3.5 in the repo manifests and switch the install entrypoints that previously rewrote lockfiles to
--frozen-lockfile. This makes Bun version expectations explicit across the main app, mobile app, and chat-components package while stopping local validation and publish automation from silently mutatingbun.lock.Background
This repo already pins Bun 1.3.5 in the main CI setup action, but several other entrypoints were still effectively unpinned or running mutable installs. That let validation on machines with a different Bun setup rewrite lockfiles even when no dependency change was intended.
Implementation
packageManager: "bun@1.3.5"to the root, mobile, and chat-components manifestsbun install --frozen-lockfilebun install --frozen-lockfileValidation
make static-checkcd mobile && bun install --frozen-lockfilecd packages/chat-components && bun install --frozen-lockfilemake lint-actionsRisks
Low. The main behavior change is that Bun version mismatches or stale lockfiles now fail fast instead of being normalized implicitly during install.
Generated with
mux• Model:openai:gpt-5.4• Thinking:xhigh• Cost:$2.29