Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade yaml from 2.2.2 to 2.6.0 #481

Merged
merged 1 commit into from
Nov 27, 2024

Conversation

suculent
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade yaml from 2.2.2 to 2.6.0.

ℹ️ 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.


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

  • The recommended version was released on 17 days ago.

Release notes
Package name: yaml
  • 2.6.0 - 2024-10-13
    • Use a proper tag for !!merge << keys (#580)
    • Add stringKeys parse option (#581)
    • Stringify a Document as a Document (#576)
    • Add sponsorship by Manifest
  • 2.5.1 - 2024-09-03
    • Include range in flow sequence pair maps (#573)
  • 2.5.0 - 2024-07-24
    • Add --indent option to CLI tool (#559, with thanks to @ danielbayley)
    • Require newline in all cases for props on block sequence (#557)
    • Always reset indentation in lexer on ... (#558)
    • Ignore minContentWidth if greater than lineWidth (#562)
    • Drop unused Collection.maxFlowStringSingleLineLength (#522, #421)
  • 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
  • 2.3.2 - 2023-08-28
  • 2.3.1 - 2023-05-26
  • 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
from yaml GitHub release notes

Important

  • 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:

Snyk has created this PR to upgrade yaml from 2.2.2 to 2.6.0.

See this package in npm:
yaml

See this project in Snyk:
https://app.snyk.io/org/suculent/project/ecd536cf-5cd8-456a-9632-baaf13c7dd47?utm_source=github&utm_medium=referral&page=upgrade-pr
@suculent suculent merged commit 95fb0a1 into master Nov 27, 2024
6 of 9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants