Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Security upgrade @nrwl/next from 13.10.6 to 15.8.8 #49

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

talhabalaj
Copy link
Contributor

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

✨ Snyk has automatically assigned this pull request, set who gets assigned.

As this is a private repository, Snyk-bot does not have access. Therefore, this PR has been created automatically, but appears to have been created by a real user.

Changes included in this PR

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
    • package.json

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
high severity 661/1000
Why? Recently disclosed, Has a fix available, CVSS 7.5
Inefficient Regular Expression Complexity
SNYK-JS-MICROMATCH-6838728
Yes No Known Exploit
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS)
SNYK-JS-MINIMATCH-3050818
Yes No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Commit messages
Package name: @nrwl/next The new version differs by 250 commits.
  • 6711c0b chore(misc): publish 15.8.8
  • 867180c fix(nextjs): set correct distDir when running production server through Nx (#15861)
  • f88cc40 fix(nextjs): add missing express dependencies to next plugin (#15854)
  • 54bc5ca fix(nextjs): add missing style deps for less and stylus (#15839)
  • c94c00d fix(core): fix broken path elevation in npm lockfile pruning (#15833)
  • cf785ef fix(nextjs): produce correct next.config.js file for production server (#15824)
  • 7a57f59 fix(nx-plugin): allow some customization when running nx-plugins (#15438)
  • f85c2df fix(core): move the daemon stop log out of client (#15783)
  • 7c4f043 fix(nextjs): handle buildable libs correctly (#15795)
  • 53ba54f fix(bundling): respect --sourcemap option for esbuild (#15778)
  • b05f540 fix(node): align proxy port with default api port (#15754)
  • cb0a2f1 fix(angular): fix wrong tsconfig option name in webpack-dev-server implementation (#15765)
  • efd89aa fix(core): misc daemon fixes (#15472)
  • 91b7344 fix(core): add warning if running on an outdated global install (#15443)
  • d863930 docs(storybook): include note for older name of flag (#15662)
  • 71b96cf fix(core): combine serial and parallel execution + forward sigint to child process (#13885)
  • f300d35 chore(misc): publish 15.8.7
  • 58c4e2f chore(repo): fix craco e2e tests
  • aabd76f fix(react): fix merge conflict for import
  • 143d8d3 fix(core): fix NX_TASK_TARGET_CONFIGURATION being set to 'null' (#15725)
  • 7d34a05 fix(react): fix next import (#15724)
  • 47fdc35 fix(core): nx migrate should accept tags other than latest and next for community packages (#15673)
  • 3811844 fix(core): wildcard implicit dependency should support scoped project names (#15699)
  • b81c398 fix(nextjs): refactor how webpack config is loaded with nextjs (#15650)

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

👩‍💻 Set who automatically gets assigned

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Inefficient Regular Expression Complexity

@talhabalaj talhabalaj self-assigned this May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants