-
-
Notifications
You must be signed in to change notification settings - Fork 8.9k
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
[JEP-233] Upgrade Guava from 11.0.1 to latest #5707
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
BTW do you plan to tackle
jenkins/.github/dependabot.yml
Lines 27 to 28 in bc827ae
# needs guava upgrades first https://github.com/jenkinsci/jenkins/pull/5200#pullrequestreview-579741619 | |
- dependency-name: "com.google.inject:guice" |
Line 99 in bc827ae
<version>4.0</version> |
I already have a change for the Guice upgrade ready to be filed, but I want to get this PR shipped first to make any potential future bisection easier. |
nice, I've tested a guice upgrade on top of this a month or so back, didn't hit any issues other than needing to add a couple more methods to some interface somewhere |
This PR is now ready for merge, after ~24 hours, we will merge it if there's no negative feedback. Thanks! |
@basil can we delete https://github.com/jenkinsci/plugin-pom/blob/655257b6dc9a14b44e096ed5af8d142711068069/pom.xml#L541 now or at some point? |
* No-op change to check CI result I suspect some unrelated problem to another change I'm trying to submit. * Verify the version past the Guava & Guice bumps jenkinsci/jenkins#5707 jenkinsci/jenkins#5858 * Add missing comma * Remove JDK8 builds Co-authored-by: Ivan Fernandez Calvo <kuisathaverat@users.noreply.github.com> Co-authored-by: Ivan Fernandez Calvo <kuisathaverat@users.noreply.github.com>
Guava Library Upgraded
Proposed changelog entries
Proposed upgrade guidelines
Submitter checklist
Proposed changelog entries
section only if there are breaking changes or other changes which may require extra steps from users during the upgradeDesired reviewers
@jenkinsci/core
Maintainer checklist
Before the changes are marked as
ready-for-merge
:Proposed changelog entries
are correctupgrade-guide-needed
label is set and there is aProposed upgrade guidelines
section in the PR title. (example)lts-candidate
to be considered (see query).