-
-
Notifications
You must be signed in to change notification settings - Fork 1
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: Lock file maintenance #10
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/lock-file-maintenance
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/lock-file-maintenance
branch
from
October 30, 2021 18:26
d6481ac
to
caad899
Compare
renovate
bot
force-pushed
the
renovate/lock-file-maintenance
branch
6 times, most recently
from
November 5, 2021 22:14
ae10f2e
to
f7cf08f
Compare
renovate
bot
force-pushed
the
renovate/lock-file-maintenance
branch
2 times, most recently
from
November 21, 2021 21:05
19a069f
to
38b4e31
Compare
Kudos, SonarCloud Quality Gate passed! |
renovate
bot
force-pushed
the
renovate/lock-file-maintenance
branch
from
January 22, 2022 01:52
38b4e31
to
b00cd85
Compare
pustovitDmytro
force-pushed
the
master
branch
3 times, most recently
from
January 22, 2022 17:39
4731285
to
52f24f8
Compare
renovate
bot
force-pushed
the
renovate/lock-file-maintenance
branch
4 times, most recently
from
January 25, 2022 23:18
f7984dd
to
49ea203
Compare
renovate
bot
force-pushed
the
renovate/lock-file-maintenance
branch
2 times, most recently
from
January 31, 2022 17:05
be9bff3
to
d154954
Compare
renovate
bot
force-pushed
the
renovate/lock-file-maintenance
branch
2 times, most recently
from
February 9, 2022 16:04
8e8eae8
to
fe69ddc
Compare
Kudos, SonarCloud Quality Gate passed! |
renovate
bot
force-pushed
the
renovate/lock-file-maintenance
branch
from
March 18, 2023 12:08
fe69ddc
to
3b3b798
Compare
Kudos, SonarCloud Quality Gate passed! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
🔧 This Pull Request updates lock files to use the latest dependency versions.
Configuration
📅 Schedule: Branch creation - "before 7:00 am every 10 days starting on the 5th day" in timezone Europe/Kiev, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.
This PR was generated by Mend Renovate. View the repository job log.