Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions package.json
Original file line number Diff line number Diff line change
Expand Up @@ -47,9 +47,9 @@
"algoliasearch": "^5.46.1",
"dotenv": "^17.2.3",
"gray-matter": "^4.0.3",
"js-yaml": "^4.1.1",
"js-yaml": "4.3.2",
"json-schema-merge-allof": "^0.8.1",
"lodash-es": "^4.17.21",
"lodash-es": "4.18.0",
Comment on lines +50 to +52

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Regenerate the pnpm lockfile for the upgraded dependencies

When any GitHub workflow reaches .github/actions/setup-pnpm/action.yml:33-35, its pnpm install runs in CI with the frozen-lockfile behavior enabled by default. The unchanged lockfile still specifies js-yaml as ^4.1.1 and lodash-es as ^4.17.21; validating this tree with pnpm install --frozen-lockfile reports ERR_PNPM_OUTDATED_LOCKFILE for both mismatches, so every workflow using this setup action fails before its actual checks or deployment can run.

Useful? React with 👍 / 👎.

"remove-markdown": "^0.6.2"
},
"devDependencies": {
Expand Down
Loading