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

chore(deps-dev): bump the major-updates group across 1 directory with 6 updates #135

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

chore(deps-dev): bump the major-updates group across 1 directory with 6 updates #135

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 7, 2024

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

Package From To
@types/node 20.14.10 22.7.4
@vitest/coverage-istanbul 1.6.0 2.1.2
@vitest/ui 1.6.0 2.1.2
concurrently 8.2.2 9.0.1
npm-check-updates 16.14.20 17.1.3
vitest 1.6.0 2.1.2

Updates @types/node from 20.14.10 to 22.7.4

Commits

Updates @vitest/coverage-istanbul from 1.6.0 to 2.1.2

Release notes

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

v2.1.2

   🐞 Bug Fixes

    View changes on GitHub

v2.1.1

   🐞 Bug Fixes

... (truncated)

Commits
  • 0ce26a4 chore: release v2.1.2
  • 88bde99 fix(coverage): cleanOnRerun: false to invalidate previous results (#6592)
  • 1371ca6 fix(coverage): remove empty coverage folder on test failure too (#6547)
  • 699055e chore: release v2.1.1
  • 9f1fd18 chore: release v2.1.0
  • b2be23e chore: release v2.1.0-beta.7
  • 8ac7011 chore: release v2.1.0-beta.6
  • da52d23 fix(coverage): use project specific vitenode for uncovered files (#6044)
  • 5932a7f feat(coverage): add --exclude-after-remap (#6309)
  • 34199bd feat(browser): support v8 coverage (#6273)
  • Additional commits viewable in compare view

Updates @vitest/ui from 1.6.0 to 2.1.2

Release notes

Sourced from @​vitest/ui's releases.

v2.1.2

   🐞 Bug Fixes

    View changes on GitHub

v2.1.1

   🐞 Bug Fixes

... (truncated)

Commits
  • 0ce26a4 chore: release v2.1.2
  • e7f3521 fix: move Vitest.setServer to post configureServer hook to enable import ...
  • d0bf89d fix(ui): list tests on ui when --standalone (#6577)
  • 699055e chore: release v2.1.1
  • 9f1fd18 chore: release v2.1.0
  • 94a186e fix(ui): render project name consistently (#6329)
  • b2be23e chore: release v2.1.0-beta.7
  • 0223bb7 fix(ui): remove "filters" flickering (#6463)
  • 97773e2 chore: fix edge case in license files bundling (#6460)
  • b78fa88 chore(deps): update dependency @​faker-js/faker to v9 (#6461)
  • Additional commits viewable in compare view

Updates concurrently from 8.2.2 to 9.0.1

Release notes

Sourced from concurrently's releases.

v9.0.1

What's Changed

Full Changelog: open-cli-tools/concurrently@v9.0.0...v9.0.1

v9.0.0

💥 Breaking Changes

  • Dropped support for Node.js < 18.0.0. Older Node.js version have reached end-of-life, and certain features require new-ish JS APIs.

  • The concurrently and default exports are now the same - #399 It's reasonable to expect that import { concurrently } from 'concurrently' would work the same as import concurrently from 'concurrently', however this has not been the case. The former used to be an unconfigured version of concurrently, lacking all features that you'd get from the CLI, which was seen as a "footgun". Both are now the same function.

    If you'd like to access the unconfigured function, use import { createConcurrently } from 'concurrently' instead.

✨ New Features

  • Exponential back-off support for process restarting - #265, #462 Use --restart-after exponential. Restarts happen at 2^N seconds.
  • Add prefix padding via new --pad-prefix flag - #166, #417, #495
  • Specify teardown commands via new --teardown flag - #472, #500
  • Expand node:<script> commands to node --run <script> - #475
  • [API only] Inter-Process Communication (ipc) - #498
  • [API only] Make it possible to use no colors at all - #466
  • [API only] Add a state field to Command - #455

🐛 Bug Fixes

  • Fix importing concurrently in ESM package - #454, #456, #494
  • Make sure concurrently doesn't resolve when manually restarting commands through API - #463, #464
  • Abort commands not running when max processes < N - #433, #452, #460
  • Fix warning coming from spawn-command when running in Node 22 - #407, #477, #479, #492
  • Make --raw and --hide compatible - #394, #486
  • Ensure prefix is written when logging without a trailing LF - #467

Other Changes

  • --help no longer shows examples due to there being too many. Refer to https://github.com/open-cli-tools/concurrently/tree/v9.0.0/docs instead, or to the node_modules/concurrently/docs directory in your project.
  • Improve examples of --passthrough-arguments - #490
  • Replace date-fns with hand-rolled date formatting - #436, #443 This should make installing concurrently faster.

New Contributors

Full Changelog: open-cli-tools/concurrently@v8.2.2...v9.0.0

Commits
  • 79b3290 9.0.1
  • 041520b Don't set up more than 1 abort signal listener (#503)
  • a7a5894 9.0.0
  • 758ee7f tests: update smoke tests lockfile
  • 710ee55 Replace date-fns for hand-rolled date formatting
  • fe7b69c deps: update @​types/node to 18.x.x too
  • fd2d140 Bump minimum Node version to 18
  • 37f98b2 deps: update several dev dependencies
  • 1b5df3a deps: update everything eslint
  • 7fc4803 Make it possible to use no colors at all through API
  • Additional commits viewable in compare view

Updates npm-check-updates from 16.14.20 to 17.1.3

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.1.2

Release notes

Sourced from vitest's releases.

v2.1.2

   🐞 Bug Fixes

    View changes on GitHub

v2.1.1

   🐞 Bug Fixes

... (truncated)

Commits
  • 0ce26a4 chore: release v2.1.2
  • 383f179 fix(browser): throw an error if "@​vitest/browser/context" is imported outside...
  • 821400b fix(vitest): don't start a websocket server if api is disabled (#6617)
  • 8a8d3f0 fix(vitest): make env.SSR consistent between different pools (#6616)
  • ed8b7c0 fix(vitest): install dependencies with the same version when prompted (#6611)
  • d2a86ff fix(workspace): ignore DS_Store by default (#6571)
  • 88bde99 fix(coverage): cleanOnRerun: false to invalidate previous results (#6592)
  • 5f75790 refactor: replace strip-ansi with stripVTControlCharacters from `node:uti...
  • e7f3521 fix: move Vitest.setServer to post configureServer hook to enable import ...
  • 891d6fe docs: deprecate benchmark.outputFile option (#6591)
  • 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

@dependabot
chore(deps-dev): bump the major-updates group across 1 directory with…
7555775 
… 6 updates

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

| Package | From | To |
| --- | --- | --- |
| [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `20.14.10` | `22.7.4` |
| [@vitest/coverage-istanbul](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-istanbul) | `1.6.0` | `2.1.2` |
| [@vitest/ui](https://github.com/vitest-dev/vitest/tree/HEAD/packages/ui) | `1.6.0` | `2.1.2` |
| [concurrently](https://github.com/open-cli-tools/concurrently) | `8.2.2` | `9.0.1` |
| [npm-check-updates](https://github.com/raineorshine/npm-check-updates) | `16.14.20` | `17.1.3` |
| [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) | `1.6.0` | `2.1.2` |



Updates `@types/node` from 20.14.10 to 22.7.4
- [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.1.2
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v2.1.2/packages/coverage-istanbul)

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

Updates `concurrently` from 8.2.2 to 9.0.1
- [Release notes](https://github.com/open-cli-tools/concurrently/releases)
- [Commits](open-cli-tools/concurrently@v8.2.2...v9.0.1)

Updates `npm-check-updates` from 16.14.20 to 17.1.3
- [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.1.3)

Updates `vitest` from 1.6.0 to 2.1.2
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v2.1.2/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: concurrently
  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 Oct 7, 2024
@dependabot dependabot bot mentioned this pull request Oct 7, 2024
Closed
@changeset-bot changeset-bot
Copy link

changeset-bot bot commented Oct 7, 2024

⚠️ No Changeset found

Latest commit: 7555775

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

@coderabbitai coderabbitai
Copy link

coderabbitai bot commented Oct 7, 2024

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

🪧 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>, please review it.
    • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @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 using 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.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.

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
dependencies Pull requests that update a dependency file
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants