[Snyk] Security upgrade js-yaml from 4.1.1 to 4.3.0

[caniszczyk]

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

Snyk changed the following file(s):

• ui/package.json
• ui/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Inefficient Algorithmic Complexity SNYK-JS-JSYAML-17900054	828

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

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.

[caniszczyk]

This minor version upgrade of js-yaml introduces several behavioral changes that require verification.

Key Changes:

• YAML 1.2 Compliance: The parser is now stricter. Numbers are parsed according to the YAML 1.2 specification. For example, a string like 0123 is now parsed as a decimal number, not an octal. Time-like strings such as 1:23 are now parsed as strings instead of numbers. [1]
• Error on Empty Input: The load() function will now throw an exception when parsing an empty string or file, whereas it previously returned undefined. Code relying on the old behavior will need to be updated. [1]
• Custom Types: The internal API for custom types has been changed. If your project defines custom YAML tags, you will need to review the updated examples and refactor your implementation. [1]
• New Safety Limits: Version 4.2.0 introduced new loader options like maxDepth to prevent potential denial-of-service attacks from overly complex documents. These have default values and could, in rare cases, cause issues with very large or deeply nested YAML files that previously worked. [1]

Recommendation: Review code that uses load() to ensure it correctly handles exceptions for empty inputs. Verify that any YAML files with non-standard number formats are still parsed as expected after the upgrade to stricter YAML 1.2 rules. If you use custom types, a refactor will be necessary.

Source: Changelog

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

[netlify]

✅ Deploy Preview for devspace-docs canceled.

Name	Link
🔨 Latest commit	5d7dee7
🔍 Latest deploy log	https://app.netlify.com/projects/devspace-docs/deploys/6a509980142a55000847df39