chore(deps-dev): bump the major-updates group across 1 directory with 5 updates #126
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
… 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.2.0` | | [@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.2.0 - [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
bot
added
the
dependencies
|
WalkthroughThis update enhances the project's dependencies by upgrading several key packages 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 (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
Files selected for processing (1)
- package.json (2 hunks)
Additional comments not posted (4)
package.json (4)
99-99: Verify compatibility with Node.js version.The update to
@types/nodefrom^20.11.25to^22.2.0may introduce changes that require verification of compatibility with your current Node.js version.
109-109: Check for breaking changes in npm-check-updates.The update to
npm-check-updatesfrom^16.14.15to^17.0.6includes breaking changes, such as requiring Node.js version>= 18.18.0. Ensure your environment meets these requirements.
100-101: Review breaking changes and new features.The updates to
@vitest/coverage-istanbuland@vitest/uifrom^1.3.1to^2.0.5include new features and bug fixes. Review the release notes for any breaking changes or new features that might affect your test coverage and UI.Verification successful
No Breaking Changes, but Note Experimental API
The update to version 2.0.5 includes an experimental API for reported tasks, which might be relevant if you are using custom reporters. No breaking changes were identified in the release notes.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Review release notes for @vitest/coverage-istanbul and @vitest/ui. # Test: Fetch release notes. Expect: No breaking changes affecting current usage. echo "Please manually review the release notes at:" echo "https://github.com/vitest-dev/vitest/releases"Length of output: 197
Script:
#!/bin/bash # Fetch the changelog or release notes for specific versions of @vitest/coverage-istanbul and @vitest/ui # Using GitHub CLI to fetch the release notes for version 2.0.5 of both packages gh release view v2.0.5 --repo vitest-dev/vitest --json body --jq '.body' > vitest_release_notes.txt # Output the fetched release notes cat vitest_release_notes.txtLength of output: 3010
127-127: Ensure compatibility with updated vitest.The update to
vitestfrom^1.3.1to^2.0.5may include changes that affect your tests. Review the release notes for any breaking changes or new features.
|
Superseded by #128. |
dependabot
bot
deleted the
dependabot/npm_and_yarn/major-updates-6efc3d5154
branch
Bumps the major-updates group with 5 updates in the / directory:
20.14.1022.2.01.6.02.0.51.6.02.0.516.14.2017.0.61.6.02.0.5Updates
@types/nodefrom 20.14.10 to 22.2.0Commits
Updates
@vitest/coverage-istanbulfrom 1.6.0 to 2.0.5Release notes
Sourced from
@vitest/coverage-istanbul's releases.... (truncated)
Commits
99452a7chore: release v2.0.5400481fchore: release v2.0.4a852b16refactor: enable isolatedDeclarations in snapshot and spy packages (#6146)81b8d67chore: release v2.0.399a12aechore: release v2.0.280a43d5fix(browser): inline pretty-format and replace picocolors with tinyrainbow (#...16eb6c8chore: release v2.0.11b150a3chore: release v2.0.05611895chore: release v2.0.0-beta.13368c137fix(coverage): remove work-around for implicitelse(#6014)Updates
@vitest/uifrom 1.6.0 to 2.0.5Release notes
Sourced from
@vitest/ui's releases.... (truncated)
Commits
99452a7chore: release v2.0.513d85bdfeat: introduce experimental reported tasks (#6149)3aab8a1refactor: deprecate all config types from the main Vitest entrypoint, introdu...c3ef56dchore(deps): update all non-major dependencies (#6188)400481fchore: release v2.0.4f55dc00chore(deps): update all non-major dependencies (#6046)2d62051feat(browser): allow preview and open in the editor screenshot error from ui ...81b8d67chore: release v2.0.3840e02ffeat(ui): show all suites/tests when parent matches (#6106)958352cchore: bump unplugin-auto-import (#6094)Updates
npm-check-updatesfrom 16.14.20 to 17.0.6Release notes
Sourced from npm-check-updates's releases.
Commits
eae469217.0.6369bbdffix: check if upgrade ignored due to engines fails due to usage of ranges (#1...1aec29a17.0.571423affix: fetchPartialPackument fallback is not done right (#1446)cf9448117.0.476d7d34fix: yarn is not pasing yarn config to getEngines (#1445)ed0767bCHANGELOG888e22217.0.3c226e38Allow custom registries without trailing slash (#1440)1dfe89d17.0.2Updates
vitestfrom 1.6.0 to 2.0.5Release notes
Sourced from vitest's releases.
... (truncated)
Commits
99452a7chore: release v2.0.59b9bdf7chore: remove unnecessary await (#6249)40dfad8docs: add reported tasks docs (#6245)13d85bdfeat: introduce experimental reported tasks (#6149)b76a927refactor(vitest): move public exports to public folder (#6218)56dbfa6refactor: make a distinction between node and runtime types (#6214)a48be6ffix(vitest): correctly resolve mocked node:* imports in mocks folder (#6204)3aab8a1refactor: deprecate all config types from the main Vitest entrypoint, introdu...57d23cedocs: fix inconsistencies, remove low informative twoslash examples (#6200)8cd8272fix(vitest): improvedefineProjectanddefineWorkspacetypes (#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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill 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 versionwill 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
@types/node,@vitest/coverage-istanbul,@vitest/ui,npm-check-updates, andvitest.