chore(deps): bump js-yaml from 3.14.1 to 4.3.0

[dependabot]

Bumps js-yaml from 3.14.1 to 4.3.0.

Changelog

Sourced from js-yaml's changelog.

4.3.0, 3.15.0 - 2026-06-27

Security

• Backported maxTotalMergeKeys option.

[5.2.0] - 2026-06-26

Added

• Added maxTotalMergeKeys (10000) loader option to limit the total number of keys processed by YAML merge (<<) across one load() / loadAll() call.
• Added maxAliases (-1) loader option to limit the number of YAML aliases per document.

Removed

• maxMergeSeqLength replaced with maxTotalMergeKeys for limiting YAML merge processing.

Fixed

• Round-trip of integers with exponential form (>= 1e21)

[5.1.0] - 2026-06-23

Added

• Collection tags can finalize an incrementally populated carrier into a different result value.

Changed

• [breaking] quoteStyle now selects the preferred quote style; use the restored forceQuotes option to force quoting non-key strings.

[5.0.0] - 2026-06-20

Added

• Added named exports for schemas, tags, parser events and AST utilities.
• Reworked JSON_SCHEMA and CORE_SCHEMA with spec-compliant scalar resolution rules, and added YAML11_SCHEMA.
• Added realMapTag for lossless mappings with non-string and complex keys. Object-based mappings now reject complex keys instead of stringifying them.
• Added dump() transform option for changing the generated AST before rendering.
• Added dump() options seqInlineFirst, flowBracketPadding, flowSkipCommaSpace, flowSkipColonSpace, quoteFlowKeys, quoteStyle and tagBeforeAnchor.
• Added formal data layers (events and AST) for modular data pipelines.
  • Added low-level parser (to events), presenter and visitor APIs.
• Added the YAML Test Suite to the test set.

Changed

• See the migration guide for upgrade notes.
• Rewritten in TypeScript and reorganized the public API around flat named exports.

... (truncated)

Commits

• 33d05b5 4.3.0 released
• 663bfab Drop demo publish, to not override new v5 one.
• 1cb8c7b Add v4-legacy tag for publish
• 02f27af Restore umd builds back to es5
• 8be84ed Fix es5 compatibility
• 59423c6 Replace maxMergeSeqLength option with maxTotalMergeKeys (more robust). Ba...
• 6842ef6 doc polish
• 590dbab 4.2.0 released
• f944dc5 Add package.json funding field
• f692719 Changelog update
• Additional commits viewable 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 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.

[changeset-bot]

⚠️ No Changeset found

Latest commit: ed3127e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

Deep Review

This PR is titled as a js-yaml bump to 4.3.0, but the only changed file is yarn.lock, and the change leaves the lockfile inconsistent with package.json. Four reviewers independently confirmed the core defect at full confidence.

🔴 P0/P1 -- must fix

• yarn.lock:529 -- The js-yaml: "npm:^4.2.0" entry was removed from the helm-charts@workspace:. dependency block and the js-yaml@npm:^4.2.0 resolution was deleted (with no 4.3.0 added), yet package.json still declares "js-yaml": "^4.2.0", so the lockfile no longer satisfies the manifest and bare yarn under CI (.github/workflows/release.yml:35, Yarn 4 immutable-by-default) aborts with YN0028, breaking the release pipeline before yarn run version/yarn run release execute.
  • Fix: Regenerate the lockfile with yarn install against the intended manifest (bump package.json to ^4.3.0 first if a v4 move is actually wanted) so the workspace dependency and a matching js-yaml@npm:^4.x resolution are restored, then verify CI=true yarn install --immutable exits 0.
  • _{correctness, project-standards, reliability, maintainability}

🟡 P2 -- recommended

• scripts/update-chart-versions.js:2 -- js-yaml is imported and used via yaml.load/yaml.dump (run by the version script), but after this change it resolves only to the transitive 3.14.1 pulled by @changesets/cli, a silent major-version drift away from the declared ^4.x.
  • Fix: Restore a resolved direct js-yaml dependency in the lockfile via the P1 relock; if v4 is intended, confirm the load/dump call sites behave as expected against the v4 API.
  • _{maintainability, correctness}
• .github/workflows/release.yml:35 -- No pull-request check runs yarn install --immutable, so lockfile-vs-manifest drift is invisible until the post-merge release workflow fails.
  • Fix: Add a lightweight PR job that runs corepack enable && yarn install --immutable to gate merges on lockfile integrity.
  • _{correctness, project-standards, reliability, maintainability}

---

Reviewers (4): correctness, project-standards, reliability, maintainability.

Testing gaps:

• No PR-time yarn install --immutable check to catch lockfile/package.json drift before merge.
• No test exercises scripts/update-chart-versions.js against the actually-resolved js-yaml version, so YAML-output differences from a major-version swap would go unnoticed.