Skip to content
Closed
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 lockfile for the upgraded dependencies

The committed pnpm-lock.yaml still specifies js-yaml as ^4.1.1/4.1.1 and lodash-es as ^4.17.21/4.17.23, so it is out of sync with these manifest changes. Every checked workflow installs through .github/actions/setup-pnpm/action.yml:35, and pnpm documents that CI enables frozen-lockfile behavior and fails when the lockfile and manifest differ; reproducing that install reports ERR_PNPM_OUTDATED_LOCKFILE for both dependencies. Commit the regenerated pnpm-lock.yaml so PR checks and deployment/indexing workflows can install dependencies and the security upgrades are actually locked.

Useful? React with 👍 / 👎.

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