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.1",
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 Update the pnpm lockfile alongside the dependency versions

The committed pnpm-lock.yaml still specifies js-yaml: ^4.1.1 and lodash-es: ^4.17.21, resolving to 4.1.1 and 4.17.23 respectively, so it is out of sync with both new exact versions. The shared setup action (.github/actions/setup-pnpm/action.yml:33–35) runs pnpm install, and the pnpm documentation states that frozen-lockfile mode defaults to true in CI and “fails to install if the lockfile is out of sync with the manifest”. Consequently, the inspected PR-check and deployment workflows that use this action will fail during dependency installation before reaching their checks or generation steps. Regenerate and commit the lockfile with these upgrades.

Useful? React with 👍 / 👎.

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