Bump @nx/next from 19.5.7 to 20.3.1 #4690
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [@nx/next](https://github.com/nrwl/nx/tree/HEAD/packages/next) from 19.5.7 to 20.3.1. - [Release notes](https://github.com/nrwl/nx/releases) - [Commits](https://github.com/nrwl/nx/commits/20.3.1/packages/next) --- updated-dependencies: - dependency-name: "@nx/next" dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
Sorry, only users with push access can use that command. |
![codacy-production[bot]](https://avatars.githubusercontent.com/in/56611?s=60&v=4){kind=small}
| } | ||
| } | ||
| }, | ||
| "node_modules/@nx/module-federation/node_modules/webpack": { |
There was a problem hiding this comment.
The issue identified by the Trivy linter is related to a security vulnerability in the webpack package version 5.88.0. Specifically, it is a DOM Clobbering vulnerability in the AutoPublicPathRuntimeModule, which can potentially allow an attacker to manipulate the DOM in a way that could lead to security issues, such as unauthorized access to sensitive data or execution of malicious scripts. The recommended fix is to update webpack to a version that has addressed this vulnerability, specifically version 5.94.0 or later.
To resolve this issue, you should update the dependency in your package.json file to the secure version. Here is the single line code suggestion to fix the issue:
| "node_modules/@nx/module-federation/node_modules/webpack": { | |
| "webpack": "^5.94.0", |
This comment was generated by an experimental AI tool.
Bumps @nx/next from 19.5.7 to 20.3.1.
Release notes
Sourced from
@nx/next's releases.... (truncated)
Commits
84617b0fix(js): only add typescript project references for explicit dependencies in ...7a583dacleanup(repo): remove unused dependencies (#27676)b9c0e3dfeat(eslint): rename eslint.config.js to eslint.config.cjs to resolve them as...d05f30ffix(core): Adding react apps/libs to workspaces so they can be referenced. (#...f922e2bfix(misc): fix misc generation issues with the ts solution setup (#29350)99a0e7cfix(misc): ensuretsBuildInfoFileis generated insideoutDir(#29343)cfcd4d1fix(react): fix tailwind for react library and component (#29319)726c07dfix(webpack): Add useTsconfigPaths to app-webpack-plugin (#29291)28c53f9feat(misc): handle artifact generators'pathoptions including file extensi...ec5a5e6feat(react): update app and lib generators to support new TS solution setup (...Maintainer changes
This version was pushed to npm by jameshenry, a new releaser for
@nx/nextsince your current version.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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@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)