yaml
2.9.1 · 11 Sep 2026ISC330.2M / weekRepositoryHomepagenpmAtom feed
Upgrading yaml From 2.3.1 to 2.8.3
19 releases in betweenevery note read
Before you upgrade
Tick each one off as you go- Breaking2.7.0
Security
Fixes 1 advisory affecting 2.3.1
- yaml is vulnerable to Stack Overflow via deeply nested YAML collectionsmoderate · GHSA-48c2-rrv3-qjmp
Release by release
- New
Add
trailingCommaToString option for multiline flow formatting
- New
- Fixed
Do not double newlines for empty map values
- Fixed
2.8.1nothing new or fixed in the note
- New
Add node cache for faster alias resolution
- New
Add
--mergeoption to CLI tool - New
Allow empty string as plain scalar representation, for failsafe schema
- New
- Fixed
Do not allow seq with single-line collection value on same line with map key
- Fixed
- Breaking
Require Node.js 14.18 or later (was 14.6)
- Breaking
- Fixed
Do not strip
:00seconds from!!timestampvalues (#578, with thanks to @qraynaud)
- Fixed
27 other lines we could not sort, mostly version bumps
- 2.8.3
Catch stack overflow during node composition
- 2.8.2
Serialize -0 as -0
- 2.8.1
Preserve empty block literals
- 2.8.0
Re-introduce compatibility with Node.js 14.6
- 2.8.0
Improve error for tag resolution error on null value
- 2.7.1
Improve warning & avoid TypeError on bad YAML 1.1 nodes
- 2.7.0
Use .ts extension in all relative imports
- 2.7.0
Ignore newline after block seq indicator as space before value
- 2.6.1
Tighten regexp for JSON
!!bool(#587, with thanks to @vra5107) - 2.6.1
Default to literal block scalar if folded would overflow
2 internal lines (docs, tests, tooling) left out.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.