feat: update conformance suite for UCP 2026-04-08#41
Open
koustubh25 wants to merge 1 commit intoUniversal-Commerce-Protocol:mainfrom
Open
feat: update conformance suite for UCP 2026-04-08#41koustubh25 wants to merge 1 commit intoUniversal-Commerce-Protocol:mainfrom
koustubh25 wants to merge 1 commit intoUniversal-Commerce-Protocol:mainfrom
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
47d64d6 to
f3f80bf
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.
Summary
Updates
conformanceto the official UCP2026-04-08release.Dependency chain for April validation:
Universal-Commerce-Protocol/python-sdk#28Universal-Commerce-Protocol/samples#91This PR removes stale
2026-01-23protocol expectations from the suite, updates officialucp.devspec/schema references to April, and adapts the tests to the April Python SDK model layout where the existing suite assumed January-era imports and scalar wrappers.Changes
2026-01-23to2026-04-08https://ucp.dev/2026-04-08/...ReverseDomainNameimports for the April Python SDK layoutAmount,SignedAmount, andTotalsWhy
The official latest UCP spec release is
2026-04-08, butconformancestill contains January-era protocol pins and SDK assumptions. That causes the suite to drift from the current published spec and from the April Python SDK update.This PR keeps the scope limited to conformance-suite April alignment. Merchant-server fixes remain in
samples#91, and SDK model updates remain inpython-sdk#28.Validation
Validated against:
https://ucp.dev/latest/specification/overview/https://ucp.dev/2026-04-08/specification/overview/python-sdk#28samples#91Serial test run result against the local April validation target:
protocol_test.pyOKvalidation_test.pyOKfulfillment_test.pyOKbusiness_logic_test.pyOKcheckout_lifecycle_test.pyOKidempotency_test.pyOKorder_test.pyOKwebhook_test.pyOKsimulation_url_security_test.pyOKap2_test.pyOKbinding_test.pyOKcard_credential_test.pyOKtest_discovery_urlsremains skipped because the remote schema publication check is not yet live onucp.dev.Scope
Included here:
Explicitly not included here:
samplespython-sdk