Bump failureaccess to 1.0.3.
#221
Merged
Conversation
This file contains hidden or 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
Bazel is already automatically pulling 1.0.3, since that's a transitive dependency of recent Guava releases. This just brings our explicit specification in line with that. (It's possible that it would make sense for us to stop listing the `failureaccess` dependency entirely: We're always going to be getting it as part of Guava. But maybe that would prevent us from exporting it from the `guava` target that we define? I don't feel like figuring that out right at this moment.) (followup to [our modularization efforts](google/guava#2970)) RELNOTES=n/a PiperOrigin-RevId: 741553352
copybara-service
bot
force-pushed
the
test_741501993
branch
from
640bb09 to
a40eaa3
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
failureaccessto 1.0.3.Bazel is already automatically pulling 1.0.3, since that's a transitive dependency of recent Guava releases. This just brings our explicit specification in line with that.
(It's possible that it would make sense for us to stop listing the
failureaccessdependency entirely: We're always going to be getting it as part of Guava. But maybe that would prevent us from exporting it from theguavatarget that we define? I don't feel like figuring that out right at this moment.)(followup to our modularization efforts)
RELNOTES=n/a