Repository navigation
build(repo): move to bun 1.4.2 - #51
Merged
Merged
Conversation
Pin packageManager, the four setup-bun steps and the CONTRIBUTING requirement to 1.4.2. bun 1.4.2 reads and keeps the v1 text lockfile; the only lockfile change is the workspace version fields it syncs from package.json, with no resolution change.
6 of 7 tasks
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
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
Move the repo from bun 1.3.14 to 1.4.2, the version showcase-kit already pins and the current release.
packageManager: bun@1.4.2, the foursetup-bunsteps (ci.ymltwice,docs.yml,release.yml) and the requirement inCONTRIBUTING.md.bun.lockstays atlockfileVersion: 1. bun 1.4.2 reads and keeps a v1 lockfile; only deleting it and regenerating writes v2, which here would move 87 resolutions (astro, rolldown, rollup and more). That is a dependency update, not a toolchain bump, so it is left out.versionfields that bun 1.4.2 syncs from each package'spackage.json, which were stale after the last release. No resolution changes.Test plan
rm -rf node_modules && bun install --frozen-lockfilewith bun 1.4.2: clean, no changesbun run build,bun run typecheck,bun run test(ESLint 10 and 9),bun run docs:build,bun run --cwd site testbun run docs:readmesleaves the tree unchangedbun-version