fix: update runtime-core API manifest after API-incompatible change that wasn't caught by CI #811
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
…hat wasn't caught by CI
ianbotsf
added
the
no-changelog
|
Kudos, SonarCloud Quality Gate passed!
|
lauzadis
approved these changes
Feb 23, 2023
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.
Issue #
(none)
Description of changes
#810 changed the API signature for the public constructor
StandardRetryTokenBucket. It was introduced on a separate branch from the change that added API compatibility verification, #808, and so did not fail compatibility checks in PR. The push to main occurred after API compatibility verification was enabled and wasn't blocked on merging because no overlapping files were touched.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.