[Snyk] Upgrade yaml from 2.6.1 to 2.8.1
Snyk has created this PR to upgrade yaml from 2.6.1 to 2.8.1.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
-
The recommended version is 4 versions ahead of your current version.
-
The recommended version was released 3 months ago.
Release notes
Package name: yaml
-
2.8.1 - 2025-08-05
- Preserve empty block literals (#634)
-
2.8.0 - 2025-05-15
- Add node cache for faster alias resolution (#612)
- Re-introduce compatibility with Node.js 14.6 (#614)
- Add
--mergeoption to CLI tool (#611) - Improve error for tag resolution error on null value (#616)
- Allow empty string as plain scalar representation, for failsafe schema (#616)
- docs: include cli example (#617)
- 2.7.1 - 2025-03-29
-
2.7.0 - 2024-12-31
The library is now available on JSR as @ eemeli/yaml and on deno.land/x as yaml. In addition to Node.js and browsers, it should work in Deno, Bun, and Cloudflare Workers.
-
2.6.1 - 2024-11-19
- Do not strip
:00seconds from!!timestampvalues (#578, with thanks to @ qraynaud) - Tighten regexp for JSON
!!bool(#587, with thanks to @ vra5107) - Default to literal block scalar if folded would overflow (#585)
- Do not strip
[!IMPORTANT]
- Check the changes in this PR to ensure they won't cause issues with your project.
- This PR was automatically created by Snyk using the credentials of a real user.
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
Summary by cubic
Upgraded yaml from 2.6.1 to 2.8.1 in packages/config-yaml to get parser fixes and faster alias resolution. No breaking changes expected; Node 14.6+ is supported.
-
Dependencies
- yaml: ^2.6.1 → ^2.8.1
Written for commit 20bce647850bef011ed09b66b58233bd1a735d7a. Summary will update automatically on new commits.
⚠️ PR Title Format
Your PR title doesn't follow the conventional commit format, but this won't block your PR from being merged. We recommend using this format for better project organization.
Expected Format:
<type>[optional scope]: <description>
Examples:
-
feat: add changelog generation support -
fix: resolve login redirect issue -
docs: update README with new instructions -
chore: update dependencies
Valid Types:
feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert
This helps with:
- 📝 Automatic changelog generation
- 🚀 Automated semantic versioning
- 📊 Better project history tracking
This is a non-blocking warning - your PR can still be merged without fixing this.
✅ Review Complete
Code Review Summary
⚠️ Continue configuration error. Please verify that the assistant exists in Continue Hub.
https://github.com/continuedev/continue/pull/8776