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

deps: update dependency vitest to v1.6.0 #22

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 26, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vitest (source) 1.2.1 -> 1.6.0 age adoption passing confidence

Release Notes

vitest-dev/vitest (vitest)

v1.6.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v1.5.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.5.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.5.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v1.5.0

Compare Source

v1.4.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v1.3.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v1.3.0

Compare Source

🚀 Features
🐞 Bug Fixes
View changes on GitHub

v1.2.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

Configuration

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

🚦 Automerge: Enabled.

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

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

This PR has been generated by Mend Renovate. View repository job log here.

Copy link
Contributor Author

renovate bot commented Jan 26, 2024

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.


  • Branch has one or more failed status checks

@renovate renovate bot changed the title deps: update dependency vitest to v1.2.2 deps: update dependency vitest to v1.3.0 Feb 16, 2024
@renovate renovate bot changed the title deps: update dependency vitest to v1.3.0 deps: update dependency vitest to v1.3.1 Feb 20, 2024
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from b902831 to f874f8b Compare March 15, 2024 11:56
@renovate renovate bot changed the title deps: update dependency vitest to v1.3.1 deps: update dependency vitest to v1.4.0 Mar 15, 2024
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from f874f8b to 540296a Compare April 11, 2024 18:57
@renovate renovate bot changed the title deps: update dependency vitest to v1.4.0 deps: update dependency vitest to v1.5.0 Apr 11, 2024
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 540296a to 6ddc8fa Compare April 24, 2024 12:13
@renovate renovate bot changed the title deps: update dependency vitest to v1.5.0 deps: update dependency vitest to v1.5.1 Apr 24, 2024
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 6ddc8fa to 606a480 Compare April 25, 2024 11:02
@renovate renovate bot changed the title deps: update dependency vitest to v1.5.1 deps: update dependency vitest to v1.5.2 Apr 25, 2024
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 606a480 to d7cd5b4 Compare April 30, 2024 10:02
@renovate renovate bot changed the title deps: update dependency vitest to v1.5.2 deps: update dependency vitest to v1.5.3 Apr 30, 2024
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from d7cd5b4 to 937e804 Compare May 3, 2024 16:31
@renovate renovate bot changed the title deps: update dependency vitest to v1.5.3 deps: update dependency vitest to v1.6.0 May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants