Skip to content

Lock file maintenance #110

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

Merged
merged 1 commit into from
Mar 3, 2025
Merged

Lock file maintenance #110

merged 1 commit into from
Mar 3, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 3, 2025

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.


Configuration

📅 Schedule: Branch creation - "before 4am on monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

Sorry, something went wrong.

Copy link

github-actions bot commented Mar 3, 2025

Coverage Report

Status Category Percentage Covered / Total
🔵 Lines 100% 130 / 130
🔵 Statements 100% 130 / 130
🔵 Functions 100% 13 / 13
🔵 Branches 100% 41 / 41
File CoverageNo changed files found.
Generated in workflow #295 for commit 66df53b by the Vitest Coverage Report Action

@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from f1ba24d to 66df53b Compare March 3, 2025 05:30
@renovate renovate bot merged commit 1d4a336 into main Mar 3, 2025
1 check passed
@renovate renovate bot deleted the renovate/lock-file-maintenance branch March 3, 2025 11:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants