Repository navigation
Version Packages (2026-10-rc) (rc) - #4723
Open
shopify-github-actions-access[bot] wants to merge 1 commit into
Open
shopify-github-actions-access[bot] wants to merge 1 commit into
shopify-github-actions-access[bot] wants to merge 1 commit into
Conversation
shopify-github-actions-access
Bot
force-pushed
the
changeset-release/2026-10-rc
branch
5 times, most recently
from
September 28, 2026 22:44
c8341ef to
c39c664
Compare
shopify-github-actions-access
Bot
force-pushed
the
changeset-release/2026-10-rc
branch
3 times, most recently
from
October 9, 2026 15:07
bb3744a to
03b8014
Compare
shopify-github-actions-access
Bot
force-pushed
the
changeset-release/2026-10-rc
branch
from
October 9, 2026 17:51
03b8014 to
b19f5b2
Compare
This branch has not been deployed
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.
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@2026.10.0-rc.14
Minor Changes
#4739
8692912Thanks @rcaplanshopify! - Expose extended address fields to checkout UI extensions:Country.acceptedAddressInputFields(the buyer's current country; on checkout'sCountryonly, not customer accounts') andlocalization.acceptedAddressInputFieldsForCountry(countryCode)(any country) list the address inputs a country's format carries, typed by the newAcceptedAddressInputField. They're guidance:applyShippingAddressChangedoesn't reject a write because it includes fields outside the list. It still rejects unknown properties, wrong value types, missing approval scopes, a malformedaddressLineComponents, components for a country without a component layout, and anyaddressCodewrite.MailingAddressgainsaddressLineComponents(newAddressLineComponentstype:streetName,streetNumber,additionalInformation,district,subdistrict) andaddressCode.applyShippingAddressChangeaccepts writes nested underaddressLineComponents.ShippingAddressChangeFieldError.fieldis nowShippingAddressChangeErrorField, which widenskeyof MailingAddressto include line component names and'addressLineComponents'.suggestandformat-suggestiontargets receivetarget.acceptedAddressInputFields.AutocompleteAddressacceptsaddressLineComponentsandaddressCode.@shopify/ui-extensions-tester: the checkout mock'slocalization.acceptedAddressInputFieldsForCountry()resolves the flat address input fields, andlocalization.countrycarries the same list. The newcreateAcceptedAddressInputFieldsForCountry(overrides?)helper andFLAT_ADDRESS_INPUT_FIELDSmodel countries with extended fields.Breaking for custom implementations:
Localizationhas a new required method, and exhaustive checks onShippingAddressChangeFieldError.fieldneed the new members.#4715
e34b5a7Thanks @js-goupil! - Addversionto the POS Extension API.shopify.extension.versionis the name of the published app version that the running extension was deployed in — the same name shown on the Versions page of the dev dashboard, and the name chosen when runningshopify app deploy. Use it to tell which build of an extension a merchant is running, which POS can cache and run offline for some time after a newer version is deployed. It's an opaque name rather than a version number, so compare it for equality. It'sundefinedwhen the extension runs from a local development server, because a build that hasn't been deployed has no published version.#4690
3703a5bThanks @ajanth-u! - Add thes-pos-listweb component for POS and theposListTemplatetagged template that compiles its<s-pos-list-item>row markup.#4724
9f5ad67Thanks @js-goupil! - Add the POSnavigationnavigatesuccessevent type and documentation for listening after a screen finishes appearing.Patch Changes
#4737
9d07293Thanks @ChemsCode! - ExposeAuthenticatedAccountCustomerfor the Authenticated Account API and its Preact hook, retainingCustomeras a deprecated compatibility interface. Correct the customer ID documentation to describe a numeric string and use the public type names in the generated documentation.#4727
8ee0082Thanks @henryStelle! - Remove stale POS component names from the component availability metadata for 2026-10 targets.#4683
8ebe439Thanks @vctrchu! - Clarify POS validation interceptor and resolution event semantics, including cash amounts, empty results, revalidation updates, and generated interceptor and Resolution API documentation.#4735
565c318Thanks @ajanth-u! - Shorten thes-pos-listproperty descriptions forrows,itemTemplates, andloadingMore, and stop listing defaults forrowsanditemTemplates.@shopify/ui-extensions-tester@2026.10.0-rc.14
Patch Changes
#4739
8692912Thanks @rcaplanshopify! - Expose extended address fields to checkout UI extensions:Country.acceptedAddressInputFields(the buyer's current country; on checkout'sCountryonly, not customer accounts') andlocalization.acceptedAddressInputFieldsForCountry(countryCode)(any country) list the address inputs a country's format carries, typed by the newAcceptedAddressInputField. They're guidance:applyShippingAddressChangedoesn't reject a write because it includes fields outside the list. It still rejects unknown properties, wrong value types, missing approval scopes, a malformedaddressLineComponents, components for a country without a component layout, and anyaddressCodewrite.MailingAddressgainsaddressLineComponents(newAddressLineComponentstype:streetName,streetNumber,additionalInformation,district,subdistrict) andaddressCode.applyShippingAddressChangeaccepts writes nested underaddressLineComponents.ShippingAddressChangeFieldError.fieldis nowShippingAddressChangeErrorField, which widenskeyof MailingAddressto include line component names and'addressLineComponents'.suggestandformat-suggestiontargets receivetarget.acceptedAddressInputFields.AutocompleteAddressacceptsaddressLineComponentsandaddressCode.@shopify/ui-extensions-tester: the checkout mock'slocalization.acceptedAddressInputFieldsForCountry()resolves the flat address input fields, andlocalization.countrycarries the same list. The newcreateAcceptedAddressInputFieldsForCountry(overrides?)helper andFLAT_ADDRESS_INPUT_FIELDSmodel countries with extended fields.Breaking for custom implementations:
Localizationhas a new required method, and exhaustive checks onShippingAddressChangeFieldError.fieldneed the new members.Updated dependencies [
9d07293,8692912,8ee0082,e34b5a7,8ebe439,565c318,3703a5b,9f5ad67]: