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

Lock file maintenance #164

Merged
merged 1 commit into from
Sep 10, 2024
Merged

Conversation

RKIMetadataExchange
Copy link
Contributor

@RKIMetadataExchange RKIMetadataExchange commented Aug 26, 2024

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: 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.

@RKIMetadataExchange RKIMetadataExchange self-assigned this Aug 26, 2024
@RKIMetadataExchange RKIMetadataExchange force-pushed the renovate/lock-file-maintenance branch from 640c929 to 0493355 Compare September 6, 2024 09:53
@rababerladuseladim
Copy link
Contributor

blocked by robert-koch-institut/mex-common#279

@RKIMetadataExchange RKIMetadataExchange force-pushed the renovate/lock-file-maintenance branch from 0493355 to abe338e Compare September 10, 2024 15:05
@rababerladuseladim rababerladuseladim merged commit 97faaa3 into main Sep 10, 2024
4 checks passed
@rababerladuseladim rababerladuseladim deleted the renovate/lock-file-maintenance branch September 10, 2024 15:17
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.

2 participants