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.
Bump a bunch of deps at once.
Notes:
jsinterop-annotations
bump to 2.1.0 because it's builtwith
-target 11
, while we still support 8.(Closes Bump com.google.jsinterop:jsinterop-annotations from 2.0.0 to 2.1.0 #1147)
(I've noted this in Figure out when to drop Java 8 support guava#6614)
that perhaps this was the result of a protobuf change from "-rc1" to
"-rc-1", but
I'm wondering if it's actually just that
versions-maven-plugin
(incontrast to Dependabot) counts release candidates as
releases?
I'd have to investigate further and perhaps use
rulesUri
. But since wenormally rely on Dependabot (and I was using
versions-maven-plugin
here only "to make things easier"... :)), I'm not going to worry about
it now.
...
Also, it looks like protobuf 4 might remove the
hasPresence()
methodthat we'd migrated to back in cl/508716698. If so, there's a good
chance that the protobuf team will fix things for us :) If not, I'm
assuming that this will relate to
"Editions."
Fixes #1149
Fixes #1148
Fixes #1146
Fixes #1145
Fixes #1150
RELNOTES=n/a