Repository navigation
fix(version): keep protocol envelope fields when converting responses down #3594
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| --- | ||
| '@adcp/sdk': patch | ||
| --- | ||
|
|
||
| Version translation no longer removes protocol envelope fields. When a response was converted down to an older release whose task schema didn't compose the protocol envelope (the 3.2 proposal-flow responses, which AdCP 3.2.x and 3.3 fix as DR-0036 correction (b)), the schema projection treated `status`, `message`, `context` and the other envelope fields as newer-only and removed them, so a 3.2 buyer could receive a 3.3 server's `list_products` response without its `status`. The projection now keeps every property the release's protocol and version envelopes declare at the payload root. |
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Medium: The protection is unconditional — it
continues before recursing, so structured envelope keys (context,governance_context,push_notification_config,payload) are kept wholesale even when the target release composes the envelope and could project their contents. For a 3.3 → 3.2.8 down-conversion (DR-0036 correction (b) backports the envelope into 3.2.8, so 3.2.8 declares these keys), a newer-only sub-field ofcontext/governance_contextnow leaks unprojected and, because this path skipsdropped.push, unreported. The witness-not-translator contract requires every removed-or-undeliverable field to surface as drift; this short-circuit silently keeps them instead. The surgical shape protects a key only when the target does not declare it — when the target declares the envelope, normal projection already keeps the key and still reports nested drift. Same set is also applied to request projection (translate.ts:179), so envelope-keyed request fields bypass the mutating-refusal gate; that's benign for the current field set but widens the blast radius. No test covers nested envelope-field drift.