fix!: Mark checkout id as deprecated_required_to_omit for update requests#145
Open
raginpirate wants to merge 2 commits intomainfrom
Open
fix!: Mark checkout id as deprecated_required_to_omit for update requests#145raginpirate wants to merge 2 commits intomainfrom
raginpirate wants to merge 2 commits intomainfrom
Conversation
knightlin-shopify
approved these changes
Jan 30, 2026
knightlin-shopify
left a comment
There was a problem hiding this comment.
LGTM to omit the id field for all the request. The id should be specified outside of checkout object (REST will be on the URL, MCP will be on parent object).
80668d3 to
e2c2d33
Compare
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.
Dependency on Universal-Commerce-Protocol/ucp-schema#6
Description
This change simplifies the checkout request schema by marking the id field as deprecated from all request types. Today we do this correctly for complete, but for update we accept a checkout id in both the transport layer as well as the checkout object being provided. This was a miss dating back to the 2026-01-11 release.
Type of change
functionality to not work as expected, including removal of schema files
or fields)
Is this a Breaking Change or Removal?
If you checked "Breaking change" above, or if you are removing any schema
files or fields:
!to my PR title (e.g.,feat!: remove field).Its very clear why this is needed; redundant context being sent between businesses and platforms.
Checklist