build(deps): bump js-yaml from 4.3.1 to 4.3.2 in /frontend/infrastructure - #101
Open
dependabot[bot] wants to merge 2 commits into
Open
build(deps): bump js-yaml from 4.3.1 to 4.3.2 in /frontend/infrastructure#101dependabot[bot] wants to merge 2 commits into
dependabot[bot] wants to merge 2 commits into
Conversation
Bumps [js-yaml](https://github.com/nodeca/js-yaml) from 4.3.1 to 4.3.2. - [Changelog](https://github.com/nodeca/js-yaml/blob/4.3.2/CHANGELOG.md) - [Commits](nodeca/js-yaml@4.3.1...4.3.2) --- updated-dependencies: - dependency-name: js-yaml dependency-version: 4.3.2 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
…ure/js-yaml-4.3.2
11 tasks
andreameroni
approved these changes
Sep 10, 2026
raphaho
added a commit
that referenced
this pull request
Sep 10, 2026
js-yaml before 4.3.2 is affected by CVE-2026-84375 (High): a crafted YAML document using merge keys with empty sources causes excessive processing in lib/loader.js, giving a denial of service. Fixed upstream in 4.3.2. The advisory applies to both frontend/infrastructure/yarn.lock and frontend/web/yarn.lock, and both pin js-yaml through a resolutions entry rather than a direct dependency, so each workspace needs the resolution raised and its lockfile refreshed. js-yaml is the only resolution that moves in either lockfile. Refreshing the lockfile alongside the manifest is the part that matters. Raising the resolutions entry on its own leaves the lockfile resolving 4.3.1, so nothing installed changes and the advisory stays open, while `yarn install --immutable` begins failing with YN0028 because the lockfile no longer satisfies the manifest. Verified in both workspaces: - `yarn install --immutable` passes in frontend/infrastructure and frontend/web, and both lockfiles resolve js-yaml 4.3.2. - frontend/web, the full CI sequence: `yarn npm audit --severity high` reports no suggestions, lint passes with no errors, `test:ci` passes 9 tests and `build` transforms 5488 modules. - frontend/infrastructure is not covered by ci.yml, which declares only the backend and frontend/web working directories, so it was checked by hand: `build` (tsc) passes, `lint` passes with 0 errors and the same 72 warnings as the base commit, and `test:ci` passes 46 tests across 7 suites. Supersedes #101, which raised the resolutions entry in frontend/infrastructure without refreshing that lockfile and left frontend/web untouched. Co-authored-by: Raphael Hofer <raphaho@amazon.com>
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
2 participants
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.3.1 to 4.3.2.
Changelog
Sourced from js-yaml's changelog.
Commits
79ca68d4.3.2 releasedd90b661Backport merge limits from v5.4.1Dependabot 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.