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.

Sign up for GitHub

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

Jump to bottom

[Snyk] Upgrade: , react-scripts #140

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

[Snyk] Upgrade: , react-scripts #140

wants to merge 1 commit into from

Conversation

officialmofabs
Copy link
Collaborator

snyk-top-banner

Snyk has created this PR to upgrade multiple dependencies.

👯 The following dependencies are linked and will therefore be updated together.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

Name Versions Released on

@testing-library/jest-dom
from 5.12.0 to 5.17.0 | 12 versions ahead of your current version | a year ago
on 2023-07-18
react-scripts
from 5.0.0 to 5.0.1 | 1 version ahead of your current version | 2 years ago
on 2022-04-12

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
high severity Denial of Service (DoS)
SNYK-JS-DECODEURICOMPONENT-3149970		 696 Proof of Concept
critical severity Incomplete List of Disallowed Inputs
SNYK-JS-BABELTRAVERSE-5962462		 696 Proof of Concept
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-MINIMATCH-3050818		 696 No Known Exploit
Release notes
Package name: @testing-library/jest-dom from @testing-library/jest-dom GitHub release notes
Package name: react-scripts
  • 5.0.1 - 2022-04-12

    5.0.1 (2022-04-12)

    Create React App 5.0.1 is a maintenance release that improves compatibility with React 18. We've also updated our templates to use createRoot and relaxed our check for older versions of Create React App.

    Migrating from 5.0.0 to 5.0.1

    Inside any created project that has not been ejected, run:

    npm install --save --save-exact react-scripts@5.0.1

    or

    yarn add --exact react-scripts@5.0.1

    🐛 Bug Fix

    💅 Enhancement

    • cra-template-typescript, cra-template, react-scripts
    • cra-template-typescript, cra-template
    • eslint-config-react-app

    📝 Documentation

    🏠 Internal

    Committers: 11

  • 5.0.0 - 2021-12-14

    v5.0.0 (2021-12-14)

    Create React App 5.0 is a major release with several new features and the latest version of all major dependencies.

    Thanks to all the maintainers and contributors who worked so hard on this release! 🙌

    Highlights

    • webpack 5 (#11201)
    • Jest 27 (#11338)
    • ESLint 8 (#11375)
    • PostCSS 8 (#11121)
    • Fast Refresh improvements and bug fixes (#11105)
    • Support for Tailwind (#11717)
    • Improved package manager detection (#11322)
    • Unpinned all dependencies for better compatibility with other tools (#11474)
    • Dropped support for Node 10 and 12

    Migrating from 4.0.x to 5.0.0

    Inside any created project that has not been ejected, run:

    npm install --save --save-exact react-scripts@5.0.0

    or

    yarn add --exact react-scripts@5.0.0

    NOTE: You may need to delete your node_modules folder and reinstall your dependencies by running npm install (or yarn) if you encounter errors after upgrading.

    If you previously ejected but now want to upgrade, one common solution is to find the commits where you ejected (and any subsequent commits changing the configuration), revert them, upgrade, and later optionally eject again. It’s also possible that the feature you ejected for is now supported out of the box.

    Breaking Changes

    Like any major release, react-scripts@5.0.0 contains a number of breaking changes. We expect that they won't affect every user, but we recommend you look over this section to see if something is relevant to you. If we missed something, please file a new issue.

    Dropped support for Node 10 and 12

    Node 10 reached End-of-Life in April 2021 and Node 12 will be End-of-Life in April 2022. Going forward we will only support the latest LTS release of Node.js.

    Full Changelog

    💥 Breaking Change

    • create-react-app
    • babel-preset-react-app, cra-template-typescript, cra-template, create-react-app, eslint-config-react-app, react-app-polyfill, react-dev-utils, react-error-overlay, react-scripts
    • eslint-config-react-app, react-error-overlay, react-scripts
    • react-scripts

    🐛 Bug Fix

    💅 Enhancement

    • react-scripts
      • #11717 Add support for Tailwind (@ iansu)
      • #8227 Add source-map-loader for debugging into original source of node_modules libraries that contain sourcemaps (@ justingrant)
      • #10499 Remove ESLint verification when opting-out (@ mrmckeb)
    • eslint-config-react-app, react-error-overlay, react-scripts
    • create-react-app
    • react-dev-utils
    • create-react-app, react-scripts

    📝 Documentation

    🏠 Internal

    • Other
    • create-react-app
    • babel-plugin-named-asset-import, babel-preset-react-app, confusing-browser-globals, create-react-app, react-app-polyfill, react-dev-utils, react-error-overlay, react-scripts
    • react-scripts
    • babel-plugin-named-asset-import, confusing-browser-globals, create-react-app, eslint-config-react-app, react-dev-utils, react-error-overlay, react-scripts
    • confusing-browser-globals, cra-template-typescript, cra-template, create-react-app
    • react-error-overlay, react-scripts
    • babel-preset-react-app, cra-template-typescript, cra-template, create-react-app, eslint-config-react-app, react-app-polyfill, react-dev-utils, react-error-overlay, react-scripts

    🔨 Underlying Tools

    • react-dev-utils, react-scripts
    • react-scripts
    • babel-plugin-named-asset-import, confusing-browser-globals, create-react-app, react-dev-utils, react-error-overlay, react-scripts
      • #11338 Upgrade jest and related packages from 26.6.0 to 27.1.0 (@ krreet)
    • eslint-config-react-app, react-error-overlay, react-scripts
    • babel-preset-react-app, react-dev-utils, react-error-overlay, react-scripts
    • react-dev-utils

    Committers: 34

from react-scripts GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.

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

For more information:

@snyk-bot
fix: upgrade multiple dependencies with Snyk
cad0710 
Snyk has created this PR to upgrade:
  - @testing-library/jest-dom from 5.12.0 to 5.17.0.
    See this package in npm: https://www.npmjs.com/package/@testing-library/jest-dom
  - react-scripts from 5.0.0 to 5.0.1.
    See this package in npm: https://www.npmjs.com/package/react-scripts

See this project in Snyk:
https://app.snyk.io/org/supportigedevteam.onmicrosoft.com/project/92d033df-ae43-4bbe-88d8-c446bfbd4a35?utm_source=github&utm_medium=referral&page=upgrade-pr
@socket-security Socket Security
Copy link

Report too large to display inline

View full report↗︎

@socket-security Socket Security
Copy link

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert Package NoteSourceCI
Critical CVE npm/loader-utils@1.4.0 ⚠︎

View full report↗︎

Next steps

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore npm/loader-utils@1.4.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@officialmofabs @snyk-bot