ci: pin Bun to 1.3.14 in CI#107
Merged
Merged
Conversation
setup-bun@v2 previously installed whatever Bun was latest, leaving the version unpinned and drifting between runs. Pin it explicitly to the current latest stable, 1.3.14.
PR #107: ci: pin Bun to 1.3.14 in CI1 files, +2 / -0 Scope✅ PR scope looks good. Structural✅ No structural bloat detected. Slop✅ Slop indicators look low. Static Analysis✅ Oxlint found no issues. Correctness✅ Small PR — correctness review skipped. |
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.
What
Pin Bun to
1.3.14(current latest stable) in thetest-bunCI job.Why
oven-sh/setup-bun@v2was used without abun-versioninput, so CI installed whatever Bun happened to be latest at run time. That left the version unpinned and free to drift between runs. Pinning makes CI reproducible.Change