fix: sync bun.lockb after vitest 4.1.8 bump#71
Merged
Conversation
Dependabot PR #70 bumped vitest in package.json but, running in the npm_and_yarn ecosystem, never updated bun.lockb. The Docker build's `bun install --frozen-lockfile` then failed on main with "lockfile had changes, but lockfile is frozen", breaking the Azure deploy.
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.
Dependabot PR #70 bumped vitest in package.json but, running in the npm_and_yarn ecosystem, never updated bun.lockb. The Docker build's
bun install --frozen-lockfilethen failed on main with "lockfile had changes, but lockfile is frozen", breaking the Azure deploy.