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.1",
"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 dependency upgrades

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. In GitHub Actions, .github/actions/setup-pnpm/action.yml runs pnpm install, and pnpm enables --frozen-lockfile by default in CI; running the frozen install against this manifest exits with ERR_PNPM_OUTDATED_LOCKFILE for both dependencies, so every workflow using this setup action fails before its actual job runs. Commit the lockfile generated from the upgraded manifest.

Useful? React with 👍 / 👎.

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