chore(deps-dev): bump js-yaml from 4.1.1 to 4.3.0 in /evals - #103
Open
dependabot[bot] wants to merge 1 commit into
Open
chore(deps-dev): bump js-yaml from 4.1.1 to 4.3.0 in /evals#103dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Skill eval results
Only suites whose source actually changed since their last recorded score were re-run. Soft-failing while we stabilise the baseline. |
Bumps [js-yaml](https://github.com/nodeca/js-yaml) from 4.1.1 to 4.3.0. - [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md) - [Commits](nodeca/js-yaml@4.1.1...4.3.0) --- updated-dependencies: - dependency-name: js-yaml dependency-version: 4.3.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/evals/js-yaml-4.3.0
branch
from
July 28, 2026 19:33
6964dde to
30950f4
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps js-yaml from 4.1.1 to 4.3.0.
Changelog
Sourced from js-yaml's changelog.
... (truncated)
Commits
33d05b54.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 releasedf944dc5Add package.json funding fieldf692719Changelog updateNote
Low Risk
Dev-only dependency bump in the evals package with no application runtime impact; main change is a security hardening backport in YAML parsing.
Overview
Bumps the
evalsdev dependencyjs-yamlfrom 4.1.1 to 4.3.0 inpackage.jsonand refreshespackage-lock.json.4.3.0 backports the
maxTotalMergeKeysloader option (YAML merge<<limits), which is the main functional/security reason for the upgrade. Eval tooling that parses YAML (e.g.build-pr-fixture.jsviajs-yaml) picks up that behavior on the hoisted install.The lockfile diff also includes transitive churn from the install (e.g. hoisted
@anthropic-ai/sdk0.115.0 withstandardwebhooks, a nestedpromptfoocopy of SDK 0.92.0, and many packages no longer markeddev: true). Those are lockfile resolution side effects, not separate product changes.Reviewed by Cursor Bugbot for commit 30950f4. Bugbot is set up for automated code reviews on this repo. Configure here.