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 the major-updates group across 1 directory with 5 updates #128

Closed

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Aug 19, 2024

Bumps the major-updates group with 5 updates in the / directory:

Package From To
@types/node 20.14.10 22.4.1
@vitest/coverage-istanbul 1.6.0 2.0.5
@vitest/ui 1.6.0 2.0.5
npm-check-updates 16.14.20 17.0.6
vitest 1.6.0 2.0.5

Updates @types/node from 20.14.10 to 22.4.1

Commits

Updates @vitest/coverage-istanbul from 1.6.0 to 2.0.5

Release notes

Sourced from @​vitest/coverage-istanbul's releases.

v2.0.5

   🚀 Features

  • Introduce experimental reported tasks  -  by @​sheremet-va in vitest-dev/vitest#6149 (13d85)
    • This is part of the experimental API and doesn't follow semver. We are hoping to stabilize it for 2.1. If you are working with custom reporters, give this a go!

   🐞 Bug Fixes

    View changes on GitHub

v2.0.4

   🐞 Bug Fixes

    View changes on GitHub

v2.0.3

   🚀 Features

   🐞 Bug Fixes

... (truncated)

Commits
  • 99452a7 chore: release v2.0.5
  • 400481f chore: release v2.0.4
  • a852b16 refactor: enable isolatedDeclarations in snapshot and spy packages (#6146)
  • 81b8d67 chore: release v2.0.3
  • 99a12ae chore: release v2.0.2
  • 80a43d5 fix(browser): inline pretty-format and replace picocolors with tinyrainbow (#...
  • 16eb6c8 chore: release v2.0.1
  • 1b150a3 chore: release v2.0.0
  • 5611895 chore: release v2.0.0-beta.13
  • 368c137 fix(coverage): remove work-around for implicit else (#6014)
  • Additional commits viewable in compare view

Updates @vitest/ui from 1.6.0 to 2.0.5

Release notes

Sourced from @​vitest/ui's releases.

v2.0.5

   🚀 Features

  • Introduce experimental reported tasks  -  by @​sheremet-va in vitest-dev/vitest#6149 (13d85)
    • This is part of the experimental API and doesn't follow semver. We are hoping to stabilize it for 2.1. If you are working with custom reporters, give this a go!

   🐞 Bug Fixes

    View changes on GitHub

v2.0.4

   🐞 Bug Fixes

    View changes on GitHub

v2.0.3

   🚀 Features

   🐞 Bug Fixes

... (truncated)

Commits
  • 99452a7 chore: release v2.0.5
  • 13d85bd feat: introduce experimental reported tasks (#6149)
  • 3aab8a1 refactor: deprecate all config types from the main Vitest entrypoint, introdu...
  • c3ef56d chore(deps): update all non-major dependencies (#6188)
  • 400481f chore: release v2.0.4
  • f55dc00 chore(deps): update all non-major dependencies (#6046)
  • 2d62051 feat(browser): allow preview and open in the editor screenshot error from ui ...
  • 81b8d67 chore: release v2.0.3
  • 840e02f feat(ui): show all suites/tests when parent matches (#6106)
  • 958352c chore: bump unplugin-auto-import (#6094)
  • Additional commits viewable in compare view

Updates npm-check-updates from 16.14.20 to 17.0.6

Release notes

Sourced from npm-check-updates's releases.

v17.0.0

Breaking

  • Require node >= 18.18.0
  • In workspaces mode, --root is now set by default (#1353)
    • To not check the root package.json, use --no-root.
  • If you have a packageManager field in your package.json, it is now upgraded by default (#1390)
    • Use --dep prod,dev,optional for the old behavior.

v17.0.0-1

This is the first prerelease in preparation for the next major v17. It mainly involves a node engines bump and lot of internal dependency upgrades, so if you notice any regressions, please let me know!

Run npx [email protected] to test.

There are a two more breaking/high-risk changes I intend to make for the v17 release, which I will also release as prerelease versions for testing.

Thanks for your help and enjoy! 🍰

Breaking

  • Require node >= 18.18.0
  • In workspaces mode, --root is now set by default (#1353)
    • To not check the root package.json, use --no-root.
  • Convert from CommonJS to ESM (#1358)
  • Replace pacote with npm-registry-fetch (#1329)
Commits

Updates vitest from 1.6.0 to 2.0.5

Release notes

Sourced from vitest's releases.

v2.0.5

   🚀 Features

  • Introduce experimental reported tasks  -  by @​sheremet-va in vitest-dev/vitest#6149 (13d85)
    • This is part of the experimental API and doesn't follow semver. We are hoping to stabilize it for 2.1. If you are working with custom reporters, give this a go!

   🐞 Bug Fixes

    View changes on GitHub

v2.0.4

   🐞 Bug Fixes

    View changes on GitHub

v2.0.3

   🚀 Features

   🐞 Bug Fixes

... (truncated)

Commits
  • 99452a7 chore: release v2.0.5
  • 9b9bdf7 chore: remove unnecessary await (#6249)
  • 40dfad8 docs: add reported tasks docs (#6245)
  • 13d85bd feat: introduce experimental reported tasks (#6149)
  • b76a927 refactor(vitest): move public exports to public folder (#6218)
  • 56dbfa6 refactor: make a distinction between node and runtime types (#6214)
  • a48be6f fix(vitest): correctly resolve mocked node:* imports in mocks folder (#6204)
  • 3aab8a1 refactor: deprecate all config types from the main Vitest entrypoint, introdu...
  • 57d23ce docs: fix inconsistencies, remove low informative twoslash examples (#6200)
  • 8cd8272 fix(vitest): improve defineProject and defineWorkspace types (#6198)
  • Additional commits viewable in compare view

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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Summary by CodeRabbit

  • Chores
    • Updated several project dependencies to their latest versions for improved performance and security.
    • Upgraded Node.js type definitions and testing framework packages to enhance features and capabilities.

… 5 updates

Bumps the major-updates group with 5 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `20.14.10` | `22.4.1` |
| [@vitest/coverage-istanbul](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-istanbul) | `1.6.0` | `2.0.5` |
| [@vitest/ui](https://github.com/vitest-dev/vitest/tree/HEAD/packages/ui) | `1.6.0` | `2.0.5` |
| [npm-check-updates](https://github.com/raineorshine/npm-check-updates) | `16.14.20` | `17.0.6` |
| [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) | `1.6.0` | `2.0.5` |



Updates `@types/node` from 20.14.10 to 22.4.1
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

Updates `@vitest/coverage-istanbul` from 1.6.0 to 2.0.5
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v2.0.5/packages/coverage-istanbul)

Updates `@vitest/ui` from 1.6.0 to 2.0.5
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v2.0.5/packages/ui)

Updates `npm-check-updates` from 16.14.20 to 17.0.6
- [Release notes](https://github.com/raineorshine/npm-check-updates/releases)
- [Changelog](https://github.com/raineorshine/npm-check-updates/blob/main/CHANGELOG.md)
- [Commits](raineorshine/npm-check-updates@v16.14.20...v17.0.6)

Updates `vitest` from 1.6.0 to 2.0.5
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v2.0.5/packages/vitest)

---
updated-dependencies:
- dependency-name: "@types/node"
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: major-updates
- dependency-name: "@vitest/coverage-istanbul"
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: major-updates
- dependency-name: "@vitest/ui"
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: major-updates
- dependency-name: npm-check-updates
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: major-updates
- dependency-name: vitest
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: major-updates
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Aug 19, 2024
Copy link

changeset-bot bot commented Aug 19, 2024

⚠️ No Changeset found

Latest commit: 34d3e9e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

coderabbitai bot commented Aug 19, 2024

Walkthrough

The recent updates in the package.json reflect a significant upgrade to various dependencies, including key libraries for testing and Node.js type definitions. These enhancements are aimed at improving functionality, performance, and security, showcasing a commitment to keeping the project current with the latest developments in its external libraries.

Changes

File Change Summary
package.json Updated dependencies: @types/node from ^20.11.25 to ^22.4.1; @vitest/coverage-istanbul and @vitest/ui from ^1.3.1 to ^2.0.5; npm-check-updates from ^16.14.15 to ^17.0.6; vitest from ^1.3.1 to ^2.0.5.

Poem

🐇 In the garden of code where the bright bits play,
Dependencies dance in a joyful array.
With each little upgrade, we hop and we cheer,
New features unfolding, the future is near!
So let’s raise our paws, let the testing begin,
For in this fine update, we’re destined to win!


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between d8b1fae and 34d3e9e.

Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
Files selected for processing (1)
  • package.json (2 hunks)
Additional comments not posted (5)
package.json (5)

99-99: Verify compatibility with Node.js version.

The @types/node package has been updated to ^22.4.1. Ensure that the project's Node.js version is compatible with this update.


101-101: Verify compatibility with the testing framework.

The @vitest/ui package has been updated to ^2.0.5. Ensure that this update is compatible with the current testing framework and any custom UI configurations.


127-127: Verify compatibility with existing tests.

The vitest package has been updated to ^2.0.5. Ensure that this update is compatible with existing tests and does not introduce any breaking changes.


100-100: Verify compatibility with the testing setup.

The @vitest/coverage-istanbul package has been updated to ^2.0.5. Ensure that this update is compatible with the current testing setup and configurations.


109-109: Verify compatibility with Node.js version for npm-check-updates.

The npm-check-updates package has been updated to ^17.0.6, which requires Node.js version >= 18.18.0. Ensure that the project's Node.js version meets this requirement.

Copy link
Contributor Author

dependabot bot commented on behalf of github Aug 26, 2024

Superseded by #129.

@dependabot dependabot bot closed this Aug 26, 2024
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/major-updates-0a683b3b01 branch August 26, 2024 03:21
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