Repository navigation
chore: bump Vite+ to 1.5.0 and keep the lock on version bumps - #19
Conversation
The catalog moves vite-plus and its vite core alias to 1.5.0, with the matching vitest and coverage line at 5.1.0. setup-vp moves to v1.22.0; it auto-detects the catalog entry, so CI installs the same 1.5.0 the workspace pins. Bun stays at 1.4.4, already latest. The version script also stops deleting bun.lock before reinstalling. On a full re-resolution the graph hoists @emnapi/runtime@2.0.0-beta.2 from @rolldown/binding-wasm32-wasi above @astrojs/astro2tsx, whose pinned @emnapi/core@1.11.3 has no bridge.setLastError, so `blume check` crashes and the required Docs site check fails on the Version PR. A plain `bun install` after `changeset version` still refreshes the workspace versions that the frozen install verifies, without re-resolving the graph.
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
|
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes
Reviewed the Vite+ 1.5.0 bump and the version script fix in this run.
- Toolchain bump to Vite+ 1.5.0: catalog entries for
vite-plus,vite,vitest, and@vitest/coverage-v8move to the 1.5.0 / 5.1.0 line, with the lockfile carrying the matching transitive bumps (oxlint,oxfmt,vitestfamily, platform bindings). - CI setup action to v1.22.0:
setup-vpmoves from v1.21.2 to v1.22.0, keeping CI and local runs on the same binary per the PR description. versionscript keeps the lock: dropsrm -f bun.locksochangeset versionis followed by a plainbun install, avoiding the full re-resolution that hoisted@emnapi/runtimeand brokeblume check.
The lockfile diff is consistent with the catalog (no version skew), and the version script change is the safer default: a plain install still records the workspace version bumps while leaving unrelated transitive pins stable.
muse-spark-1.3-contributor | 𝕏

Bumps the workspace to the published Vite+ 1.5.0 line:
vite-plusand itsvitecore alias to 1.5.0,vitestand@vitest/coverage-v8to 5.1.0.setup-vpmoves to v1.22.0, which resolves the version from the catalog, so CI and local runs use the same binary. Bun is already on 1.4.4, the latest release.The
versionscript no longer deletesbun.lockbefore reinstalling. A full re-resolution hoists@emnapi/runtime@2.0.0-beta.2from@rolldown/binding-wasm32-wasiabove@astrojs/astro2tsx, whose pinned@emnapi/core@1.11.3has nobridge.setLastError, soblume checkcrashes and the required Docs site check fails on the Version PR (reproduced locally afterchangeset version). A plainbun installstill refreshes the workspace versions that the frozen install verifies, and the Version flow then touches only 3 lines of the lock.Verified:
bun run check, 901 tests,bun run pack, the docs typecheck, and a fullbun run versionrehearsal in a worktree withbun install --frozen-lockfileandblume checkgreen.Summary by CodeRabbit


Confidence Score: 5/5
This PR appears safe to merge; no actionable issues were found.Summary
Updates Vite+ and keeps the existing dependency lock during version bumps.
Reviews (1) · Last reviewed commit: "chore: bump Vite+ to 1.5.0 and keep the ..." · Reviewed by Greptile