Skip to content

Commit a1bd23a

Browse files
committed
Restore docs workflow installs after adding the WebFetch dependency
The main branch push introduced a new root dependency for WebFetch fixes, but package-lock.json was not refreshed, so the docs workflow's npm ci step failed before it could even build VitePress. This syncs the lockfile, upgrades the docs workflow to Node 22 for the current parser dependency requirements, and includes package-lock.json in the workflow trigger set. Constraint: The docs pipeline uses npm ci, which requires package.json and package-lock.json to stay exactly in sync Rejected: Leave the workflow on Node 20 | continues to emit avoidable engine warnings for current docs parser dependencies Rejected: Switch docs workflow from npm ci to npm install | weakens reproducibility instead of fixing the lockfile contract Confidence: high Scope-risk: narrow Reversibility: clean Directive: Whenever root dependencies change, keep package-lock.json in the same commit so docs and other npm-based workflows remain green Tested: npm ci Not-tested: Remote GitHub Actions rerun after pushing this fix
1 parent 2239098 commit a1bd23a

2 files changed

Lines changed: 22 additions & 1 deletion

File tree

‎.github/workflows/deploy-docs.yml‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@ on:
66
paths:
77
- 'docs/**'
88
- 'package.json'
9+
- 'package-lock.json'
910
- '.github/workflows/deploy-docs.yml'
1011
workflow_dispatch:
1112

@@ -30,7 +31,7 @@ jobs:
3031
- name: Setup Node
3132
uses: actions/setup-node@v4
3233
with:
33-
node-version: 20
34+
node-version: 22
3435
cache: npm
3536

3637
- name: Setup Pages

‎package-lock.json‎

Lines changed: 20 additions & 0 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)