Releases: eemeli/yaml
v2.3.1
v2.3.0
This release corresponds with the release of yaml-types
v0.2.0, an expanding library of custom tags or types for use with yaml
.
This release contains no changes from v2.3.0-5, and the notes below include all changes from the v2.3.0-x prereleases.
Custom Tag Improvements
- Add export of
createNode()
&createPair()
to'yaml/util'
(#457) - Add static
from()
methods to simplify tag development, and otherwise make extending custom collections easier (#467)
TypeScript Improvements
- Add a second optional generic type argument
Strict
toDocument
instances. (#441) - Add types exports for TypeScript (#463)
- Export
StringifyContext
type from'yaml/util'
(#464)
Other New Features
- Add a
toJS(doc, options?)
method to nodes (#451, #458) - Set explicit tag during
createNode()
for non-default tags (#464)
Bugfixes
v2.3.0-5
v2.2.2
This patch release includes a fix for an error that could be thrown in parseDocument
for degenerate input. Otherwise, it's a patch release uplifting a few fixes from the ongoing v2.3 work to v2.2:
- Corner case failure in error pretty-printer (CVE-2023-2251)
- Use correct argument order when stringifying flow collection comments (#443)
- First-line folding for block scalars (#422)
v2.3.0-4
v2.3.0-3
v2.3.0-1
v2.3.0-0
This release is made available first as a prerelease to gauge the effects of the TypeScript changes, which add a second optional generic type argument Strict
to Document
instances. While this change appears to improve the TS usage experience at least with basic patterns, it's possible that it doesn't take into account some usage that would be negatively affected by the change.
Comments are requested, both for and against the change.
New Features
- Improve TS developer experience (#441)
Bugfixes
- Use correct argument order when stringifying flow collection comments (#443)