chore: update dependencies and bump pnpm to v11#14
Open
thelooter wants to merge 1 commit into
Open
Conversation
Bump vue, vitepress, and prettier to their latest patch/minor releases, and pnpm from 9.12.2 to 11.9.0. pnpm 11 requires Node.js 22+, so the CI build matrix drops Node 18/20 in favor of 22/lts/latest, and it blocks postinstall scripts by default, so pnpm-workspace.yaml now allowlists esbuild's build script. Also adds the missing engines.pnpm field that the CI workflow's version-detection step was silently failing to read.
Deploying docs with
|
| Latest commit: |
ab3cd5f
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://e73ea09a.docs-7os.pages.dev |
| Branch Preview URL: | https://chore-update-dependencies.docs-7os.pages.dev |
4everTheOne
approved these changes
Jul 1, 2026
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
2 participants
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
vue3.5.13 → 3.5.39,vitepress1.5.0 → 1.6.4,prettier3.4.2 → 3.9.4pnpm-workspace.yamlwithallowBuilds: { esbuild: true }, since pnpm 11 blocks postinstall scripts by defaultengines.pnpmfield topackage.json, which the CI workflow's version-detection step already referenced but which never actually existed (the step was silently writing an empty version and falling back to thepackageManagerfield)pnpm-lock.yamlandpackage-lock.jsonNotes
pnpm auditstill reports 7 vulnerabilities (2 high, 5 moderate) in vite/esbuild/rollup/postcss/mdast-util-to-hast, all transitive deps pinned by vitepress 1.6.4 (latest stable 1.x). The fixes only landed in vite 6.x, which vitepress 1.x doesn't support yet (VitePress 2.0 is still alpha, no GA timeline). No safe fix available until vitepress ships vite 6 support.Test plan
pnpm install --frozen-lockfilesucceedspnpm run docs:buildsucceedspnpm run docs:devserves the site (verified HTTP 200 on localhost)pnpm run lint:checkpasses