Bump js-yaml from 3.14.2 to 3.15.0 - #79644
Conversation
|
Size Change: 0 B Total Size: 7.61 MB |
commented
Jun 29, 2026
|
Flaky tests detected in ed4b971. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/28392143252
|
Bumps [js-yaml](https://github.com/nodeca/js-yaml) from 3.14.2 to 3.15.0. - [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md) - [Commits](nodeca/js-yaml@3.14.2...3.15.0) --- updated-dependencies: - dependency-name: js-yaml dependency-version: 3.15.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
ed4b971 to
25cde2d
Compare
commented
Jun 30, 2026
|
@copilot Analyze how Additionally, evaluate whether this dependency is even required at all or can be dropped in favor of some native feature, or if the functionality is duplicated by another dependency. |
commented
Jun 30, 2026
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
commented
Jun 30, 2026
Usage analysis
Impact of 3.14.2 → 3.15.0 The sole change in 3.15.0 is a security backport of the Can js-yaml be dropped? Not at this time:
One longer-term option worth noting: js-yaml v3 is now at its final release (3.15.0 is the last planned v3 tag — the project has moved to v4/v5). Upgrading to v4 would be the natural next step for |
Bumps js-yaml from 3.14.2 to 3.15.0.
Changelog
Sourced from js-yaml's changelog.
... (truncated)
Commits
c34b6c43.15.0 released21e13d3dist rebuild4165c62Add v3-legacy tag for publishd8ff750Add package lock24f13e7AddedmaxTotalMergeKeys(10000) loader option (v5 backport)