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 Update the lockfile with the dependency bumps

In every GitHub Actions workflow that invokes .github/actions/setup-pnpm/action.yml, the action runs pnpm install; pnpm's CLI documents that frozen-lockfile is “on by default in CI environments.” The unchanged pnpm-lock.yaml still specifies js-yaml as ^4.1.1 and lodash-es as ^4.17.21, so a CI install exits with ERR_PNPM_OUTDATED_LOCKFILE for both mismatches before any checks or deployments can run. Regenerate and commit the lockfile alongside these manifest changes.

Useful? React with 👍 / 👎.

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