Bumps yaml from 1.10.2 to 2.2.1.

Sourced from yaml's releases.

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.

If you've been using the library just via its parse(), parseDocument() and stringify() functions, then it's quite likely that none of the changes affect your experience in any way. However, if you've been doing something more involved, then I would strongly recommend that you review the library's documentation site for the v2 docs.

Going forward, it's finally time to start experimenting with new YAML spec features that may eventually be included in YAML 1.3 and later. Those will be made available by specifying the version: 'next' option. However, beware! Any features available this way may be removed or have their API broken by any minor release of this library, and no compatibility guarantees with other libraries are given. In general, semver compatibility is guaranteed for features that are explicitly included in the documentation; everything else should be considered as internal implementation details.

The following is an overview of the breaking changes and new features introduced in each of the prerelease steps leading up to this release; the individual releases' notes and the PRs will contain more detail, along with specific migration guides.

BREAKING CHANGES

... (truncated)

• c914dcc 2.2.1
• c8551eb fix: Quote top-level map keys containing document markers (fixes #431)
• 3576408 2.2.0
• ab52daa ci: Remove all @​types except for node when testing types on old TS
• 85be08d chore: Explicitly set supported types in tsconfig.json
• 4732502 ci: Uninstall @​jest/types before testing types on TS 4.2
• 8e134c7 chore: Update to rollup 3
• f72eee8 style: Apply updated Prettier styling
• e8ea440 chore: Refresh lockfile & update out-of-date type dependencies
• 97ec3e6 fix: Minor relaxation of types for custom tags (fixes #429)
• 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.

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)