Preserve Provider body evidence API compatibility - #573
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
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.
What changed
ProviderHttpCallRecordsource-compatible for existing struct literalsinsert_provider_http_callas the compatibility entry point with explicit missing-evidence coverageinsert_provider_http_call_with_body_evidencefor adapters that capture request and response bodiesWhy
Release-plz correctly identified the original public struct field additions as breaking and proposed
lenso-platform-core0.2.0 plus a broad dependent release. Body evidence can be added without breaking existing callers.Validation