-
Notifications
You must be signed in to change notification settings - Fork 2
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
Conversation
… 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]>
|
WalkthroughThe recent updates in the Changes
Poem
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? TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Additionally, you can add CodeRabbit Configuration File (
|
There was a problem hiding this 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
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.
Superseded by #129. |
Bumps the major-updates group with 5 updates in the / directory:
20.14.10
22.4.1
1.6.0
2.0.5
1.6.0
2.0.5
16.14.20
17.0.6
1.6.0
2.0.5
Updates
@types/node
from 20.14.10 to 22.4.1Commits
Updates
@vitest/coverage-istanbul
from 1.6.0 to 2.0.5Release notes
Sourced from
@vitest/coverage-istanbul
's releases.... (truncated)
Commits
99452a7
chore: release v2.0.5400481f
chore: release v2.0.4a852b16
refactor: enable isolatedDeclarations in snapshot and spy packages (#6146)81b8d67
chore: release v2.0.399a12ae
chore: release v2.0.280a43d5
fix(browser): inline pretty-format and replace picocolors with tinyrainbow (#...16eb6c8
chore: release v2.0.11b150a3
chore: release v2.0.05611895
chore: release v2.0.0-beta.13368c137
fix(coverage): remove work-around for implicitelse
(#6014)Updates
@vitest/ui
from 1.6.0 to 2.0.5Release notes
Sourced from
@vitest/ui
's releases.... (truncated)
Commits
99452a7
chore: release v2.0.513d85bd
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.4f55dc00
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.3840e02f
feat(ui): show all suites/tests when parent matches (#6106)958352c
chore: bump unplugin-auto-import (#6094)Updates
npm-check-updates
from 16.14.20 to 17.0.6Release notes
Sourced from npm-check-updates's releases.
Commits
eae4692
17.0.6369bbdf
fix: check if upgrade ignored due to engines fails due to usage of ranges (#1...1aec29a
17.0.571423af
fix: fetchPartialPackument fallback is not done right (#1446)cf94481
17.0.476d7d34
fix: yarn is not pasing yarn config to getEngines (#1445)ed0767b
CHANGELOG888e222
17.0.3c226e38
Allow custom registries without trailing slash (#1440)1dfe89d
17.0.2Updates
vitest
from 1.6.0 to 2.0.5Release notes
Sourced from vitest's releases.
... (truncated)
Commits
99452a7
chore: release v2.0.59b9bdf7
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): improvedefineProject
anddefineWorkspace
types (#6198)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 conditionsSummary by CodeRabbit