Skip to content

Bump vitest from 2.1.9 to 4.1.0 - autoclosed#1015

Closed
renovate-pagopa[bot] wants to merge 1 commit into
mainfrom
renovate/vitest-to-4.1.0
Closed

Bump vitest from 2.1.9 to 4.1.0 - autoclosed#1015
renovate-pagopa[bot] wants to merge 1 commit into
mainfrom
renovate/vitest-to-4.1.0

Conversation

@renovate-pagopa

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
vitest (source) ^2.1.9 -> ^4.0.0 age confidence
vitest (source) ^3.1.3 -> ^4.0.0 age confidence

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

For further information on security, please refer to the Confluence page link


Release Notes

vitest-dev/vitest (vitest)

v4.1.0

Compare Source

Vitest 4.1 is out!

This release page lists all changes made to the project during the 4.1 beta. To get a review of all the new features, read our blog post.

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v4.0.18

Compare Source

   🚀 Experimental Features
   🐞 Bug Fixes
    View changes on GitHub

v4.0.17

Compare Source

   🚀 Experimental Features
   🐞 Bug Fixes
    View changes on GitHub

v4.0.16

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v4.0.15

Compare Source

   🚀 Experimental Features
   🐞 Bug Fixes

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@renovate-pagopa renovate-pagopa Bot requested a review from a team as a code owner June 2, 2026 06:53
@renovate-pagopa renovate-pagopa Bot added the OER label Jun 2, 2026
@renovate-pagopa

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: src/oneid/oneid-fe/yarn.lock
Unknown Syntax Error: Unsupported option name ("--ignore-platform").

$ yarn install [--json] [--immutable] [--immutable-cache] [--refresh-lockfile] [--check-cache] [--check-resolutions] [--inline-builds] [--mode #0]

@changeset-bot

changeset-bot Bot commented Jun 2, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 1c99dd4

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

@github-actions github-actions Bot added the missing changeset missing changeset in the pr label Jun 2, 2026
@renovate-pagopa renovate-pagopa Bot changed the title Bump vitest from 2.1.9 to 4.1.0 Bump vitest from 2.1.9 to 4.1.0 - autoclosed Jun 9, 2026
@renovate-pagopa renovate-pagopa Bot closed this Jun 9, 2026
@renovate-pagopa renovate-pagopa Bot deleted the renovate/vitest-to-4.1.0 branch June 9, 2026 07:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

missing changeset missing changeset in the pr OER

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants