Bump js-yaml from 4.1.1 to 4.2.0 in /docs in the npm_and_yarn group across 1 directory

[dependabot]

Bumps the npm_and_yarn group with 1 update in the /docs directory: js-yaml.

Updates 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 maxMergeSeqLength (20) loader option. 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

• See full diff in compare view

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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.

---

pr-sous-chef: refreshed the branch and left a progress nudge. Run: https://github.com/github/gh-aw/actions/runs/27576490342

Generated by 👨‍🍳 PR Sous Chef · 65.7 AIC · ⌖ 1.01 AIC · ⊞ 17.4K · ◷

[github-actions]

@copilot review all comments and address unresolved review feedback. Then rerun checks after the branch update and summarize any remaining blockers.

Generated by 👨‍🍳 PR Sous Chef · 65.7 AIC · ⌖ 1.01 AIC · ⊞ 17.4K · ◷

[github-actions]

👋 Thanks for the automated js-yaml bump from 4.1.1 → 4.2.0 in the /docs directory! The 4.2.0 release carries a meaningful security fix — potential DoS via quadratic complexity in YAML merge handling — plus new maxDepth and maxMergeSeqLength safety options, making this a worthwhile update.

The only checklist flag is the absence of test file changes. For a lockfile-only update this is expected and not a real gap, but maintainers may want a quick smoke-check to confirm the docs toolchain is happy with the new version before merging.

Verify the /docs build is unaffected by the js-yaml 4.1.1 → 4.2.0 upgrade:
1. Change into the /docs directory.
2. Run `npm ci` to install from the updated package-lock.json.
3. Run the full docs build (e.g. `npm run build`) and confirm it completes without errors or warnings.
4. Spot-check any YAML-parsing paths in the docs toolchain to ensure compatibility with js-yaml 4.2.0 behaviour changes (e.g. the new maxDepth/maxMergeSeqLength limits and the updated numeric-scalar parsing rules).

Generated by ✅ Contribution Check · 304.2 AIC · ⌖ 17.3 AIC · ⊞ 24.7K · ◷

[github-actions]

Please run a /docs build smoke test and share the result.

Generated by 👨‍🍳 PR Sous Chef · 58 AIC · ⌖ 1.01 AIC · ⊞ 17.4K · ◷