chore(deps): bump js-yaml from 3.14.2 to 3.15.0

[dependabot]

Bumps js-yaml from 3.14.2 to 3.15.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

• c34b6c4 3.15.0 released
• 21e13d3 dist rebuild
• 4165c62 Add v3-legacy tag for publish
• d8ff750 Add package lock
• 24f13e7 Added maxTotalMergeKeys (10000) loader option (v5 backport)
• 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 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.

[greptile-apps]

PR author is in the excluded authors list.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 7a6b7e1

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

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
hyperdx-oss	Ignored	Preview	Jul 23, 2026 10:54pm
hyperdx-storybook	Ignored	Preview	Jul 23, 2026 10:54pm

[github-actions]

🟢 Tier 1 — Trivial

Docs, images, lock files, or a dependency bump. No functional code changes detected.

Why this tier:

• Bot author: dependabot[bot]

Review process: Auto-merge once CI passes. No human review required.
SLA: Resolves automatically.

Stats

• Production files changed: 0
• Production lines changed: 0
• Branch: dependabot/npm_and_yarn/js-yaml-3.15.0
• Author: dependabot[bot]

To override this classification, remove the review/tier-1 label and apply a different review/tier-* label. Manual overrides are preserved on subsequent pushes.

[github-actions]

Deep Review

✅ No critical issues found.

This PR bumps the transitive dependency js-yaml from 3.14.2 to 3.15.0 in yarn.lock. The change is lockfile-only — no application source, configuration, or workspace manifest is modified, and js-yaml is not a declared dependency in the root or any workspace package.json (it resolves transitively).

What actually changed (yarn.lock:19731): the js-yaml@npm:^3.10.0, ^3.13.0, ^3.13.1, ^3.6.1 entry now resolves to 3.15.0 with a new checksum; its own dependencies (argparse@^1.0.7, esprima@^4.0.0) and its bin mapping are unchanged. The parallel js-yaml@npm:^4.1.x → 4.1.1 entry (yarn.lock:19743) is untouched.

3.14.2 → 3.15.0 is a backward-compatible minor bump whose only substantive change is a backported loader option (maxTotalMergeKeys, default 10000) that caps YAML merge-key (<<) expansion to mitigate a resource-exhaustion vector. It is opt-out with a safe default and introduces no API changes, so no call sites require updates — a net security improvement with no behavioral regression on the happy path.

🔵 Notes (non-blocking)

• The repository continues to resolve two major versions of js-yaml (3.15.0 and 4.1.1). This duplication is pre-existing, not introduced by this diff, and is out of scope here; consolidating onto 4.x would be a separate follow-up and does not affect this bump's safety.

---

Reviewers (0 automated personas): The multi-agent fan-out could not be dispatched — the sandbox blocked all shell/git tooling in this session (bwrap: Can't create file at /home/.mcp.json, persisting even with the sandbox disabled), and the reviewer sub-agents plus diff tooling depend on it. This review was performed directly by inspecting the resolved lockfile change and confirming the diff is a transitive dependency bump with no source changes.

Testing gaps: No new behavior is introduced. Rely on the existing CI pipeline (install + build + test) to confirm the resolved 3.15.0 tree installs, builds, and passes; there is nothing new to unit-test in this diff.

[github-actions]

E2E Test Results

✅ All tests passed • 242 passed • 1 skipped • 1008s

Status	Count
✅ Passed	242
❌ Failed	0
⚠️ Flaky	1
⏭️ Skipped	1

Tests ran across 4 shards in parallel.

View full report →