Skip to content

Lock file maintenance - #225

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/lock-file-maintenance
Open

Lock file maintenance#225
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/lock-file-maintenance

Conversation

@renovate

@renovate renovate Bot commented May 25, 2026

Copy link
Copy Markdown
Contributor

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: (in timezone Europe/Madrid)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • 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 was generated by Mend Renovate. View the repository job log.

@changeset-bot

changeset-bot Bot commented May 25, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 5c23f78

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

@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 6 times, most recently from 26a25f4 to 75e15e9 Compare June 4, 2026 13:20
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 4 times, most recently from 018c687 to 066146f Compare June 11, 2026 17:03
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 6 times, most recently from f1eb1e4 to 2d4f366 Compare June 21, 2026 16:41
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 3 times, most recently from a7ece2c to 2653db9 Compare June 29, 2026 18:33
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 4 times, most recently from 14fc69c to 079ea13 Compare July 12, 2026 10:53
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 4 times, most recently from 4549cb2 to 9b187f1 Compare July 20, 2026 20:55
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 764e6f4 to e13ed84 Compare July 24, 2026 18:01
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 3 times, most recently from bf9ccae to e90d022 Compare August 5, 2026 18:28
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 7 times, most recently from 8d13d6c to d1b793a Compare August 16, 2026 16:04
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 3 times, most recently from 69dab9b to 6812911 Compare August 24, 2026 07:41
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 2e6a657 to 5b93579 Compare August 28, 2026 09:04
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 6 times, most recently from 71a3d28 to 888f477 Compare September 3, 2026 21:39
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 6 times, most recently from 72cb4d1 to 087c4f3 Compare September 7, 2026 15:00
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 087c4f3 to 5c23f78 Compare September 8, 2026 00:09
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.

0 participants