Repository navigation
chore(deps): bump nx from 22.7.7 to 22.7.12 - #6857
Open
dependabot[bot] wants to merge 1 commit into
Open
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [nx](https://github.com/nrwl/nx/tree/HEAD/packages/nx) from 22.7.7 to 22.7.12. - [Release notes](https://github.com/nrwl/nx/releases) - [Commits](https://github.com/nrwl/nx/commits/22.7.12/packages/nx) --- updated-dependencies: - dependency-name: nx dependency-version: 22.7.12 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
requested review from
alwx,
antonis and
lucas-zimerman
as code owners
October 8, 2026 12:14
Contributor
Semver Impact of This PR⚪ None (no version bump detected) 📋 Changelog PreviewThis is how your changes will appear in the changelog.
Plus 2 more 🤖 This preview updates automatically when you update the PR. |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit f06738c. Configure here.
| balanced-match: "npm:^4.0.2" | ||
| checksum: 10c0/73304caafd00fdc5b0168e693ac15bf25b6357dec76d1195fcd628fe2cf99c46f9c889a7ecfa3cfe236dbd2d5ce3e27a6ccc4370b46d475d0d19081e11f86019 | ||
| languageName: node | ||
| linkType: hard |
There was a problem hiding this comment.
Vulnerable brace-expansion bypasses resolutions
Medium Severity
The nx 22.7.12 bump now depends on exact brace-expansion@5.0.8, which is not covered by the existing Yarn resolutions that remap 5.0.6 and the ^5.0.x ranges to ^5.0.9. That leaves vulnerable 5.0.8 (CVE-2026-69152) in the lockfile. Flagged from the dependency-update review guidance.
Additional Locations (1)
Triggered by project rule: PR Review Guidelines for Cursor Bot
Reviewed by Cursor Bugbot for commit f06738c. Configure here.
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 nx from 22.7.7 to 22.7.12.
Release notes
Sourced from nx's releases.
... (truncated)
Commits
7c5b4dcdocs(core): correct the NX_MAX_MESSAGE_SIZE row and drop a stale clause3163430chore(core): format daemon client with prettierab613f7chore(core): satisfy cargo fmt on the backported hash planner1cffd59fix(core): avoid mutating target options when resolving configurations (#36934)8d81ae2fix(core): reduce task hashing memory usage on large workspaces (#36267)bfd3e51fix(core): share workspace fileset hash results instead of deep-cloning per t...02f82facleanup(core): persist file-set hash caches on the TaskHasher instance (#36118)2c34a3bfix(core): remove redundantallWorkspaceFilesfrom the project graph pipeli...73a415bfix(core): fall back to v8 for oversized daemon responses and length-prefix t...a25009dfix(core): intern hash instructions in a pool and plan with id lists (#36249)Dependabot 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.