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.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 both dependency versions

The committed pnpm-lock.yaml still specifies js-yaml: ^4.1.1 and lodash-es: ^4.17.21, so it no longer matches this manifest. The PR checks in .github/workflows/pr-checks.yml use .github/actions/setup-pnpm/action.yml, whose dependency-install step runs pnpm install without overriding frozen-lockfile behavior. The pnpm documentation states that this setting is enabled by default in CI and installation “fails to install if the lockfile is out of sync with the manifest”. Consequently, these checks and the other workflows sharing that action stop at dependency installation. Regenerate and commit the lockfile with both upgrades.

Useful? React with 👍 / 👎.

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