Skip to content

fix(deps): update dependency js-yaml to v5 - #1037

Merged
Danathar merged 1 commit into
mainfrom
renovate/js-yaml-5.x
Nov 18, 2026
Merged

Danathar merged 1 commit into
mainfrom
renovate/js-yaml-5.x

Conversation

@mergeraptor

@mergeraptor mergeraptor Bot commented Nov 17, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
js-yaml ^4.3.1 → ^5.0.0 age confidence

Release Notes

nodeca/js-yaml (js-yaml)

v5.5.0

Compare Source

Changed
  • Updated argparse to v3.
  • Updated development dependencies.
Fixed
  • Correct percent-encoding of shorthand and verbatim tags.
  • Reject ,, ], and } at the start of block plain scalars, #​801.
  • Report the exact position of non-printable characters in errors, #​801.

v5.4.3

Compare Source

Fixed
  • Fixed loading a whitespace-only block scalar followed by a less indented
    line, #​802.

v5.4.2

Compare Source

Fixed
  • forceQuotes no longer quotes non-string scalars, #​798.

v5.4.1

Compare Source

Changed
  • Hard-limit merge sequence size to 100.
Security
  • Count empty mappings in merge sequences toward maxTotalMergeKeys to limit
    CPU usage, #​797.

v5.4.0

Compare Source

Added
  • Added the scalarStyleRules dumper option to customize string formatting.
    See Scalar styling for details.
Changed
  • [breaking] Flattened the low-level AST node style representation. Scalar
    and collection nodes now use SCALAR_STYLE and COLLECTION_STYLE values;
    explicit tags use the separate tagged property. Alias nodes now contain
    only kind and anchor. This only affects code that directly constructs or
    edits AST nodes.
  • [breaking] The sortKeys option was rewritten using AST mutation to avoid
    side effects.
  • Reworked scalar style selection. This can change formatting without changing
    loaded values; in particular, whitespace-only strings are now double-quoted.
Fixed
  • Accept a byte order mark at the start of each document in a stream, #​791.
  • Produce valid flow mappings with quoteFlowKeys and flowSkipColonSpace,
    including alias and property-only keys, #​786.
  • Preserve empty scalar items when converting block sequences to flow style.
  • Do not apply the 1024-character simple-key limit to flow mapping keys.
  • Count Unicode code points, rather than UTF-16 code units, for the
    1024-character simple-key limit.
  • Add an explicit document-end marker after keep-chomped block scalars when
    needed to preserve trailing newlines.

v5.3.0

Compare Source

This release focuses on reworking the documentation and making small
architectural improvements before moving forward.

Added
  • Added completely new documentation.
  • Exported DUMP_SCHEMA, the default schema used by the dumper.
  • Added YAMLException.throwAt() for throwing an error at a source position.
Changed
  • Changed flat constant exports to grouped exports: EVENT_ID, SCALAR_STYLE,
    COLLECTION_STYLE, and CHOMPING_MODE, along with their value types. The old
    exports are still preserved, but deprecated.
  • Made identify mandatory for custom tag definitions. Use
    identify: () => false for load-only tags.
Deprecated
  • Deprecated flat constant exports. Use grouped ones instead.
Removed
  • Removed the MERGE_KEY export (not used anymore after last fixes).
Fixed
  • Validate << sequence items at merge time, so aliased merge sources are
    checked too.
  • Resolve << outside of a mapping key as the plain string '<<', matching
    v4, instead of leaking an internal symbol into the result.

v5.2.3

Compare Source

Fixed
  • Prevent prototype fallback when resolving tags and mapping entries, #​782.
  • Resolve !!timestamp years 0000-0099 correctly, #​775.
  • Preserve implicit null mapping values before document markers and reject
    unpaired mapping event streams, #​784.
  • Preserve folded scalar values with tab-indented lines when round-tripping a
    parsed AST through present(); dump() and loading are unaffected, #​780.

v5.2.2

Compare Source

Fixed
  • Quote flow scalars where a colon precedes a flow indicator, #​773.
Security
  • Avoid exponential parsing time for nested flow sequence pairs.

v5.2.1

Compare Source

Fixed
  • Add Map support to !!omap (should work when realMapTag used)
Security
  • Remove quadratic complexity from !!omap addItem. Regression from v5
    (usually not critical, because YAML11_SCHEMA is not default anymore).

v5.2.0

Compare Source

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)

v5.1.0

Compare Source

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.

v5.0.0

Compare Source

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").
  • load/dump default behaviour is now specified exactly via schemas:
    • load uses CORE_SCHEMA, without !!merge by default.
    • dump uses YAML11_SCHEMA + CORE_SCHEMA for the quoting check, to
      guarantee backward compatibility by default.
  • !!set is now loaded as a JavaScript Set.
  • Replaced the Type API with a tags API. Similar, but more precise and
    simpler. See examples for details. Tags can be defined via
    defineScalarTag(), defineSequenceTag() and defineMappingTag(), or as a
    spread + override of an existing tag.
  • Renamed Schema.extend() to Schema.withTags().
  • Expanded YAML 1.2 conformance and improved handling of directives, document
    markers, block keys, multiline scalars, tag syntax and other things.
  • load() now throws on empty input instead of returning undefined.
  • Moved browser builds to the js-yaml/browser export.
  • Deprecated the loadAll signature with an iterator (still works, but is a
    candidate for removal).
Removed
  • Removed deprecated safeLoad(), safeLoadAll() and safeDump() exports.
  • Removed DEFAULT_SCHEMA and the nested types export.
  • Removed loader options onWarning, legacy and listener.
  • Removed dumper options styles, replacer, noCompatMode, condenseFlow,
    quotingType and forceQuotes. Renamed noArrayIndent to seqNoIndent.
    Formatting and representation are now configured through presenter options,
    schemas and tag definitions. See migration guide on how to replace.
  • Removed support for importing internal files from lib/.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@hivecommons-hive

hivecommons-hive Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Hive status — updated in place; edits do not notify. Full history is in the Activity Monitor.

ℹ️ Sentinel: informational, author is trusted (allow-listed bot), merge is not blocked. Head 4bfc88b91762 matched:

  • sensitive_path: changes 2 sensitive path(s) (package-lock.json, package.json)

No sentinel-alert label was added. The finding is recorded in the dashboard Security tab and /api/sentinel; set sentinel.trusted_authors_block: true to block trusted authors too.

stage 060-reviewed → 050-review-pending: repo-auto-merge-disabled

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I checked the js-yaml v5 breaking changes against every call site in this repo. This looks correct to me; CI test (with coverage) is green on 02ca53b.

  • load() now throws on empty input. All four runtime callers already handle a throw. SectionPicker.vue:52 runs inside try/catch. update-image-versions.js:67 goes through readGenerated, which catches and returns undefined (:48-55). wolves-projects.ts:41 and wolves-lore-records.ts:186 already throw on anything that is not a mapping.
  • load defaults to CORE_SCHEMA, so no !!merge or timestamps. No YAML under src/ or .github/ uses <<: merge keys. No caller checks for Date. public/stream-versions.yml quotes checkedAt, so it stays a string.
  • Removed dump options (forceQuotes, noArrayIndent, quotingType, condenseFlow, styles, replacer). None are used. The only option passed is lineWidth: -1 (scripts/lib/image-version-audit.js:347-348), and v5 keeps it.
  • Removed safeLoad/safeDump/DEFAULT_SCHEMA. Not imported anywhere. Every import is a named load or dump.

One optional cleanup: js-yaml v5 is written in TypeScript and ships its own types, so @types/js-yaml (package.json:37, still ^4.0.9) is now redundant. It does not break anything, because TypeScript prefers the package's bundled types. Remove it in a follow-up if you like.

Confidence: 5/5 (safe)

— hive: agent=reviewer backend=claude model=claude-opus-5-5 effort=medium claude=2.1.325

@hivecommons-hive hivecommons-hive Bot added no-dco A commit is missing Signed-off-by — run `git rebase --signoff` role/trusted Author is trusted for unattended merge (trusted-author role or registry/claim tier in require_tiers) stage/050-review-pending Review swarm requested; awaiting a verdict for the current head stage/060-reviewed Review swarm verdict approve; a gate is still pending (CI running, soak not started) and removed stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Nov 17, 2026
@hivecommons-hive

hivecommons-hive Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

🐝 Superseded regeneration series

mergeraptor[bot] has 3 open PRs regenerating the same file(s). This one is the newest, so the 2 older one(s) are superseded by construction:

Posted once on the newest PR rather than on each of them, so a daily regeneration does not produce a daily comment on every PR in the series.

Evidence — identical changed-file set (2 file(s)):

  • package-lock.json
  • package.json

This is a suggestion, not a verdict. Hive will not close, label, approve or merge anything here — a human decides.

It was produced by comparing changed-file sets across open PRs, which is a candidate generator: PRs that share a file are not necessarily the same work. Here the patches DIFFER, so this is the weaker tier: dependency-bump PRs that edit one shared manifest, and unrelated fixes to one busy file, both land in it. Read the diffs before acting.

Danathar
Danathar previously approved these changes Nov 17, 2026

@Danathar Danathar left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving. Major bump of js-yaml ^4.3.1 → ^5.0.0. Every use in the repo is a named load or dump import (src/data/wolves-projects.ts, src/data/wolves-lore-records.ts, SectionPicker.vue, scripts/update-image-versions.js, scripts/lib/image-version-audit.js and the workflow tests). Both functions still exist in v5. CI passed at this head: typecheck, the full test suite including update-image-versions*.test.ts (which goes through the dump path) and the build. @eslint/eslintrc keeps its own nested js-yaml 4.3.2, which is expected.

The 5.4.0 changelog says scalar style selection changed (for example, whitespace-only strings are now double-quoted). That can change the formatting of YAML that update-image-versions writes, but not the values. Worth knowing if a later content-update PR shows quoting-only diffs.

@hivecommons-hive hivecommons-hive Bot added stage/090-ready-for-human-merge Hive would merge this but trust/role blocks it; a maintainer's /lgtm /approve is all that is missing and removed stage/060-reviewed Review swarm verdict approve; a gate is still pending (CI running, soak not started) labels Nov 17, 2026
@hivecommons-hive

hivecommons-hive Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Ready for a human merge: verdict approved @8d219ad, 5/5 checks green, soak 30m0s elapsed. Auto-merge is off for this repo, so a person merges.

The hive never approves on your behalf: approve and merge it on GitHub if you accept it.

Updated 2026-11-18 16:06 UTC.

@hivecommons-hive hivecommons-hive Bot added stage/050-review-pending Review swarm requested; awaiting a verdict for the current head stage/090-ready-for-human-merge Hive would merge this but trust/role blocks it; a maintainer's /lgtm /approve is all that is missing and removed stage/090-ready-for-human-merge Hive would merge this but trust/role blocks it; a maintainer's /lgtm /approve is all that is missing stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Nov 17, 2026
@Danathar

Copy link
Copy Markdown
Contributor

Correction: this PR isn't superseded. It updates js-yaml to v5, which no other open PR updates. It only shares package.json / package-lock.json with the other Renovate PRs. Ignore the hive's "Superseded regeneration series" note above: it treated every bot PR that touches the same files as one series. That's fixed in hivecommons/hive#18837.

@mergeraptor
mergeraptor Bot force-pushed the renovate/js-yaml-5.x branch from 02ca53b to dea5239 Compare November 18, 2026 00:23
@hivecommons-hive hivecommons-hive Bot added stage/050-review-pending Review swarm requested; awaiting a verdict for the current head stage/070-fixing Hive-authored PR: CI red, changes requested or needs rebase; a hive agent is fixing it and removed stage/090-ready-for-human-merge Hive would merge this but trust/role blocks it; a maintainer's /lgtm /approve is all that is missing stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Nov 18, 2026
@hivecommons-hive

Copy link
Copy Markdown
Contributor

Review follow-ups (below review.backlog.min_severity: P2)

Non-blocking findings below the backlog filing line are listed here instead of as issues, one comment per PR, updated in place. Tick them off as they are fixed; set review.backlog.min_severity: P3 to file every finding.

  • P3 low style — Old v4 type package left installed after js-yaml upgrade (package.json:37): package.json:37 still lists "@types/js-yaml": "^4.0.9". js-yaml v5 is rewritten in TypeScript (per its 5.0.0 release notes) and ships its own types, which TypeScript prefers over @types, so the v4 ty…

@hivecommons-hive hivecommons-hive Bot added the stage/stalled No activity (head, comment, review, CI, label) longer than the stage expects; nobody is working it label Nov 18, 2026
@mergeraptor
mergeraptor Bot force-pushed the renovate/js-yaml-5.x branch from dea5239 to 4bfc88b Compare November 18, 2026 03:14
@hivecommons-hive hivecommons-hive Bot removed the stage/070-fixing Hive-authored PR: CI red, changes requested or needs rebase; a hive agent is fixing it label Nov 18, 2026
@hivecommons-hive hivecommons-hive Bot added stage/050-review-pending Review swarm requested; awaiting a verdict for the current head stage/060-reviewed Review swarm verdict approve; a gate is still pending (CI running, soak not started) stage/090-ready-for-human-merge Hive would merge this but trust/role blocks it; a maintainer's /lgtm /approve is all that is missing and removed stage/stalled No activity (head, comment, review, CI, label) longer than the stage expects; nobody is working it stage/050-review-pending Review swarm requested; awaiting a verdict for the current head stage/060-reviewed Review swarm verdict approve; a gate is still pending (CI running, soak not started) stage/090-ready-for-human-merge Hive would merge this but trust/role blocks it; a maintainer's /lgtm /approve is all that is missing labels Nov 18, 2026

@Danathar Danathar left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Re-approving at the rebased head. The change is the same as the one I approved before: js-yaml ^4.3.1 → ^5.0.0, plus @eslint/eslintrc keeping its own nested js-yaml 4.3.2. The code only uses the named load and dump imports, which v5 still has. test, Audit GitHub Actions and wolves-movie-flow pass on this head.

@hivecommons-hive hivecommons-hive Bot added stage/060-reviewed Review swarm verdict approve; a gate is still pending (CI running, soak not started) and removed stage/090-ready-for-human-merge Hive would merge this but trust/role blocks it; a maintainer's /lgtm /approve is all that is missing labels Nov 18, 2026
@mergeraptor
mergeraptor Bot force-pushed the renovate/js-yaml-5.x branch from 4bfc88b to 8d219ad Compare November 18, 2026 15:11

@Danathar Danathar left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Re-approving after Renovate's rebase. The diff is still only js-yaml 4 → 5 in package.json and the lockfile; @eslint/eslintrc keeps its own nested js-yaml 4.3.2. All checks pass on this head.

@hivecommons-hive hivecommons-hive Bot added stage/050-review-pending Review swarm requested; awaiting a verdict for the current head stage/060-reviewed Review swarm verdict approve; a gate is still pending (CI running, soak not started) stage/090-ready-for-human-merge Hive would merge this but trust/role blocks it; a maintainer's /lgtm /approve is all that is missing and removed stage/060-reviewed Review swarm verdict approve; a gate is still pending (CI running, soak not started) stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Nov 18, 2026
@Danathar
Danathar added this pull request to the merge queue Nov 18, 2026
Merged via the queue into main with commit cb393e2 Nov 18, 2026
5 checks passed
@Danathar
Danathar deleted the renovate/js-yaml-5.x branch November 18, 2026 16:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-dco A commit is missing Signed-off-by — run `git rebase --signoff` role/trusted Author is trusted for unattended merge (trusted-author role or registry/claim tier in require_tiers) stage/090-ready-for-human-merge Hive would merge this but trust/role blocks it; a maintainer's /lgtm /approve is all that is missing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant