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

[dependabot]

Bumps js-yaml from 4.1.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

[cursor]

PR Summary

Low Risk
Dependency-only minor bump within js-yaml v4; improves YAML parse safety for existing untrusted load() call sites with no API or logic changes in this repo.

Overview
Bumps js-yaml from 4.1.x to ^4.3.0 in cron_service, packages_worker, and security_best_practices_worker, with pnpm-lock.yaml updated to resolve 4.3.0 (and related transitive refreshes such as js-yaml@3.15.0 where older consumers still pull v3).

No application code changes—the workers keep using yaml.load() on external YAML (e.g. OpenStack governance, SECURITY-INSIGHTS, security evaluation configs). 4.3.0 backports maxTotalMergeKeys, which limits YAML merge (<<) processing during load() and addresses merge-related DoS concerns on untrusted input.

^{Reviewed by Cursor Bugbot for commit 98f8ad6. Bugbot is set up for automated code reviews on this repo. Configure here.}

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 2895c71. Configure here.}

[cursor]

Lockfile forces SSH git fetch

High Severity

This Dependabot lockfile refresh rewrites clearbit's transitive needle dependency from a public HTTPS codeload tarball to a git@github.com SSH git resolution. Fresh pnpm installs (especially CI without GitHub SSH keys) can fail while resolving backend's clearbit dependency, even though the intended change is only the js-yaml bump.

Additional Locations (2)

• pnpm-lock.yaml#L15679-L15680
• pnpm-lock.yaml#L18539-L18540

 

^{Reviewed by Cursor Bugbot for commit 2895c71. Configure here.}