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 @testing-library/react from 14.3.1 to 16.0.0 #3

Merged
merged 1 commit into from
Aug 17, 2024
Merged

[Snyk] Upgrade @testing-library/react from 14.3.1 to 16.0.0 #3

merged 1 commit into from
Aug 17, 2024

Conversation

OKEAMAH
Copy link
Member

@OKEAMAH OKEAMAH commented Aug 17, 2024

snyk-top-banner

Snyk has created this PR to upgrade @testing-library/react from 14.3.1 to 16.0.0.

ℹ️ 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.

⚠️ Warning: This PR contains major version upgrade(s), and may be a breaking change.

  • The recommended version is 9 versions ahead of your current version.

  • The recommended version was released on 2 months ago.

Release notes
Package name: @testing-library/react
  • 16.0.0 - 2024-06-03

    16.0.0 (2024-06-03)

    Features

    • Move @ testing-library/dom and @ types/react-dom to peer dependencies (#1305) (a4744fa)

    BREAKING CHANGES

    • @ testing-library/dom was moved to a peer dependency and needs to be explicitly installed. This reduces the chance of having conflicting versions of @ testing-library/dom installed that frequently caused bugs when used with @ testing-library/user-event. We will also be able to allow new versions of @ testing-library/dom being used without a SemVer major release of @ testing-library/react by just widening the peer dependency.
      @ types/react-dom needs to be installed if you're typechecking files using @ testing-library/react.
  • 15.0.7 - 2024-05-07

    15.0.7 (2024-05-07)

    Bug Fixes

    • Ensure act is not any when React.act is not declared (#1323) (c1f2957)
  • 15.0.6 - 2024-05-01

    15.0.6 (2024-05-01)

    Bug Fixes

  • 15.0.5 - 2024-04-26

    15.0.5 (2024-04-26)

    Bug Fixes

    • Stop restricting container option based on hydrate (#1313) (d143f46)
  • 15.0.4 - 2024-04-23

    15.0.4 (2024-04-23)

    Bug Fixes

    • Ensure renderHook options extend options for render (#1308) (48282c2)
  • 15.0.3 - 2024-04-23

    15.0.3 (2024-04-23)

    Bug Fixes

    • Don't raise TypeScript errors when hydating document (#1304) (067d0c6)
  • 15.0.2 - 2024-04-13

    15.0.2 (2024-04-13)

    Bug Fixes

  • 15.0.1 - 2024-04-11

    15.0.1 (2024-04-11)

    Bug Fixes

  • 15.0.0 - 2024-04-10

    15.0.0 (2024-04-10)

    Release

    BREAKING CHANGES

    • Minimum supported Node.js version is 18.0
    • New version of @ testing-library/dom changes various roles. Check out the changed tests in testing-library/dom-testing-library@2c57055 to get an overview about what changed.
  • 14.3.1 - 2024-04-11

    14.3.1 (2024-04-11)

    Bug Fixes

from @testing-library/react GitHub release notes

Important

  • Warning: This PR contains a major version upgrade, and may be a breaking change.
  • 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.

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
feat: upgrade @testing-library/react from 14.3.1 to 16.0.0
73665bc 
Snyk has created this PR to upgrade @testing-library/react from 14.3.1 to 16.0.0.

See this package in npm:
@testing-library/react

See this project in Snyk:
https://app.snyk.io/org/okeamah/project/bc7fa2ad-7386-45f1-96fe-f67f02938026?utm_source=github&utm_medium=referral&page=upgrade-pr
sourcery-ai[bot]
sourcery-ai bot reviewed Aug 17, 2024
View reviewed changes
Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have skipped reviewing this pull request. Here's why:

  • It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
  • We don't review packaging changes - Let us know if you'd like us to change this.

@socket-security Socket Security
Copy link

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@metamask/test-dapp@8.1.0 None 0 4.46 MB gudahtt
npm/@playwright/test@1.40.1 Transitive: environment, eval, filesystem, network, shell, unsafe +2 10.1 MB dgozman-ms
npm/@synthetixio/synpress@3.7.2-beta.9 environment, filesystem Transitive: eval, network, shell, unsafe +941 132 MB drptbl
npm/dotenv@16.3.1 environment, filesystem 0 71.6 kB motdotla
npm/prom-client@15.0.0 filesystem, network, unsafe +3 3.7 MB simenb
npm/serve@14.2.1 Transitive: environment, eval, filesystem, network, shell, unsafe +89 4.43 MB vercel-release-bot
npm/typescript@5.3.3 None 0 32 MB typescript-bot
npm/viem@1.20.0 network Transitive: environment +9 10.2 MB jmoxey

🚮 Removed packages: npm/@babel/eslint-parser@7.23.10, npm/@changesets/changelog-github@0.4.8, npm/@changesets/cli@2.27.1, npm/@eth-optimism/contracts-periphery@1.0.8, npm/@eth-optimism/contracts@0.6.0, npm/@ethereumjs/rlp@5.0.2, npm/@ethersproject/abi@5.7.0, npm/@ethersproject/abstract-provider@5.7.0, npm/@ethersproject/abstract-signer@5.7.0, npm/@ethersproject/address@5.7.0, npm/@ethersproject/bignumber@5.7.0, npm/@ethersproject/bytes@5.7.0, npm/@ethersproject/constants@5.7.0, npm/@ethersproject/contracts@5.7.0, npm/@ethersproject/keccak256@5.7.0, npm/@ethersproject/properties@5.7.0, npm/@ethersproject/rlp@5.7.0, npm/@ethersproject/transactions@5.7.0, npm/@ethersproject/web@5.7.1, npm/@nomiclabs/hardhat-ethers@2.2.3, npm/@nomiclabs/hardhat-waffle@2.0.1, npm/@nomiclabs/hardhat-waffle@2.0.6, npm/@sentry/node@7.99.0, npm/@swc/core@1.4.6, npm/@testing-library/jest-dom@6.4.2, npm/@testing-library/react-hooks@8.0.1, npm/@testing-library/react@14.2.1, npm/@types/chai-as-promised@7.1.8, npm/@types/chai@4.3.11, npm/@types/change-case@2.3.1, npm/@types/dateformat@5.0.0, npm/@types/glob@8.1.0, npm/@types/mocha@10.0.6, npm/@types/morgan@1.9.9, npm/@types/node@20.11.17, npm/@types/pino-multi-stream@5.1.6, npm/@types/pino@7.0.5, npm/@types/semver@7.5.7, npm/@typescript-eslint/eslint-plugin@6.21.0, npm/@typescript-eslint/parser@6.21.0, npm/@vitest/coverage-istanbul@1.2.2, npm/@wagmi/cli@2.1.4, npm/@wagmi/core@2.6.3, npm/abitype@1.0.2, npm/bcfg@0.2.1, npm/body-parser@1.20.2, npm/chai-as-promised@7.1.1, npm/chai@4.3.10, npm/change-case@4.1.2, npm/dateformat@4.5.1, npm/depcheck@1.4.7, npm/doctoc@2.2.1, npm/dotenv@16.4.5, npm/envalid@8.0.0, npm/eslint-config-prettier@9.1.0, npm/eslint-config-standard@16.0.3

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
Install scripts npm/core-js@2.6.12
  • Install script: postinstall
  • Source: node -e "try{require('./postinstall')}catch(e){}"
 🚫
Install scripts npm/cypress@12.17.3
  • Install script: postinstall
  • Source: node index.js --exec install
 🚫
Install scripts npm/core-js@3.34.0
  • Install script: postinstall
  • Source: node -e "try{require('./postinstall')}catch(e){}"
 🚫

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

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/core-js@2.6.12
  • @SocketSecurity ignore npm/cypress@12.17.3
  • @SocketSecurity ignore npm/core-js@3.34.0

@OKEAMAH OKEAMAH merged commit 9227843 into celestia-develop Aug 17, 2024
10 of 12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@sourcery-ai Sourcery AI sourcery-ai left review comments

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
@OKEAMAH @snyk-bot