Upgrades lock_api to v0.4.10 #33736
Merged
Upgrades lock_api to v0.4.10 #33736
Conversation
This file contains 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
Codecov Report
@@ Coverage Diff @@
## master #33736 +/- ##
=======================================
Coverage 81.8% 81.8%
=======================================
Files 806 806
Lines 217851 217851
=======================================
+ Hits 178204 178248 +44
+ Misses 39647 39603 -44 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem
The
lock_apidependency is old. I'd like to useSeqLockin accounts-db, which useslock_apiinternally. However, lock_api had a breaking API change after v0.4.6, and SeqLock requires the new API.See #33696 for more information/usage.
Summary of Changes
Upgrade lock_api.