-
Notifications
You must be signed in to change notification settings - Fork 39
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 API 1.7.36 -> 2.0.2 #209
Conversation
Suggested commit message:
|
9a4754d
to
94f261a
Compare
80fe207
to
12d6835
Compare
c4c95b7
to
af8c45d
Compare
7db7dbc
to
6984ec5
Compare
6984ec5
to
603668c
Compare
@Stephan202 Internally we are blocked on SB 3 upgrade, do we want to add |
603668c
to
534fe8d
Compare
@rickie good question. Generally that might be a good strategy indeed. On the other hand, I expect that we'll not suddenly start writing rules against SLF4J internals, while the public API remained mostly stable. Since we don't pull the dependency in at runtime (it's declared |
This PR contains the following updates:
1.7.36
->2.0.2