Skip to content

Conversation

@Blankll
Copy link
Member

@Blankll Blankll commented Nov 4, 2024

snyk-top-banner

Snyk has created this PR to upgrade yaml from 2.5.1 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 1 version ahead of your current version.

  • The recommended version was released on 22 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)
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.5.1 to 2.6.0.

See this package in npm:
yaml

See this project in Snyk:
https://app.snyk.io/org/blankll/project/9c72c875-e7a2-4e68-85a9-7b26a5bc5b32?utm_source=github&utm_medium=referral&page=upgrade-pr
@codecov
Copy link

codecov bot commented Nov 4, 2024

Welcome to Codecov 🎉

Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.

Thanks for integrating Codecov - We've got you covered ☂️

@Blankll Blankll merged commit f74a925 into master Nov 7, 2024
4 checks passed
@Blankll Blankll deleted the snyk-upgrade-bd2599231a417a66be912b567529d27e branch November 7, 2024 13:03
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.

3 participants