[Snyk] Upgrade yaml from 1.10.2 to 2.4.5

[WontonSam]

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade yaml from 1.10.2 to 2.4.5.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

⚠️ Warning: This PR contains major version upgrade(s), and may be a breaking change.

• The recommended version is 38 versions ahead of your current version.

• The recommended version was released on a month ago.

Release notes

Package name: yaml

• 2.4.5 - 2024-06-08
  
  • Improve tab handling (#553, yaml-test-suite tests DK95 & Y79Y)
• 2.4.4 - 2024-06-08
  

  With special thanks to @ RedCMD for finding and reporting all of the following:

  • Allow comment after top-level block scalar with explicit indent indicator (#547)
  • Allow tab as indent for line comments before nodes (#548)
  • Do not allow tab before block collection (#549)
  • In flow collections, allow []{} immediately after : with plain key (#550)
  • Require indentation for ? explicit-key contents (#551)
  • Require indentation from block scalar header & flow collections in mapping values (#553)
• 2.4.3 - 2024-06-02
  
  • Improve error when parsing a non-string value (#459)
  • Do not parse -.NaN or +.nan as NaN (#546)
  • Support # within %TAG prefixes with trailing #comments
  • Check for non-node complex keys when stringifying with simpleKeys (#541)
• 2.4.2 - 2024-04-28
  
  • Restrict YAML 1.1 boolean strings to their explicit capitalization (#530)
  • Add sponsorship by Scipress (#536)
• 2.4.1 - 2024-03-06
  
  • cst: Do not drop trailing newline after line comment in block-map if followed by unindented block-seq value (#525)
  • Stringify flow collection comments in parent (#528)
  • Do not skip folding lines after the first in indented block scalars (#529)
• 2.4.0 - 2024-02-25
  
  • Add a command-line tool (#523)
  • Use the lineWidth option for line breaking in flow collections (#522)
• 2.3.4 - 2023-11-03
  
  • Do not throw for carriage return in tag shorthand (#501)
• 2.3.3 - 2023-10-14
  
  • Do not throw error on malformed URI escape in tag (#498)
• 2.3.2 - 2023-08-28
  
  • Fix docs typo (#489)
  • Do not require quotes for implicit keys with flow indicators (#494)
  • Update Prettier to v3 & update ESLint config
• 2.3.1 - 2023-05-26
  
  • Drop npm from package.json "engines" config (#476)
• 2.3.0 - 2023-05-23
• 2.3.0-5 - 2023-05-06
• 2.3.0-4 - 2023-04-18
• 2.3.0-3 - 2023-04-14
• 2.3.0-2 - 2023-04-14
• 2.3.0-1 - 2023-04-04
• 2.3.0-0 - 2023-03-11
• 2.2.2 - 2023-04-24
• 2.2.1 - 2022-12-30
• 2.2.0 - 2022-12-21
• 2.1.3 - 2022-10-05
• 2.1.2 - 2022-10-02
• 2.1.1 - 2022-05-29
• 2.1.0 - 2022-05-14
• 2.0.1 - 2022-04-15
• 2.0.0 - 2022-04-06
• 2.0.0-11 - 2022-03-22
• 2.0.0-10 - 2021-12-31
• 2.0.0-9 - 2021-11-13
• 2.0.0-8 - 2021-09-06
• 2.0.0-7 - 2021-07-17
• 2.0.0-6 - 2021-06-14
• 2.0.0-5 - 2021-04-18
• 2.0.0-4 - 2021-03-13
• 2.0.0-3 - 2021-01-31
• 2.0.0-2 - 2021-01-31
• 2.0.0-1 - 2020-10-05
• 2.0.0-0 - 2020-08-23
• 1.10.2 - 2021-03-13

from yaml GitHub release notes

---

Important

• Warning: This PR contains a major version upgrade, and may be a breaking change.
• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.