chore(deps): bump yaml from 2.0.1 to 2.1.1

[dependabot[bot]]

Bumps yaml from 2.0.1 to 2.1.1.

Release notes

Sourced from yaml's releases.

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

Commits

• 96c6993 2.1.1
• 3b35834 ci: Add separate workflow for TS tests
• 4ff5051 fix: NodeType<T> for older TS versions
• d63d48d ci: Add typescript test jobs for its older versions
• 7e9b489 chore: Fix types for TS 4.7
• 42e527a chore: Refresh lockfile
• 98a1d5e Revert "feat: Use TS named tuple for range (#385)"
• 5050494 docs: Document defaultStringType option more explicitly
• c80d4c2 2.1.0
• 102ecf1 chore: Update to jest 28
• 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)

[RobbieMcKinstry]

@t0yv0 and I looked at this on Friday. Newer versions of the YAML dependency use the "operation chaining" ? operator, which isn't supposed in Node 12 (it's added in Node 14). We could either:

1. transpile the YAML dependency with a shim for the operational chaining operator.
2. wait until we bump this action from Node 12 to Node 14. This is dependent on external factors, like how long we're expected to support Node 12 passed its EOL date.

[dependabot[bot]]

Superseded by #736.