algo-builder
algo-builder copied to clipboard
chore(deps): bump yaml from 1.10.2 to 2.2.2
Bumps yaml from 1.10.2 to 2.2.2.
Release notes
Sourced from yaml's releases.
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:
- Use correct argument order when stringifying flow collection comments (#443)
- First-line folding for block scalars (#422)
- Corner case failure in error pretty-printer (CVE-2023-2251)
v2.2.1
- Quote top-level map keys containing document markers (#431)
v2.2.0
New Features
- Add
flowCollectionPadding
toString option (#420)- Use indicator line for props on block collection values of mappings (#425)
Bugfixes
- Minor relaxation of types for custom tags (#429)
v2.1.3
- Set correct node-end position for block collections with comments (#413)
v2.1.2
- Set correct node-end position for empty values with comments (#413)
v2.1.1
No changes in executable code, only TS types.
- Revert "Use TS named tuple for range (#385)" -- see #393
- Fix types for compatibility with TS 4.2 and 4.7
- Add CI workflow for testing published type in a range of TS versions
v2.1.0
Fixes for TypeScript users. Arguably this could've been a patch release as well.
- Improve/specify/fix TS types for Document & collection access methods (#383)
- Use TS named tuple for range (#385)
- Rename internal Document option as
_directives
to resolve type conflict with ToString options (#389)- Update tsc target to ES2020 to match Node.js support
- Update dev dependencies, including jest 28
v2.0.1
- Fix tags and anchors on map keys (#378)
v2.0.0
This update has been in the works for the last year and a half. Its prerelease versions have been thoroughly tested by a wide number of users, and I think it's finally ready for "actual" release, for use in the mythical "production".
The breaking changes introduced here are mostly originating from the v1 CST parser having become a rather difficult beast to work with. So it's here rewritten pretty much completely, now with a lexer as a first stage. Along the way, the whole project was rewritten in TypeScript and the export paths and options refactored pretty deeply.
... (truncated)
Commits
f21fa45
2.2.2984f578
fix: Corner case failure in error pretty-printer443e3aa
fix: First-line folding for block scalars (fixes #422)5af5d3d
fix: Use correct argument order when stringifying flow collection comments (f...c914dcc
2.2.1c8551eb
fix: Quote top-level map keys containing document markers (fixes #431)3576408
2.2.0ab52daa
ci: Remove all@types
except for node when testing types on old TS85be08d
chore: Explicitly set supported types in tsconfig.json4732502
ci: Uninstall@jest/types
before testing types on TS 4.2- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebase
will rebase this PR -
@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it -
@dependabot merge
will merge this PR after your CI passes on it -
@dependabot squash and merge
will squash and merge this PR after your CI passes on it -
@dependabot cancel merge
will cancel a previously requested merge and block automerging -
@dependabot reopen
will reopen this PR if it is closed -
@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.