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

chore(deps-dev): bump vitest from 1.0.1 to 1.2.0 #44

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 15, 2024

Bumps vitest from 1.0.1 to 1.2.0.

Release notes

Sourced from vitest's releases.

v1.2.0

   🚀 Features

   🐞 Bug Fixes

    View changes on GitHub

v1.1.3

   🐞 Bug Fixes

    View changes on GitHub

... (truncated)

Commits

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 1.0.1 to 1.2.0.
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v1.2.0/packages/vitest)

---
updated-dependencies:
- dependency-name: vitest
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jan 15, 2024
Copy link

stackblitz bot commented Jan 15, 2024

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

Copy link

Pull Request Review Markdown Doc

Hey there! 👋 Here's a summary of the previous results for the Pull Request review. Let's break it down into different sections:

Changes

  1. Updated the version of vitest from 1.0.1 to 1.2.0. You can find the release notes here.
    • Commits related to this update can be found here.

Suggestions

  • Consider using the latest version of typescript (5.3.2).
  • Update the specifier and version of vitest to match the other devDependencies (line 56).
  • Update the specifier and version of @vitest/expect to match the other dependencies (line 971).
  • Update the specifier and version of estree-walker to match the other devDependencies (line 1878).
  • Update the specifier and version of vite-node to match the other dependencies (line 3355).
  • Update the specifier and version of @vitest/expect, @vitest/runner, @vitest/snapshot, @vitest/spy, @vitest/utils, acorn-walk, and vite-node to match the other dependencies (line 3438).

Bugs

  • Potential bug: Check the file package.json at line 40, where the vitest version was updated.

Improvements

  • Refactoring suggestion: In the file package.json, consider using a variable to store the vitest version like this:
"vitest": "^1.2.0"

Rating

Overall rating: 7.5 out of 10

  • The code is fairly readable, but could benefit from some refactoring.
  • Performance and security seem to be fine.

That's it for the summary! Let me know if you need any further assistance. 😄

Copy link

Updated dependencies detected. Learn more about Socket for GitHub ↗︎

Packages Version New capabilities Transitives Size Publisher
vitest 1.0.1...1.2.0 None +1/-1 1.54 MB oreanno

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.

Issue Package Version Note Source
Major refactor vitest 1.2.0
  • Change Percentage: 82.57
  • Current Line Count: 35979
  • Previous Line Count: 35337
  • Lines Changed: 58886

Next steps

What is a major refactor?

Package has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.

Consider waiting before upgrading to see if any issues are discovered, or be prepared to scrutinize any bugs or subtle changes the major refactor may bring. Publishers my consider publishing beta versions of major refactors to limit disruption to parties interested in the new changes.

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 package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore vitest@1.2.0

Copy link
Contributor Author

dependabot bot commented on behalf of github Jan 22, 2024

Superseded by #49.

@dependabot dependabot bot closed this Jan 22, 2024
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/vitest-1.2.0 branch January 22, 2024 04:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants