Skip to content

Update dependency js-yaml@3 to v5 [SECURITY] - autoclosed #229

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
renovate wants to merge 1 commit into from
Closed

Update dependency js-yaml@3 to v5 [SECURITY] - autoclosed #229

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@
"minimatch@3": "^3.1.3",
"minimatch@9": "^9.0.7",
"rollup": "^4.59.0",
"js-yaml@3": "^3.15.0",
"js-yaml@3": "^5.0.0",

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 23, 2026

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 Keep read-yaml-file on compatible js-yaml

When the workspace/release tooling reaches @manypkg/get-packages, the lockfile still resolves read-yaml-file@1.1.0, but this override now replaces that package's js-yaml 3 dependency with 5.2.1. read-yaml-file@1.1.0 calls the removed yaml.safeLoad API, so pnpm changeset version/publish against this repo's pnpm-workspace.yaml will fail before reading package data. Please avoid the cross-major override here or upgrade the consumer to a read-yaml-file version that uses yaml.load.

Useful? React with 👍 / 👎.

"js-yaml@4": "^4.3.0",
"brace-expansion@1": "^1.1.16",
"brace-expansion@2": "^2.1.2",
Expand Down
39 changes: 10 additions & 29 deletions pnpm-lock.yaml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading