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

[dependabot]

Bumps js-yaml from 4.1.1 to 5.2.0.

Changelog

Sourced from js-yaml's changelog.

[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.
• Reduced the set of exported schemas:
  • YAML 1.2 schemas: CORE_SCHEMA (loader default), JSON_SCHEMA, FAILSAFE_SCHEMA.
  • YAML11_SCHEMA, a combination of all YAML 1.1 tags (YAML 1.1 does not specify a schema, only "types").

... (truncated)

Commits

• c28ed5e 5.2.0 released
• 125cd5a Add maxAliases option
• 3105455 Replace maxMergeSeqLengthoption with maxTotalMergeKeys (more robust)
• 39d00d6 numbers: Drop boxed numbers support, simplify .identify() checks, clarify rou...
• eb5cb5b fix: round-trip integers that stringify in exponential notation (#771)
• 89024c4 Update migration info, close #770
• f1e45cd 5.1.0 released
• 53b22be Fix constructor coverage
• a1eaa2b Fix quote style options and restore forceQuotes
• 0532e7d Add finalizers for immutable collection tags
• 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)

---

Note

Medium Risk
Major-version dependency bump with no code changes in the diff; parsing/serialization behavior may change for YAML usage in api/core without compile-time signal from this PR alone.

Overview
Upgrades js-yaml from ^4.1.1 to ^5.2.0 in the root workspace, apps/api, and packages/core, with matching updates in pnpm-lock.yaml (direct deps resolve to 5.2.0; some transitive Astro-related packages move to js-yaml@4.3.0).

There are no application source changes in this PR—only dependency manifests and the lockfile. js-yaml v5 is a major release (TypeScript rewrite, schema/API changes per upstream migration notes), so runtime YAML load/dump behavior could differ anywhere the library is used once installed.

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

[dependabot]

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[cursor]

No security findings for the changed files.

Reviewed changes:

• package.json:27, apps/api/package.json:31, and packages/core/package.json:24 update direct js-yaml dependencies from ^4.1.1 to ^5.2.0.
• pnpm-lock.yaml updates the corresponding lockfile entries from js-yaml@4.1.1 to js-yaml@5.2.0 with the same argparse@2.0.1 dependency shape.

Threat surfaces checked against this diff:

1. MCP endpoint auth: no MCP route or token/project-scoping code changed.
2. Query execution sandboxing: no execute_query, DuckDB, view-scoping, timeout, or result-limit code changed.
3. Admin auth / Better Auth: no session secret, CSRF, cookie, or auth route code changed.
4. API input validation: no Hono route handlers, Zod schemas, MongoDB query construction, or DuckDB SQL construction changed.
5. Environment secrets: no .env* files or secret-handling/logging code changed.
6. Dependency exposure: ran pnpm audit --prod. It does not report a js-yaml advisory for the bumped version. The audit still reports existing transitive advisories for packages such as xlsx, @xmldom/xmldom, ws, and form-data, but the affected lockfile entries are present in both the base and head and are not introduced by this PR.

  

_{Sent by Cursor Automation: archmax Security Review}

[github-actions]

Docker image ready

docker pull ghcr.io/archmaxai/archmax:pr-76