Skip to content

fix: upgrade yaml to ^2.8.3 to fix security vulnerability (#44) - #46

Merged
jzhang026 merged 1 commit into
tiktok:mainfrom
faizanongit:fix/update-yaml-security-vulnerability
Jul 1, 2026
Merged

fix: upgrade yaml to ^2.8.3 to fix security vulnerability (#44)#46
jzhang026 merged 1 commit into
tiktok:mainfrom
faizanongit:fix/update-yaml-security-vulnerability

Conversation

@faizanongit

Copy link
Copy Markdown
Contributor

This commit upgrades the yaml dependency from version 2.4.1 (pinned) to ^2.8.3 (using semantic versioning).

The old version 2.4.1 is vulnerable to Stack Overflow via deeply nested YAML collections (GHSA-48c2-rrv3-qjmp). The upgrade to 2.8.3 or later patches this vulnerability.

Changes:

  • Updated yaml dependency in packages/pnpm-sync-lib/package.json from '2.4.1' to '^2.8.3'
  • Bumped version to 0.3.4 in both packages/pnpm-sync-lib and packages/pnpm-sync (patch release)
  • Using semantic versioning (^) to allow for future patch and minor version updates
  • Updated pnpm-lock.yaml to reflect the new dependency version

Fixes: #44

@cla-assistant

cla-assistant Bot commented Jun 29, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

This commit upgrades the yaml dependency from version 2.4.1 (pinned) to ^2.8.3 (using semantic versioning).

The old version 2.4.1 is vulnerable to Stack Overflow via deeply nested YAML collections (GHSA-48c2-rrv3-qjmp). The upgrade to 2.8.3 or later patches this vulnerability.

Changes:
- Updated yaml dependency in packages/pnpm-sync-lib/package.json from '2.4.1' to '^2.8.3'
- Bumped version to 0.3.4 in both packages/pnpm-sync-lib and packages/pnpm-sync (patch release)
- Using semantic versioning (^) to allow for future patch and minor version updates
- Updated pnpm-lock.yaml to reflect the new dependency version

Fixes: tiktok#44

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@jzhang026
jzhang026 merged commit f0c4982 into tiktok:main Jul 1, 2026
2 checks passed
@faizanongit

Copy link
Copy Markdown
Contributor Author

@jzhang026 Looks like the publish failed. Do you already know the cause?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

This library is pinning an old version of yaml which now has a security issue

2 participants