chore(deps-dev): bump js-yaml from 3.14.2 to 3.15.2 - #254
Conversation
Bumps [js-yaml](https://github.com/nodeca/js-yaml) from 3.14.2 to 3.15.2. - [Changelog](https://github.com/nodeca/js-yaml/blob/3.15.2/CHANGELOG.md) - [Commits](nodeca/js-yaml@3.14.2...3.15.2) --- updated-dependencies: - dependency-name: js-yaml dependency-version: 3.15.2 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dhensby
left a comment
There was a problem hiding this comment.
Approving — js-yaml 3.14.2 → 3.15.2, a transitive dev-scope patch (lockfile-only, manifest untouched).
The one thing worth checking here
A 3.x line receiving a patch while 5.x is current looks like the classic "abandoned line suddenly moving" red flag. It isn't — the maintainer publishes and supports three lines in parallel, and 3.15.2 is precisely the published head of the legacy one:
v3-legacy: 3.15.2 ← this bump
v4-legacy: 4.3.2
latest: 5.4.1
So this is routine backport maintenance of a supported line, not a resurrection.
Supply chain
| Check | Result |
|---|---|
| Publisher | vitaly — the long-standing nodeca maintainer, consistent with this package's history |
| Repository | git+https://github.com/nodeca/js-yaml.git — matches the declared field |
| Install hooks | none — only a test script; no preinstall / install / postinstall / prepare |
| Published | 2026-08-26T20:53:50Z |
nodeca/js-yaml publishes no GitHub releases at all — tags are its release mechanism — so the absence of one here is the project's norm rather than a missing artefact.
Scope and impact
Lockfile-only, so nothing this package imports directly changes. Dev-scope, meaning it does not reach consumers of this library at all.
CI
Green across the whole matrix — 16.x, 18.x, 20.x, 22.x, 24.x, plus lint and coverage.
Bumps js-yaml from 3.14.2 to 3.15.2.
Changelog
Sourced from js-yaml's changelog.
Commits
5c45bd63.15.2 released5a708f9dist rebuild3485bc0Backport merge limits from v5.4.1f34812fUpdate .gitignoreab85ae23.15.1 released30a5e76dist rebuild22a8071Backport quadratic complexity fix for !!omapc34b6c43.15.0 released21e13d3dist rebuild4165c62Add v3-legacy tag for publishDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill 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.