Version Packages (2026-10-rc) (rc) - #4622
Merged
Merged
Conversation
shopify-github-actions-access
Bot
force-pushed
the
changeset-release/2026-10-rc
branch
from
August 17, 2026 09:43
00d6cff to
1575522
Compare
aaronschubert0
approved these changes
Aug 17, 2026
This was referenced Aug 17, 2026
aaronschubert0
added a commit
that referenced
this pull request
Aug 18, 2026
…cs (#4632) ## What Docs-only follow-up to #4611: pins `PaymentValidationsEvent`'s dispatch timing, which was settled after that PR merged. - Fires when a tender is **confirmed but not committed** — after the amount is entered, before the payment is recorded (previously read "when staff selects a payment method", which was the pre-settlement wording). - **One event per tender attempt**; split payments dispatch one event per tender, each carrying its own `amount`. - Replaces the rejected two-event proposal (method-selected + post-tender). Confirm-time is also why `amount` is per-tender meaningful: at selection time only the outstanding total exists; at confirm time the event carries the amount this tender actually charges. ## References - Types: #4611 (merged) · Release: #4622 (`2027.0.0-rc.5`) - API contract: Shopify/ui-api-design#1557 - POS host implementation (gates at `useCashPaymentSubmission`, before `addPayment`): shop/world#997831 → shop/world#1000498 → execution PR to follow
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
1 participant
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to 2026-10-rc, this PR will be updated.
2026-10-rcis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exiton2026-10-rc.Releases
@shopify/ui-extensions@2027.0.0-rc.5
Major Changes
#4612
8e59844Thanks @aaronschubert0! - Remove the POS Action API (shopify.action.presentModal()) from action render targets (*.action.render).Action render targets are themselves the modal destination that
presentModal()opens, so exposing the Action API there had no meaningful destination — callingshopify.action.presentModal()frompos.cart.line-item-details.action.render(the one action render target that still exposed it) pushed another instance of the same target onto the navigation stack, rendering a duplicate modal on top of the already-open one.Action render targets now expose only
ActionTargetApiplus their contextual APIs, matching every other*.action.rendertarget. Extensions that need in-workflow navigation should use the Navigation API (shopify.navigation). This is a versioned breaking change: the surface is removed for API versions2026-10and later; older API versions keep their published types.Minor Changes
d8b03c9Thanks @aaronschubert0! - Addpaymentvalidationsintercept types for POS payment blocking workflows, and rename thebeforecheckoutintercept tocartvalidationsso both interceptable workflows follow one naming scheme.@shopify/ui-extensions-tester@2027.0.0-rc.5
Major Changes
#4612
8e59844Thanks @aaronschubert0! - Remove the POS Action API (shopify.action.presentModal()) from action render targets (*.action.render).Action render targets are themselves the modal destination that
presentModal()opens, so exposing the Action API there had no meaningful destination — callingshopify.action.presentModal()frompos.cart.line-item-details.action.render(the one action render target that still exposed it) pushed another instance of the same target onto the navigation stack, rendering a duplicate modal on top of the already-open one.Action render targets now expose only
ActionTargetApiplus their contextual APIs, matching every other*.action.rendertarget. Extensions that need in-workflow navigation should use the Navigation API (shopify.navigation). This is a versioned breaking change: the surface is removed for API versions2026-10and later; older API versions keep their published types.Patch Changes
d8b03c9,8e59844]: