Skip to content

chore(deps-dev): bump js-yaml from 4.1.1 to 4.2.0 in /apps/vs-code-designer#9343

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/apps/vs-code-designer/js-yaml-4.2.0
Open

chore(deps-dev): bump js-yaml from 4.1.1 to 4.2.0 in /apps/vs-code-designer#9343
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/apps/vs-code-designer/js-yaml-4.2.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 1, 2026

Copy link
Copy Markdown
Contributor

Bumps js-yaml from 4.1.1 to 4.2.0.

Changelog

Sourced from js-yaml's changelog.

[4.2.0] - 2026-06-01

Added

  • Added docs/safety.md with notes about processing untrusted YAML.
  • Added maxDepth (100) loader option. Not a problem, but gives a better exception instead of RangeError on stack overflow.
  • Added a loader option limiting merge sequence length. Not a problem after merge fix, but an additional restriction for safety.
  • Added sourcemaps to dist/ builds.

Changed

  • Stop resolving numbers with underscores as numeric scalars, #627.
  • Switched dev toolchains to Vite / neostandard.
  • Updated demo.
  • Reorganized tests.
  • dist/ files are no longer kept in the repository.

Fixed

  • Fix parsing of properties on the first implicit block mapping key, #62.
  • Fix trailing whitespace handling when folding flow scalar lines, #307.
  • Reject top-level block scalars without content indentation, #280.
  • Ensure numbers survive round-trip, #737.
  • Fix test coverage for issue #221.
  • Fix flow scalar trailing whitespace folding, #307.
  • Fix digits in YAML named tag handles.

Security

  • Fix potential DoS via quadratic complexity in merge - deduplicate repeated elements (makes sense for malformed files > 10K).

[3.14.2] - 2025-11-15

Security

  • Backported v4.1.1 fix to v3
Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [js-yaml](https://github.com/nodeca/js-yaml) from 4.1.1 to 4.2.0.
- [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md)
- [Commits](nodeca/js-yaml@4.1.1...4.2.0)

---
updated-dependencies:
- dependency-name: js-yaml
  dependency-version: 4.2.0
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
Copilot AI review requested due to automatic review settings July 1, 2026 19:54
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jul 1, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.

@github-actions

github-actions Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

🤖 AI PR Validation Report

PR Review Results

Thank you for your submission! Here's detailed feedback on your PR title and body compliance:

PR Title

  • Current: chore(deps-dev): bump js-yaml from 4.1.1 to 4.2.0 in /apps/vs-code-designer
  • Issue: None — the title is specific, correctly scoped, and clearly describes the dependency update.
  • Recommendation: No change needed.

Commit Type

  • Properly selected: chore.
  • Only one commit type is implied, which is correct for a dependency bump.

⚠️ Risk Level

  • The PR body is missing a selected risk level checkbox.
  • Advised risk: low — this is a small dependency version bump in a single package file, with limited scope.
  • Recommendation: Select exactly one risk label in the PR body and ensure it matches the repo label convention (e.g. risk:low, risk:medium, or risk:high) if applicable.

What & Why

  • Current: (Missing)
  • Issue: This section is required and should briefly explain the purpose of the change.
  • Recommendation: Add a short explanation such as: Upgrade js-yaml to 4.2.0 to pick up upstream fixes and security improvements in the VS Code designer package.

Impact of Change

  • No impact summary was provided.
  • Recommendation:
    • Users: Note whether there is any visible change; for a dependency bump, this may be No direct user-facing change expected.
    • Developers: Mention that package dependency resolution is updated in /apps/vs-code-designer.
    • System: Mention any expected risk or note that the change is limited to dependency metadata and lockfile resolution if applicable.

⚠️ Test Plan

  • The diff contains no test changes, which is acceptable for this dependency-only update if the PR is documented as non-functional / config-only.
  • However, the checkbox section is empty, so the body does not currently explain why automated tests were not added.
  • Recommendation: Mark Manual testing completed only if you actually performed it, or add a brief note that this is a dependency-only change and no automated tests were required.

⚠️ Contributors

  • No contributors listed.
  • Recommendation: Optional, but if anyone helped with validation or review, credit them here.

⚠️ Screenshots/Videos

  • Not applicable for this change.
  • Recommendation: No screenshots needed for a dependency bump.

Summary Table

Section Status Recommendation
Title None
Commit Type None
Risk Level ⚠️ Select one risk level in the PR body
What & Why Add a brief purpose statement
Impact of Change Add user/dev/system impact notes
Test Plan ⚠️ Explain why tests are not needed or mark manual testing if done
Contributors ⚠️ Optional; add if applicable
Screenshots/Videos ⚠️ Not needed for this change

Overall: the PR title is good, but the body is incomplete and should be updated before merge. Please add the missing required sections and ensure the risk label/body selection matches.


Last updated: Wed, 01 Jul 2026 19:54:28 GMT

@github-actions

github-actions Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

📊 Coverage check completed. See workflow run for details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code pr-validated

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant