Skip to content

[Snyk] Security upgrade js-yaml from 4.1.1 to 4.2.0#254

Merged
kevin-from-atlassian merged 1 commit into
mainfrom
snyk-fix-5c4fa2b9b92b557d096c7e18c33a408f
Jun 16, 2026
Merged

[Snyk] Security upgrade js-yaml from 4.1.1 to 4.2.0#254
kevin-from-atlassian merged 1 commit into
mainfrom
snyk-fix-5c4fa2b9b92b557d096c7e18c33a408f

Conversation

@hstan

@hstan hstan commented Jun 16, 2026

Copy link
Copy Markdown
Member

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

  • package.json
  • yarn.lock

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
medium severity Inefficient Algorithmic Complexity
SNYK-JS-JSYAML-17342520
  738  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • 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 fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

@hstan hstan requested a review from a team as a code owner June 16, 2026 16:50
@kevin-from-atlassian kevin-from-atlassian merged commit 6da56d8 into main Jun 16, 2026
8 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.

3 participants