Repository navigation
Bump js-yaml from 4.3.2 to 5.4.2 - #28
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [js-yaml](https://github.com/nodeca/js-yaml) from 4.3.2 to 5.4.2. - [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md) - [Commits](nodeca/js-yaml@4.3.2...5.4.2) --- updated-dependencies: - dependency-name: js-yaml dependency-version: 5.4.2 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Closing: js-yaml 5 can't be adopted yet.
Done in c272f88: Dependabot now ignores js-yaml major updates, with the reason in |
Dependabot PR #28 (js-yaml 4 -> 5) breaks every check: js-yaml 5 has no default export, and it removed safeLoad, which gray-matter calls at load time through the package.json override, so Eleventy itself would crash. Our tools must also parse frontmatter with the same js-yaml major as Eleventy, or validation and the site could disagree about a value. - dependabot.yml ignores js-yaml semver-major updates, with the reason. - tools/lib/content.mjs imports { load }, which works in js-yaml 4 and 5, so the eventual upgrade is a version bump only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
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. |
Bumps js-yaml from 4.3.2 to 5.4.2.
Changelog
Sourced from js-yaml's changelog.
... (truncated)
Commits
494400b5.4.2 released6d8adb4FixforceQuotesquoting non-string scalars, #798e5a3ba05.4.1 releasede54dea3Hard-limit merge sequence size to 100dfd3a29Cleanup 6a8e05f, #7976a8e05ffix: count empty merge sources against maxTotalMergeKeys (#797)6b4ff5e5.4.0 released3b3625eUpdate changelog4f25a74Fix file name3bd003bExpose new scalar styling APIDependabot 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)