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 pnpm lockfile

These manifest changes leave pnpm-lock.yaml declaring the old ^4.1.1 and ^4.17.21 specifiers and resolutions. Every checked workflow installs through .github/actions/setup-pnpm/action.yml, whose line 35 runs pnpm install; in CI, pnpm enables frozen-lockfile behavior by default when a lockfile is present and fails when it is out of sync with the manifest (pnpm install documentation). Consequently, the PR checks and deployment/indexing workflows will fail during dependency installation until the lockfile is regenerated and committed.

Useful? React with 👍 / 👎.

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