fix: drop --frozen-lockfile from CI (bun cross-platform drift)#38
Merged
Conversation
…e drift After npm→bun migration, lockfile generated on macOS differs slightly on Linux runners causing frozen-lockfile check to fail on every CI run. Co-Authored-By: Claude Sonnet 4.6 <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
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
--frozen-lockfilefrombuild-check.ymlandmain-release.ymlRoot Cause
bun install --frozen-lockfileerrors with "lockfile had changes, but lockfile is frozen" on every run since the migration commit (44110bc). Bun resolves optional/platform-specific deps differently between macOS and Linux, producing a slightly differentbun.lock.Fix
Drop
--frozen-lockfile— Bun will still install from the committed lockfile as a baseline and won't fail CI for minor platform differences.Test plan
🤖 Generated with Claude Code