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

chore(deps): bump @nextcloud/vite-config from 2.2.2 to ^2.2.2 #756

Merged
merged 1 commit into from
Sep 1, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 31, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@nextcloud/vite-config ^2.0.1 -> ^2.2.2 age adoption passing confidence

Configuration

📅 Schedule: Branch creation - "before 4am on the first day of the month" in timezone Europe/Berlin, 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added 4. to release dependencies Pull requests that update a dependency file labels Aug 31, 2024
@renovate renovate bot enabled auto-merge (rebase) August 31, 2024 22:57
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/nextcloud-vite-config-2.x branch from f791fc9 to 96c048f Compare September 1, 2024 00:12
@renovate renovate bot merged commit 52be29a into main Sep 1, 2024
9 checks passed
@renovate renovate bot deleted the renovate/nextcloud-vite-config-2.x branch September 1, 2024 00:14
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4. to release dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants