build(deps): bump js-yaml from 4.2.0 to 4.3.0 in /tests/functional#2467
build(deps): bump js-yaml from 4.2.0 to 4.3.0 in /tests/functional#2467dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [js-yaml](https://github.com/nodeca/js-yaml) from 4.2.0 to 4.3.0. - [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md) - [Commits](nodeca/js-yaml@4.2.0...4.3.0) --- updated-dependencies: - dependency-name: js-yaml dependency-version: 4.3.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
Hello dependabot[bot],My role is to assist you with the merge of this Available options
Available commands
Status report is not available. The following options are set: bypass_author_approval, bypass_jira_check |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
The following options are set: bypass_author_approval, bypass_jira_check |
There was a problem hiding this comment.
Dependency Bump Evaluation
Version change: 4.2.0 -> 4.3.0 (minor)
Breaking changes: None — the v5.x breaking changes in the changelog do not apply to this v4-branch bump
Security concerns: None — this bump improves security by backporting maxTotalMergeKeys (DoS mitigation for crafted YAML merge keys)
Impact on codebase: js-yaml is used in one place (tests/functional/testResourcesSetup/config.ts:94) via a basic yaml.load(content) call with no custom options. The new maxTotalMergeKeys default (10000) is a sensible limit that will not affect normal config loading. No usage of maxMergeSeqLength or maxAliases found anywhere in the repo.
Recommendation: SAFE TO MERGE
— Claude Code
Bumps js-yaml from 4.2.0 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 polishDependabot 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.