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

Upgrade SLF4J 2.0.10 -> 2.0.11 #957

Merged
merged 1 commit into from
Jan 12, 2024
Merged

Upgrade SLF4J 2.0.10 -> 2.0.11 #957

merged 1 commit into from
Jan 12, 2024

Conversation

Picnic-Bot
Copy link
Contributor

This PR contains the following updates:

Package Type Update Change
SLF4J (source) import patch 2.0.10 -> 2.0.11

  • If you want to rebase/retry this PR, check this box

@Picnic-Bot
Copy link
Contributor Author

Picnic-Bot commented Jan 10, 2024

Suggested commit message:

Upgrade SLF4J 2.0.10 -> 2.0.11 (#957)

See:
- https://www.slf4j.org/news.html
- https://github.com/qos-ch/slf4j/compare/v_2.0.10...v_2.0.11

Copy link

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

@Stephan202 Stephan202 added this to the 0.15.0 milestone Jan 10, 2024
@rickie rickie force-pushed the renovate/slf4j-2.x branch from e3af85b to 58955e6 Compare January 12, 2024 09:14
Copy link

Quality Gate Passed Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

Copy link

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

@rickie rickie merged commit a89f986 into master Jan 12, 2024
16 checks passed
@rickie rickie deleted the renovate/slf4j-2.x branch January 12, 2024 09:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants