build(deps): bump js-yaml from 4.1.1 to 4.3.1 in /docs - #427
build(deps): bump js-yaml from 4.1.1 to 4.3.1 in /docs#427dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [js-yaml](https://github.com/nodeca/js-yaml) from 4.1.1 to 4.3.1. - [Changelog](https://github.com/nodeca/js-yaml/blob/4.3.1/CHANGELOG.md) - [Commits](nodeca/js-yaml@4.1.1...4.3.1) --- updated-dependencies: - dependency-name: js-yaml dependency-version: 4.3.1 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
|
Superseded by #435, which makes the same bump on The advisory is real and |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
…427) (#435) js-yaml 4.3.0 is still in the vulnerable range of the high-severity quadratic-CPU advisory: 4.3.0 fixed the merge-key chain variant, and 4.3.1 backports the same guard to `!!omap` duplicate-key resolution. Exposure here is a build-time parse of our own frontmatter, so the practical risk is limited to someone who can already commit — the bump is one line and closes a high alert on a public repo. Dependabot's own PR targeted `master`, which only fast-forwards from `dev`, so a commit there would break the next FF. The three lines are hand-edited rather than installed: `npm install js-yaml@4.3.1` promotes it to a direct dependency in package.json and strips `"libc"` platform metadata from optional entries, and `npm update` strips the same. Validated with `npm ci` (0 vulnerabilities) and a full `npm run build` (31 pages). postcss needs nothing: `dev` is at 8.5.23, which is the patched version for both open postcss advisories. Nine of the ten open Dependabot alerts describe `master`'s lockfile, not `dev`'s, and clear at the next release fast-forward.
1 participant
Bumps js-yaml from 4.1.1 to 4.3.1.
Changelog
Sourced from js-yaml's changelog.
... (truncated)
Commits
86e91b84.3.1 releasedc3cc4b0Backport quadratic complexity fix for !!omap33d05b54.3.0 released663bfabDrop demo publish, to not override new v5 one.1cb8c7bAdd v4-legacy tag for publish02f27afRestore umd builds back to es58be84edFix es5 compatibility59423c6ReplacemaxMergeSeqLengthoption withmaxTotalMergeKeys(more robust). Ba...6842ef6doc polish590dbab4.2.0 releasedDependabot 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.