Skip to content

Commit

Permalink
chore(deps): bump yaml from 2.1.3 to 2.2.2 (#255)
Browse files Browse the repository at this point in the history
Bumps [yaml](https://github.com/eemeli/yaml) from 2.1.3 to 2.2.2.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/eemeli/yaml/releases">yaml's
releases</a>.</em></p>
<blockquote>
<h2>v2.2.2</h2>
<p>This patch release includes a fix for an error that could be thrown
in <code>parseDocument</code> for degenerate input. Otherwise, it's a
patch release uplifting a few fixes from the ongoing v2.3 work to
v2.2:</p>
<ul>
<li>Corner case failure in error pretty-printer (<a
href="https://github.com/advisories/GHSA-f9xv-q969-pqx4">CVE-2023-2251</a>)</li>
<li>Use correct argument order when stringifying flow collection
comments (<a
href="https://redirect.github.com/eemeli/yaml/issues/443">#443</a>)</li>
<li>First-line folding for block scalars (<a
href="https://redirect.github.com/eemeli/yaml/issues/422">#422</a>)</li>
</ul>
<h2>v2.2.1</h2>
<ul>
<li>Quote top-level map keys containing document markers (<a
href="https://redirect.github.com/eemeli/yaml/issues/431">#431</a>)</li>
</ul>
<h2>v2.2.0</h2>
<h3>New Features</h3>
<ul>
<li>Add <code>flowCollectionPadding</code> toString option (<a
href="https://redirect.github.com/eemeli/yaml/issues/420">#420</a>)</li>
<li>Use indicator line for props on block collection values of mappings
(<a
href="https://redirect.github.com/eemeli/yaml/issues/425">#425</a>)</li>
</ul>
<h3>Bugfixes</h3>
<ul>
<li>Minor relaxation of types for custom tags (<a
href="https://redirect.github.com/eemeli/yaml/issues/429">#429</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/eemeli/yaml/commit/f21fa455b8bb08aa3b20f07968aa923544635c2d"><code>f21fa45</code></a>
2.2.2</li>
<li><a
href="https://github.com/eemeli/yaml/commit/984f5781ffd807e58cad3b5c8da1f940dab75fba"><code>984f578</code></a>
fix: Corner case failure in error pretty-printer</li>
<li><a
href="https://github.com/eemeli/yaml/commit/443e3aa2acfb1951e6032a6c11798f861859b003"><code>443e3aa</code></a>
fix: First-line folding for block scalars (fixes <a
href="https://redirect.github.com/eemeli/yaml/issues/422">#422</a>)</li>
<li><a
href="https://github.com/eemeli/yaml/commit/5af5d3da01c55ecbadd596babab70fa9db9e47ee"><code>5af5d3d</code></a>
fix: Use correct argument order when stringifying flow collection
comments (f...</li>
<li><a
href="https://github.com/eemeli/yaml/commit/c914dcc9dd19c9c4da065fbbc4c920f244304dec"><code>c914dcc</code></a>
2.2.1</li>
<li><a
href="https://github.com/eemeli/yaml/commit/c8551ebca947c0fcd7a5cbd5b7b2636d4bd6925c"><code>c8551eb</code></a>
fix: Quote top-level map keys containing document markers (fixes <a
href="https://redirect.github.com/eemeli/yaml/issues/431">#431</a>)</li>
<li><a
href="https://github.com/eemeli/yaml/commit/35764085bec81eb075ad16241508de0934ec3477"><code>3576408</code></a>
2.2.0</li>
<li><a
href="https://github.com/eemeli/yaml/commit/ab52daa0a56fbafc5a332980b50631f991be3523"><code>ab52daa</code></a>
ci: Remove all <a
href="https://github.com/types"><code>@​types</code></a> except for node
when testing types on old TS</li>
<li><a
href="https://github.com/eemeli/yaml/commit/85be08de5d255e855e5bc9871532ad270e9b5456"><code>85be08d</code></a>
chore: Explicitly set supported types in tsconfig.json</li>
<li><a
href="https://github.com/eemeli/yaml/commit/4732502dc2a6d395665b6014eadce66ccd0da041"><code>4732502</code></a>
ci: Uninstall <code>@​jest/types</code> before testing types on TS
4.2</li>
<li>Additional commits viewable in <a
href="https://github.com/eemeli/yaml/compare/v2.1.3...v2.2.2">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=yaml&package-manager=npm_and_yarn&previous-version=2.1.3&new-version=2.2.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

You can trigger a rebase of this PR by commenting `@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

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](https://github.com/google-github-actions/get-secretmanager-secrets/network/alerts).

</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
  • Loading branch information
dependabot[bot] committed May 3, 2023
1 parent bcc64de commit 5d3a169
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

0 comments on commit 5d3a169

Please sign in to comment.