chore: repair pnpm lockfile and pin prettier 3.9.6 - #2040
Open
Swamp-Ig wants to merge 2 commits into
Open
Conversation
Remove the duplicate @vuepress/helper snapshot that broke --frozen-lockfile, bump prettier to the 3.9.x CI was already resolving under ^3.8.1, freeze installs in workflows, and pin format-docs to the same prettier version. Closes zachowj#2036
There was a problem hiding this comment.
Pull request overview
This PR restores deterministic dependency installs by repairing a broken pnpm-lock.yaml (duplicate snapshot key) and then tightening the repo’s tooling/CI to rely on the lockfile via pnpm install --frozen-lockfile. It also updates and consistently pins Prettier to 3.9.6 across dependencies and docs-formatting automation.
Changes:
- Fix
pnpm-lock.yamlvalidity by removing the duplicated@vuepress/helper@2.0.0-rc.122(...)snapshot mapping key. - Bump
prettierto^3.9.6(and lockfile to3.9.6) so dev tooling resolves consistently. - Update GitHub Actions workflows to use
pnpm install --frozen-lockfile, and pin the docs formatting action to Prettier3.9.6.
Reviewed changes
Copilot reviewed 5 out of 6 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
pnpm-lock.yaml |
Removes the duplicated snapshot entry and updates Prettier-related lock entries to 3.9.6, enabling frozen-lockfile installs. |
package.json |
Updates the dev dependency range for prettier to ^3.9.6. |
.github/workflows/ci.yml |
Switches CI installs to pnpm install --frozen-lockfile to catch lockfile drift/breakage. |
.github/workflows/documentation.yml |
Uses frozen-lockfile install for docs builds to ensure reproducible dependency resolution. |
.github/workflows/publish.yml |
Uses frozen-lockfile install during publish workflow to ensure published builds match the committed lock. |
.github/workflows/format-docs.yml |
Pins creyD/prettier_action to Prettier 3.9.6 to avoid formatting drift from latest. |
Files not reviewed (1)
- pnpm-lock.yaml: Generated file
This was referenced Jul 30, 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
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
pnpm-lock.yamlby removing the duplicate@vuepress/helper@2.0.0-rc.122(…)snapshot key sopnpm install --frozen-lockfileworks again (fixes pnpm-lock.yaml has duplicate key; --frozen-lockfile fails #2036).prettierto^3.9.6/ lock3.9.6— matching what CI was already resolving under the old^3.8.1caret while the broken lockfile was ignored. No source reformat needed; current tree already matches 3.9.x.pnpm install --frozen-lockfile.format-docscreyD/prettier_actiontoprettier_version: 3.9.6so docs formatting stops floating onlatest.Stacking note
This is a base piece of upcoming entity-availability work (paired contrib + companion PRs, not opened yet). It pairs with the version-handshake split-off in #2039.
#2040 and #2039 are independent in substance (lockfile/CI vs handshake) and can be merged in either order. If they land out of the order a branch currently assumes, the remaining open PR(s) just need a clean rebase onto
main(no conflict expected — disjoint files).Fine to skip these intermediates and merge the eventual availability PR instead: that branch will carry both of these commits (plus the availability work), so merging availability alone is enough if preferred.
Test plan
pnpm install --frozen-lockfilesucceedspnpm run lintcleanpnpm testgreen (515 passed)