-
Notifications
You must be signed in to change notification settings - Fork 4
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
fix(deps): update log4j packages to v2.24.1 #112
Open
renovate
wants to merge
1
commit into
develop
Choose a base branch
from
renovate/log4j
base: develop
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.
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #112 +/- ##
========================================
Coverage 74.84% 74.84%
========================================
Files 34 34
Lines 799 799
Branches 103 103
========================================
Hits 598 598
Misses 141 141
Partials 60 60 ☔ View full report in Codecov by Sentry. |
renovate
bot
force-pushed
the
renovate/log4j
branch
2 times, most recently
from
June 15, 2023 09:44
129fb2a
to
c16b7ce
Compare
renovate
bot
changed the title
fix(deps): update log4j packages to v2.20.0
fix(deps): update log4j packages to v2.21.0
Oct 16, 2023
renovate
bot
force-pushed
the
renovate/log4j
branch
from
October 16, 2023 21:32
c16b7ce
to
8d88f72
Compare
renovate
bot
changed the title
fix(deps): update log4j packages to v2.21.0
fix(deps): update log4j packages to v2.21.1
Oct 24, 2023
renovate
bot
force-pushed
the
renovate/log4j
branch
from
October 24, 2023 16:58
8d88f72
to
40c725e
Compare
renovate
bot
changed the title
fix(deps): update log4j packages to v2.21.1
fix(deps): update log4j packages to v2.22.0
Nov 20, 2023
renovate
bot
force-pushed
the
renovate/log4j
branch
from
November 20, 2023 09:07
40c725e
to
952f0e3
Compare
renovate
bot
force-pushed
the
renovate/log4j
branch
from
December 27, 2023 10:06
952f0e3
to
bad69f0
Compare
renovate
bot
changed the title
fix(deps): update log4j packages to v2.22.0
fix(deps): update log4j packages to v2.22.1
Dec 27, 2023
renovate
bot
force-pushed
the
renovate/log4j
branch
from
February 21, 2024 13:43
bad69f0
to
11b4965
Compare
renovate
bot
changed the title
fix(deps): update log4j packages to v2.22.1
fix(deps): update log4j packages to v2.23.0
Feb 21, 2024
renovate
bot
force-pushed
the
renovate/log4j
branch
from
March 10, 2024 19:50
11b4965
to
40900ba
Compare
renovate
bot
changed the title
fix(deps): update log4j packages to v2.23.0
fix(deps): update log4j packages
Mar 10, 2024
renovate
bot
force-pushed
the
renovate/log4j
branch
from
March 10, 2024 23:30
40900ba
to
f4b614a
Compare
renovate
bot
changed the title
fix(deps): update log4j packages
fix(deps): update log4j packages to v2.23.1
Mar 10, 2024
renovate
bot
force-pushed
the
renovate/log4j
branch
2 times, most recently
from
April 2, 2024 08:38
e4d21fb
to
25cc389
Compare
renovate
bot
force-pushed
the
renovate/log4j
branch
from
September 6, 2024 21:55
25cc389
to
7e07a77
Compare
renovate
bot
changed the title
fix(deps): update log4j packages to v2.23.1
fix(deps): update log4j packages to v2.24.0
Sep 6, 2024
renovate
bot
force-pushed
the
renovate/log4j
branch
from
September 29, 2024 16:01
7e07a77
to
d14db54
Compare
renovate
bot
changed the title
fix(deps): update log4j packages to v2.24.0
fix(deps): update log4j packages to v2.24.1
Sep 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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:
2.19.0
->2.24.1
2.19.0
->2.24.1
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.