Upgrade yaml package version from 2.4.2 to 2.4.3

[2lambda123]

User description

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


Snyk has created this PR to upgrade yaml from 2.4.2 to 2.4.3.

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

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:

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

---

Description

• Updated the yaml package version from 2.4.2 to 2.4.3 in both package-lock.json and package.json
• Updated package integrity and resolved URLs for the yaml package
• Added license information for the yaml package

---

Changes walkthrough 📝

	Relevant files
Enhancement	package-lock.json Update `yaml` package version to 2.4.3 in package-lock.json package-lock.json ['Updated yaml package version from 2.4.2 to 2.4.3', 'Updated yaml package integrity and resolved URLs', 'License added for the yaml package'] +5/-4      package.json Update `yaml` package version to 2.4.3 in package.json      package.json ['Updated yaml package version from 2.4.2 to 2.4.3'] +1/-1

[cr-gpt]

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information

[performance-testing-bot]

Unable to locate .performanceTestingBot config file

[git-greetings]

Thanks @2lambda123 for opening this PR!

For COLLABORATOR only :

• To add labels, comment on the issue
  /label add label1,label2,label3

• To remove labels, comment on the issue
  /label remove label1,label2,label3

[codeautopilot]

Your organization has reached the subscribed usage limit. You can upgrade your account by purchasing a subscription at Stripe payment link

Disclaimer: This comment was entirely generated using AI. Be aware that the information provided may be incorrect.

Current plan usage: 103.94%

Have feedback or need help?
Discord
Documentation
[email protected]

[git-greetings]

PR Details of @2lambda123 in Accenture-mercury-nodejs :

OPEN	CLOSED	TOTAL
3	16	19

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[quine-bot]

👋 Figuring out if a PR is useful is hard, hopefully this will help.

• @2lambda123 has been on GitHub since 2019 and in that time has had 2362 public PRs merged
• Don't you recognize them? They've been here before 🎉
• Here's a good example of their work: HeyGenClone
• From looking at their profile, they seem to be good with JavaScript and CSS.

Their most recently public accepted PR is: 2lambda123/Accenture-sfmc-devtools#85

[penify-dev]

PR Review 🔍

⏱️ Estimated effort to review [1-5]	1, because this PR simply updates the yaml package version from 2.4.2 to 2.4.3 in both package-lock.json and package.json.
🧪 Relevant tests	No
⚡ Possible issues	No
🔒 Security concerns	No

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	environment	0	672 kB	eemeli

🚮 Removed packages: npm/[email protected]

View full report↗︎

[penify-dev]

PR Code Suggestions ✨

Category	Suggestion	Score
Best practice	Update the integrity field for the yaml package to match version 2.4.3 Consider updating the integrity field for the yaml package to match the new version 2.4.3. package-lock.json [6956-6959] "version": "2.4.3", "resolved": "https://registry.npmjs.org/yaml/-/yaml-2.4.3.tgz", -"integrity": "sha512-sntgmxj8o7DE7g/Qi60cqpLBA3HG3STcDA0kO+WfB05jEKhZMbY7umNm2rBpQvsmZ16/lPXCJGW2672dgOUkrg==", +"integrity": "NEW_INTEGRITY_VALUE_FOR_2.4.3", "license": "ISC", Suggestion importance[1-10]: 8 Why: Updating the integrity field for the yaml package to match the new version 2.4.3 is a best practice for maintaining package security and ensuring the integrity of the dependencies.	8

[gitginie]

@2lambda123
Thank you for your contribution to this repository! We appreciate your effort in closing pull request.
Happy coding!