AI Pulse

<p>v20.0.0</p> <h3>🛠 Breaking changes</h3> <ul> <li>[eas-cli] Rename observe commands: <code>observe:logs</code> → <code>observe:events</code> (events emitted via <code>logEvent</code>), previous <code>observe:events</code> → <code>observe:metrics</code> (individual performance metric samples), previous <code>observe:metrics</code> → <code>observe:metrics-summary</code> (aggregated stats by app version). (<a href="https://github.com/expo/eas-cli/pull/3778" data-hovercard-type="pull_request" dat

Your store includes a default agents.md file accessible at /agents.md . The paths /llms.txt and /llms-full.txt also point to this content by default. Add any of the following templates under Online Store > Themes > Edit code to serve different content per path: templates/agents.md.liquid — controls /agents.md (and the default for the other two paths) templates/llms.txt.liquid — controls /llms.txt only templates/llms-full.txt.liquid — controls /llms-full.txt only If no template is present for a g

<p>v19.1.0</p> <h3>🎉 New features</h3> <ul> <li>[eas-cli] Add <code>--refresh-ad-hoc-provisioning-profile</code> flag to refresh managed ad-hoc provisioning profiles from App Store Connect before gathering build credentials in non-interactive mode. (<a href="https://github.com/expo/eas-cli/pull/3716" data-hovercard-type="pull_request" data-hovercard-url="/expo/eas-cli/pull/3716/hovercard">#3716</a> by <a href="https://github.com/sswrk">@sswrk</a>)</li> <li>[eas-build-job] Add optional <code>ref

<p>v19.0.8</p> <h3>🐛 Bug fixes</h3> <ul> <li>[eas-cli] <code>eas go</code> now pre-selects the SDK version from the current project's <code>app.json</code> or <code>app.config.js</code> when available. (<a href="https://github.com/expo/eas-cli/pull/3776" data-hovercard-type="pull_request" data-hovercard-url="/expo/eas-cli/pull/3776/hovercard">#3776</a> by <a href="https://github.com/gwdp">@gwdp</a>)</li> </ul>

<p>v19.0.7</p>

The release of Shopify CLI 4.0 today brings clarity to CLI versioning, the introduction of automatic updates, and the announced removal of the deprecated --force flag from shopify app deploy . Semantic Versioning Shopify CLI is now following semantic versioning practices. Releases with new features will be minor versions, and bug fixes will be patch versions. When required, major version releases will be used to communicate breaking changes to CLI command structure or behavior. For more informat

<p>v19.0.6</p> <h3>🐛 Bug fixes</h3> <ul> <li>[build-tools] Update the minimum Expo version required for iOS precompiled modules to 55.0.26. (<a href="https://github.com/expo/eas-cli/pull/3771" data-hovercard-type="pull_request" data-hovercard-url="/expo/eas-cli/pull/3771/hovercard">#3771</a> by <a href="https://github.com/chrfalch">@chrfalch</a>)</li> </ul>

You can now create your app's landing page in App Home as a Preact-based admin UI extension using the new admin.app.home.render target. This means your App Home UI extensions are bundled with your other admin UI extensions, eliminating the need for a separate web server to render your app's primary workspace. Use this extension type when you want: A persistent, full-page app workspace that's integrated into your extension bundle, rather than a separate iframe-hosted web app. A unified source of

<p>v19.0.5</p> <h3>🐛 Bug fixes</h3> <ul> <li>[eas-cli] Improve Sentry diagnostics for managed iOS entitlements config fallback. (<a href="https://github.com/expo/eas-cli/pull/3763" data-hovercard-type="pull_request" data-hovercard-url="/expo/eas-cli/pull/3763/hovercard">#3763</a> by <a href="https://github.com/sjchmiela">@sjchmiela</a>)</li> </ul>

New Features Optional Consent Users can now reject scopes and continue using your Mini. Consent is no longer all-or-nothing — if a user declines a scope, your Mini should gracefully degrade rather than block the experience. If your Mini hard-fails when a scope is rejected, please update it using the new hooks below. useCheckScopesConsent Hook Check at runtime which scopes a user has granted. Use this to conditionally render features that depend on a particular scope. Usage: import {useCheckScope

<p>v19.0.4</p>

<p>v19.0.3</p>

<p>v19.0.2</p>

<p>v19.0.1</p> <h3>🐛 Bug fixes</h3> <ul> <li>[eas-cli] Disable dotenv loading when resolving managed iOS entitlements. (<a href="https://github.com/expo/eas-cli/pull/3752" data-hovercard-type="pull_request" data-hovercard-url="/expo/eas-cli/pull/3752/hovercard">#3752</a> by <a href="https://github.com/sjchmiela">@sjchmiela</a>)</li> <li>[eas-cli] Restore the bundled config fallback for managed iOS entitlements introspection. (<a href="https://github.com/expo/eas-cli/pull/3753" data-hovercard-ty

<h2>What's Changed</h2> <ul> <li><strong>Add <code>position</code> field to <code>insert_content</code> params for update page markdown endpoint</strong> in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="4456544100" data-permission-text="Title is private" data-url="https://github.com/makenotion/notion-sdk-js/issues/720" data-hovercard-type="pull_request" data-hovercard-url="/makenotion/notion-sdk-js/pull/720/hovercard" href="https://github.com/makenotion/noti

<p>v19.0.0</p> <h3>🛠 Breaking changes</h3> <ul> <li>[eas-cli] Make browser-based authentication the default for <code>eas login</code>. Use <code>--no-browser</code> for CLI-based login. (<a href="https://github.com/expo/eas-cli/pull/3746" data-hovercard-type="pull_request" data-hovercard-url="/expo/eas-cli/pull/3746/hovercard">#3746</a> by <a href="https://github.com/byronkarlen">@byronkarlen</a>)</li> </ul> <h3>🎉 New features</h3> <ul> <li>[eas-cli] Allow command <code>observe:routes</code>

Next Generation Events are now available in developer preview, with field-level control over when events fire, what data they carry, and what triggered each delivery. Subscribe to exactly what you care about. Field-level triggers pre-qualify deliveries before they reach your endpoint. A subscription scoped to product.variants.price won't fire on title edits, tag updates, or status changes. Only when the price changes. Get the payload your app needs, not a fixed schema. You define the delivery pa

<p>v18.13.1</p> <h3>🎉 New features</h3> <ul> <li>[eas-cli] Send the installed <code>expo</code> package version in build metadata. (<a href="https://github.com/expo/eas-cli/pull/3725" data-hovercard-type="pull_request" data-hovercard-url="/expo/eas-cli/pull/3725/hovercard">#3725</a> by <a href="https://github.com/sjchmiela">@sjchmiela</a>)</li> </ul> <h3>🐛 Bug fixes</h3> <ul> <li>[eas-cli] Prevent <code>npx</code> invocations that can be unreliable and fail when retrieving entitlements or proj

You can query the shippingLine field on FulfillmentOrderLineItem . This field returns the ShippingLine associated with a fulfillment order line item, if available. This feature simplifies the process for order management and fulfillment apps to identify the shipping method for each line item. It is particularly useful in scenarios where fulfillment orders are merged across different delivery profiles, and the original per-line shipping service is not identified by the fulfillment order's deliver

<p>v18.13.0</p> <h3>🎉 New features</h3> <ul> <li>[eas-cli] New command <code>observe:routes</code> for navigation metrics. (<a href="https://github.com/expo/eas-cli/pull/3730" data-hovercard-type="pull_request" data-hovercard-url="/expo/eas-cli/pull/3730/hovercard">#3730</a> by <a href="https://github.com/douglowder">@douglowder</a>)</li> </ul> <h3>🧹 Chores</h3> <ul> <li>[eas-cli] Refactor observe commands to extract common flag definitions. (<a href="https://github.com/expo/eas-cli/pull/3731"

You no longer need to ask merchants to share function run logs with you. These logs are now automatically available in the Dev Dashboard for any function your app has the necessary access scopes to view. What's Changed Function run logs in the Dev Dashboard are now accessible based on the access scopes granted to your app by the merchant. The required scopes to view a log are determined by the function's input query. If your app has the necessary scopes to read these fields via the GraphQL Admin

<p>v18.12.3</p>

We’ve published new migration guides to help you upgrade Checkout and Customer Account UI extensions to the latest API version and Polaris web components. The new guides include: Guidance for moving from React or JavaScript extension APIs to Preact, Polaris web components, and the global shopify object. More than 60 component-specific migration pages, covering components such as Button , Checkbox , TextField , Banner and View for Checkout and Customer Account UI extensions. Instructions for migr

<p>v18.12.2</p> <h3>🧹 Chores</h3> <ul> <li>[ci] Audit GitHub Actions workflows: harden <code>pull_request_target</code> usage, pin all external actions to commit SHAs, and add Dependabot to refresh them. (<a href="https://github.com/expo/eas-cli/pull/3718" data-hovercard-type="pull_request" data-hovercard-url="/expo/eas-cli/pull/3718/hovercard">#3718</a> by <a href="https://github.com/brentvatne">@brentvatne</a>)</li> </ul>

Starting with the 2026-07 version of the Storefront API, the Cart emits a PRODUCT_UNAVAILABLE_IN_BUYER_LOCATION warning when a cart line contains a product that isn't available in the buyer's location. Each affected cart line returns its own warning. The warning's target is set to the CartLine ID so you can map it back to the line in your UI. For background on cart warnings and an example of handling them, refer to our docs on cart warnings .

<p>v18.12.1</p>

<p>v18.12.0</p> <h3>🎉 New features</h3> <ul> <li>[eas-cli] Automatically save the Convex deployment URL as an EAS environment variable when connecting a Convex project. (<a href="https://github.com/expo/eas-cli/pull/3685" data-hovercard-type="pull_request" data-hovercard-url="/expo/eas-cli/pull/3685/hovercard">#3685</a> by <a href="https://github.com/fiberjw">@fiberjw</a>)</li> </ul> <h3>🐛 Bug fixes</h3> <ul> <li>[build-tools] Update the minimum Expo version required for iOS precompiled module

<h2>What's Changed</h2> <ul> <li><strong>chore: sync generated api endpoints modules</strong> by <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/haustle/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/haustle">@haustle</a> in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="4318038454" data-permission-text="Title is private" data-url="https://github.com/ma

Shopify App Pricing supports subscriptions, usage-based charges, or combined models, configured in the Partner Dashboard. What's new: Managed Pricing is now Shopify App Pricing Shopify App Pricing replaces Managed Pricing as Shopify’s default billing solution that gets configured during app submission in the Partner Dashboard. Apps previously on Managed Pricing will now see “Shopify App Pricing” as their selected billing solution. Usage-based billing now possible with App Events API Charge based

The App Events API lets you send any event from your app to Shopify. App event data appears in your Dev Dashboard Logs alongside webhooks, Function executions, and API calls. How it works: **1. Send app events to a single API endpoint:**Define the event_handle and attributes you want to track and send them to the App Events API, including: Feature usage: bulk_edit_completed , report_generated , automation_created Workflows: onboarding_completed , campaign_sent , export_finished Performance: sync

We're changing how public apps handle offline access tokens to enhance merchant data protection. Starting January 1, 2027, all public apps must use expiring offline access tokens when calling the Admin API. After that date, public apps still using non-expiring tokens will receive authentication errors. This extends the April 1, 2026 change , which applied only to newly created public apps, to all public apps, including those created before April 1, 2026. What apps are affected Public apps making

As of version 2026-07 of the GraphQL Storefront API, the Cart object issues a warning when a buyer's selected delivery option becomes unavailable. Previously, if a buyer's chosen delivery option was no longer available (for example, after changes to the cart's address or contents) the system would automatically switch to a different option without notifying the buyer. This lack of notification made it challenging for developers to inform buyers of the change. Now, with the introduction of the DE

<p>Here's everything that happened with Supabase in the last month:</p> <h2>Custom OAuth/OIDC providers for Supabase Auth</h2> <a target="_blank" rel="noopener noreferrer" href="https://private-user-images.githubusercontent.com/30495040/589233420-97a1bc92-f8a9-4bf4-894d-ede6a762ab2b.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NzgxOTg3NDUsIm5iZiI6MTc3ODE5ODQ0NSwicGF0aCI6Ii8zMDQ5NTA0MC81ODkyMzM0MjA

What's changing Shopify now applies stricter rate limits to bots and agents that access the Storefront API and Shopify-hosted online store pages. Bots and agents that don't sign their requests are subject to the strictest limits. To qualify for higher rate limits, operators should sign their requests with Web Bot Auth. For more details, see Storefront rate limits . What you should do If you operate a bot or agent accessing Shopify storefronts, sign your requests using Web Bot Auth . To get start

ProductVariant is now a Publishable . Variants can be published or unpublished per publication (channel or catalog) in API version 2026-07, giving merchants — and your apps — fine-grained control over where each variant is visible without deleting variants, duplicating products, or hiding them via storefront code. This is a non-breaking, additive change: Product-level publishing is unchanged and still takes precedence. A product must be active and published to a channel for any of its variants t

App deployment in CI/CD is now available for all apps through app automation tokens on the Dev Dashboard. These tokens offer app-scoped authentication, allowing you to use the latest Shopify CLI to automate app releases in GitHub Workflows and similar tools. App-scoped authentication ensures that each token is specific to an individual app, enhancing security and control. To deploy your app using an app automation token, set the token as an environment variable and execute the deployment command

We've introduced markets as a new option in DiscountContextInput , enabling you to target discounts to specific regional markets, retail locations, or B2B company locations. This option can be used alongside existing eligibility options such as all , customerSegments , and customers . You can now set market eligibility for all discount types, including: Basic, BXGY, App, and Free Shipping discounts (both automatic and code-based). Note that eligibility types are mutually exclusive—you can target

Seven new Settings intents let apps open editors for notifications, payment capture, gift cards, delivery profiles, and business details. This builds on the initial Settings intents release from March. With a single API call, your app opens the relevant Settings section as a contextual overlay and scrolls the merchant directly to the field they need to edit. New intents Notifications edit:settings/NotificationsSenderEmail edit:settings/NotificationsStaff Payments and gift cards edit:settings/Pay

<p>v18.11.0</p> <h3>🎉 New features</h3> <ul> <li>[eas-cli] Add <code>--simulator</code> to <code>eas build:dev</code> and <code>eas build:run</code> to select which iOS simulator to install and run builds on. (<a href="https://github.com/expo/eas-cli/pull/3637" data-hovercard-type="pull_request" data-hovercard-url="/expo/eas-cli/pull/3637/hovercard">#3637</a> by <a href="https://github.com/mmichels-brex">@mmichels-brex</a>)</li> </ul> <h3>🐛 Bug fixes</h3> <ul> <li>[eas-cli] Fix Convex team inv

Inventory transfer webhooks: new origin and destination fields Payloads for the following webhook topics now include the source and destination location of the transfer as Location Global IDs: inventory_transfers/add_items inventory_transfers/update_item_quantities inventory_transfers/remove_items inventory_transfers/ready_to_ship inventory_transfers/cancel inventory_transfers/complete Each payload now includes: origin.id — for example, gid://shopify/Location/123 destination.id — for example, gi

The default value of appliesOnSubscription has been changed from false to true on the DiscountCodeAppInput and DiscountAutomaticAppInput input types in GraphQL Admin API. No action is required. This default value change has no effect on how discounts are applied at checkout. If your app explicitly sets appliesOnSubscription when creating or updating app discounts, your behavior is unchanged. This change applies across all active API versions. The appliesOnOneTimePurchase field already defaults t

Your app's admin performance data is now available in the Dev Dashboard, alongside your existing monitoring tools. This change eliminates the need to switch between Partner Dashboard tabs to check web vitals. What's changed The admin performance dashboards have moved from the Partner Dashboard to the Dev Dashboard. You can now access daily and 28-day P75 rollups for three Core Web Vitals: LCP (Largest Contentful Paint): Measures loading performance. INP (Interaction to Next Paint): Assesses inte

<p>v18.10.0</p> <h3>🎉 New features</h3> <ul> <li>[eas-cli] Add <code>eas integrations:convex</code> commands to manage Convex integrations for EAS projects. (<a href="https://github.com/expo/eas-cli/pull/3575" data-hovercard-type="pull_request" data-hovercard-url="/expo/eas-cli/pull/3575/hovercard">#3575</a> by <a href="https://github.com/fiberjw">@fiberjw</a>)</li> </ul> <h3>🐛 Bug fixes</h3> <ul> <li>[eas-cli] Create portable project archives on all platforms to normalize cross-platform tar m

We have introduced a new actor field in subscription mutations to help you track who initiated an action - whether it was the customer, the merchant, or the partner app's automated system. You can now include an actor argument when creating billing attempts or editing subscription contracts. This field accepts the following values: customer : The buyer initiated the action (e.g., clicking "pay now" in a customer portal). merchant : A merchant or their staff manually initiated the action. partner

<p>v18.9.1</p>

<p>v18.9.0</p> <h3>🎉 New features</h3> <ul> <li>[eas-cli] Add <code>eas integrations:asc</code> commands to manage App Store Connect integrations for EAS projects. (<a href="https://github.com/expo/eas-cli/pull/3558" data-hovercard-type="pull_request" data-hovercard-url="/expo/eas-cli/pull/3558/hovercard">#3558</a> by <a href="https://github.com/sswrk">@sswrk</a>)</li> <li>[eas-cli] Allow <code>eas build:download</code> to accept a build ID. (<a href="https://github.com/expo/eas-cli/pull/3655"

You can now create and manage metric targets for merchants using four new GraphQL Admin API operations: analyticsTargets , analyticsTargetCreate , analyticsTargetUpdate , and analyticsTargetsDelete . With targets, merchants can set numeric goals for analytics metrics, such as "achieve $50K in gross sales this quarter," and track their progress with a visual gauge. The API has been available to apps from the start, enabling you to build on the same foundation that supports targets in the Shopify

Starting with POS version 11.5, we are updating the internal calculation method for custom fixed-amount line item discounts. These discounts will now be applied on a per-unit basis rather than across the entire line. Note that this change only affects fixed-amount discounts; percentage discounts remain unchanged. If your app uses setLineItemDiscount or bulkSetLineItemDiscounts from the Cart API with a FixedAmount discount type, you can continue to pass the total discount amount for the line item

As of POS version 11.5, merchants can generate scannable QR codes for any discount code in the Shopify Admin. These QR codes can be applied by both POS staff at checkout and by customers in online store sessions. What this means for discount apps No changes are required with this release. If your app creates discount codes, you can now generate QR codes for them that encode the store's discount URL. What you should do Shopify uses the format https://{shop}.myshopify.com/discount/{CODE} with the

Starting in API version 2026-07, the taxSettings field on the Customer object will be publicly accessible in the Admin GraphQL API. Apps with the read_customers or read_taxes access scopes can now query a customer's tax ID, such as a VAT number, which is collected and validated during checkout. This update aligns with the CompanyLocation.taxSettings.taxRegistrationId , which has been available since API version 2025-01 for B2B customers. Example query: { customer(id: "gid://shopify/Customer/cust

<p>v18.8.1</p>

Shopify Plus and Enterprise merchants will soon be able to enable a single checkout experience where customers can choose both shipping and store pickup within the same order. Previously, customers had to place separate orders for each delivery method. This change impacts how delivery and fulfillment information flows through checkout. If your app reads, calculates, or displays delivery and fulfillment information, the testing window is open now. Enable feature preview and make the necessary upd

What’s changing The following UCP catalog tools in Storefront Catalog are now available: - `search_catalog`: Search a store's product catalog with filters, pagination, and buyer context - `lookup_catalog`: Batch lookup products or variants by identifier with inputs correlation - `get_product`: Retrieve full product details with interactive variant selection, availability signals, and more Tool calls can be placed against the https://{storedomain}/api/ucp/mcp endpoint. What you should do The prev

We've updated the app uninstall reasons that appear in your Partner Dashboard. These changes better reflect why merchants uninstall apps, giving you clearer, more actionable insights to improve your app experience. The uninstall reason options merchants see have been revised to the following: Testing multiple apps Store is closing or pausing Not using app now Not satisfied with app features or support Expensive or unexpected cost Not working or compatible with store

<p>v18.8.0</p> <h3>🎉 New features</h3> <ul> <li>[eas-cli] Support custom params in <code>observe:events</code> results. (<a href="https://github.com/expo/eas-cli/pull/3620" data-hovercard-type="pull_request" data-hovercard-url="/expo/eas-cli/pull/3620/hovercard">#3620</a> by <a href="https://github.com/douglowder">@douglowder</a>)</li> <li>[build-tools] Add <code>eas/deploy</code> function for EAS Hosting web deployments. (<a href="https://github.com/expo/eas-cli/pull/3598" data-hovercard-type=

<h2>What's Changed</h2> <ul> <li><strong>Add <code>request_status</code> field to all affected list response types</strong> in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="4298102520" data-permission-text="Title is private" data-url="https://github.com/makenotion/notion-sdk-js/issues/711" data-hovercard-type="pull_request" data-hovercard-url="/makenotion/notion-sdk-js/pull/711/hovercard" href="https://github.com/makenotion/notion-sdk-js/pull/711">#711</a></

We updated the app submission experience to help apps get reviewed and published faster. Three changes are live now in the Partner Dashboard: End-to-end review management in Partner Dashboard Review feedback for app submissions now lives in the Partner Dashboard under App > Distribution. Each requirement now has its own status, reviewer comments, and a way to ask questions directly. You can see exactly what's outstanding and resubmit when everything is resolved. Requirement-level tracking: Each

The cartToken field is now available on the GraphQL Admin API's Order object. This field returns the token associated with the cart that was used to create the order, matching the existing cart_token field in the REST Admin API.

<p>v5.19.0</p>

The MOST_RELEVANT value is now available to the GraphQL Admin API's CollectionSortOrder , available in API version 2026-07 and higher. Learn more about collection sorting options in the Shopify Help Center .

Shopify is introducing CSS content subsetting for {% stylesheet %} tags to improve storefront performance. Starting April 20, 2026, Shopify only delivers the CSS from {% stylesheet %} tags that are relevant to the sections, blocks, and snippets rendered on each page, instead of serving all {% stylesheet %} CSS on every page load. What this means for your theme If your theme's CSS classes are self-contained – each file's {% stylesheet %} only styles HTML elements within that same file or its dire

We are updating the MetaobjectAdminAccess enum by deprecating the PRIVATE and PUBLIC_READ values. These values are now obsolete and are never returned by the API. This change removes ambiguity, as the deprecated access values do not accurately reflect the intended access behaviors. There are no required changes, but updating your code will help maintain clarity and prevent potential access issues.

<p>v18.7.0</p> <h3>🎉 New features</h3> <ul> <li>[build-tools] Add <code>eas/read_package_json</code> and <code>eas/read_app_config</code> functions (<a href="https://github.com/expo/eas-cli/pull/3585" data-hovercard-type="pull_request" data-hovercard-url="/expo/eas-cli/pull/3585/hovercard">#3585</a> by <a href="https://github.com/gwdp">@gwdp</a>)</li> <li>[eas-cli] Add <code>--skip-bundler</code> to <code>eas build:dev</code> to install and run a development build without starting the local Exp

New CSS Variable for Mobile Safe Area Insets A new CSS custom property, --shopify-safe-area-inset-bottom , is now available for embedded apps running on Shopify Mobile. This property provides the exact pixel value of host UI overlays, such as the floating bottom navigation bar, to prevent apps from placing fixed-position content over these overlays. The var(--shopify-safe-area-inset-bottom) is automatically set by App Bridge. It defaults to 0px when no overlay is present, and adjusts to the heig

<h2>What's Changed</h2> <ul> <li><strong>Support multi-value filters for select, status, and multi_select property filters</strong> in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="4234218539" data-permission-text="Title is private" data-url="https://github.com/makenotion/notion-sdk-js/issues/707" data-hovercard-type="pull_request" data-hovercard-url="/makenotion/notion-sdk-js/pull/707/hovercard" href="https://github.com/makenotion/notion-sdk-js/pull/707">#7

The LineItem object in the GraphQL Admin API now includes a [ priceAfterAllDiscountsBeforeTaxesSet ( https://shopify.dev/docs/api/admin-graphql/2026-07/objects/LineItem#field-LineItem.fields.priceAfterAllDiscountsBeforeTaxesSet ) field, which is equivalent to the REST API's current_subtotal_price_set on line items. This field returns the total price of a line item in both shop and presentment currencies after all discounts have been applied, excluding refunded and removed quantities. The value d

Starting June 15, 2026, Shopify will renew its mTLS client certificate used by Payments Apps to verify that the client initiating the request is Shopify. Unless you're using custom checks or validation logic, this update won't impact your live payments apps, as the new certificate is signed by the same Certificate Authority as the current one. Who's affected Payments Apps Reason for the change The current certificate will expire on July 24, 2026. It must be renewed before this date to ensure uni

Starting in version 2026-07 of the GraphQL Admin API , you can query the weight field on the LineItem type in the GraphQL Admin API. This field returns a Weight object with value and unit , making it easy to access line item weights without converting from the REST API's grams field.

What's changing We are removing the grams field from the DraftOrderLineItem object in the Admin GraphQL API, starting with version 2026-07. This field was deprecated over 8 years ago. After the 2026-04 API version becomes unsupported, any queries referencing DraftOrderLineItem.grams will return an error. What you need to do Replace any usage of grams with the weight field on DraftOrderLineItem . The weight field returns both a value and a unit, giving you more flexibility than the old grams inte

<p>v18.6.0</p> <h3>🎉 New features</h3> <ul> <li>[eas-cli] Add missing Apple metadata attributes for age ratings and content descriptions. (<a href="https://github.com/expo/eas-cli/pull/3584" data-hovercard-type="pull_request" data-hovercard-url="/expo/eas-cli/pull/3584/hovercard">#3584</a> by <a href="https://github.com/EvanBacon">@EvanBacon</a>)</li> <li>[eas-cli] Add App Clip metadata support to <code>metadata:push</code> and <code>metadata:pull</code> (default experience action, per-locale s

Mobile primary action now renders as an icon in the title bar On mobile, the primary and secondary actions defined on your TitleBar are changing how they render: The primary action now displays as an icon-only button in the mobile header, rather than in a bottom bar with icon and text. Secondary actions now appear in the overflow menu, creating a more consistent mobile interface. If you don't pass an icon property with your primary action, it defaults to a + (plus) icon. Who's affected All embed

The Hydrogen April 2026 release (v2026.4.0) is out. This release updates the Storefront API and Customer Account API to 2026-04 and includes breaking changes to consent handling and the API proxy. Updated Storefront API and Customer Account API to 2026-04 ( #3651 ) Breaking: The Storefront API proxy is now always enabled. The proxyStandardRoutes option has been removed from createRequestHandler . If your load context does not include a storefront instance, the request handler will throw an error

We are enhancing Shopify Functions with new capabilities for discounts, shipping, and payments. These improvements aim to replace the functionalities you previously achieved using Shopify Scripts, allowing you to build custom logic tailored to your unique business needs. To assist with your migration planning, we recommend using the Shopify Scripts customizations report . This tool will help you identify which of your current customizations can be transitioned to Shopify Functions or public apps

<p>Here’s everything that happened with Supabase in the last month:</p> <h2>Multigres Operator is now open source</h2> <p><a target="_blank" rel="noopener noreferrer" href="https://private-user-images.githubusercontent.com/30495040/575664480-a6ef072e-991d-4213-a7ba-ac036a2798d5.jpeg?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NzU3NTc5MjcsIm5iZiI6MTc3NTc1NzYyNywicGF0aCI6Ii8zMDQ5NTA0MC81NzU2NjQ0ODAtYTZ

In version 2026-04 of the GraphQL Admin API, we're introducing support for applying multiple product discounts on a single cart line. This feature will enable merchants to continue migrating Scripts ahead of the June 30th, 2026 sunset date. To learn more about configuring discount combinations, please refer to the documentation for the GraphQL Admin API .

<h2>What's Changed</h2> <ul> <li><strong>Add <code>markdown</code> parameter to Create Comment endpoint</strong> in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="4212929721" data-permission-text="Title is private" data-url="https://github.com/makenotion/notion-sdk-js/issues/703" data-hovercard-type="pull_request" data-hovercard-url="/makenotion/notion-sdk-js/pull/703/hovercard" href="https://github.com/makenotion/notion-sdk-js/pull/703">#703</a></li> <li><st

As of API version 2026-04, Shopify provides an official testing library for UI extensions. @shopify/ui-extensions-tester lets you write unit tests for extensions on any surface — Checkout, Admin, Customer Accounts, and POS — without a running Shopify host. What it does The library provides strongly typed mocks of the extension API, so you can render extensions in isolation, simulate user interactions, and verify behaviour against public APIs with full type safety. Key capabilities Render and que

The Shopify AI Toolkit is now available. With the Toolkit, you can build apps using Shopify's documentation, API schemas, and code validation, and manage your Shopify store through the CLI's store execute capabilities. We're also releasing a new plugin to install the Toolkit. The plugin auto-updates, so your agent stays up to date as we release new capabilities. Supported tools Claude Code Cursor Gemini CLI Visual Studio Code Codex CLI (skills and MCP only) Get started Plugin installation takes

<p>v18.5.0</p> <h3>🎉 New features</h3> <ul> <li>[eas-cli] Add screenshots and previews support to <code>metadata:push</code> and <code>metadata:pull</code>. (<a href="https://github.com/expo/eas-cli/pull/3301" data-hovercard-type="pull_request" data-hovercard-url="/expo/eas-cli/pull/3301/hovercard">#3301</a> by <a href="https://github.com/EvanBacon">@EvanBacon</a>)</li> <li>[eas-cli] Add <code>--non-interactive</code> flag to <code>metadata:push</code> and <code>metadata:pull</code> commands wi

As of API version 2026-04, the ability to read and write checkout metafields in checkout and customer account UI extensions has been removed. Instead, checkout metafields have been replaced by cart metafields in checkout UI extensions and order metafields in customer account UI extensions. Action Required If you are using checkout metafields in older API versions, it is essential to upgrade to version 2026-04. Follow our guides to ensure a smooth transition: Migrate to cart metafields in checkou

As of Customer Account API version 2026-04, the DraftOrderLineItem object includes a new components field. This field returns the individual component line items associated with a parent line item. Additionally, a new optional argument, flattenComponents , has been introduced to the DraftOrder.lineItems connection. For API versions 2026-04 and later, flattenComponents defaults to false , meaning only top-level line items are returned as nodes, with their components accessible via the DraftOrderL

We have introduced an expiresIn field to the DelegateAccessToken type, which is returned by the delegateAccessTokenCreate mutation. This addition allows app developers using delegate tokens to know precisely when their tokens will expire. The expiresIn field provides the number of seconds remaining until the token expires, aligning with the data available through the REST Admin API's delegate endpoint. This feature is particularly beneficial when the expiresIn input is not specified, causing the

We are introducing a new access field to the StandardMetaobjectDefinitionTemplate . This field will display the template's access rules, helping you determine if a specific template is configured for access via the Storefront API. By understanding these access rules, developers can plan their API interactions more effectively, ensuring seamless integration with the Storefront. The StandardMetaobjectDefinitionTemplate is a component that defines the structure and behavior of metaobjects within Sh

Polaris reference docs now follow the same versioning policy as Shopify's GraphQL APIs: Each stable version is supported for a minimum of 12 months. Older versions continue to work, they just won’t have dedicated docs on Shopify.dev. Shopify CLI already prevents deploys targeting API versions older than 12 months, so we recommend keeping your extensions on a supported version. Starting with the 2026-04 release, we'll only publish docs for the last four stable versions of these reference docs: Ad

App-owned metaobjects, identified by types such as $app:example , including those created using declarative metaobject definitions , can now be utilized by their owning app without requiring any access scopes. This change simplifies the process for developers by eliminating the need to request additional access scopes, thereby reducing potential merchant friction. If you are considering using declarative metaobjects in your app, you can now proceed without worrying about additional access scope

Discount functions now support prerequisites for product discount candidates, allowing you to define the "Buy X" portion of a Buy X, Get Y (BXGY) discount. In a BXGY discount, customers must purchase a specified quantity of one product (Buy X) to receive a discount on another product (Get Y). What's New: A prerequisites field has been added to product discount candidates. Each prerequisite is defined as a cartLinePrerequisite , which includes: id : The identifier for the cart line used as the pr

Starting in API version 2026-04, discounts support tags allowing you to efficiently label, group, and organize your discounts. What's new: The tags field has been added to all discount types Tags can be added, updated, and removed via the Admin API For more information, visit the Admin API documentation

As of API version 2026-04, you can validate billing addresses and purchase order (PO) numbers in Cart and Checkout Validation Functions. We've added billing address and PO Number to the function input graph and introduced new checkout field targets. This allows you to enforce compliance rules such as blocking prohibited billing countries and requiring PO numbers for B2B orders without relying upon client-side UI extensions. What's changed Input graph fields: billingAddress and poNumber are avail

Sales channel apps can now create and manage multiple channel connections from a single app. A single app can now establish more than one channel on a shop, with a separate specification and/or external account for each connection. Why this matters If you build a sales channel app that needs separate connections for different accounts or to sell in different markets or have different surfaces, you no longer need to split that model across multiple apps. You can keep those connections inside one

As of API version 2026-07, the payment method identifier field is now required when using the customerPaymentMethodRemoteCreate mutation with Stripe, Authorize.net, or Braintree inputs. The affected fields are: paymentMethodId on RemoteStripePaymentMethodInput customerPaymentProfileId on RemoteAuthorizeNetCustomerPaymentProfileInput paymentMethodToken on RemoteBraintreePaymentMethodInput These fields were previously optional at the schema level but are required for the payment method to be funct

In the API 2026-04 release candidate version, you can now include a new field called paymentProcessingPolicy when creating a billing attempt using the subscriptionBillingAttemptCreate mutation. A billing attempt is an action to charge a customer based on their subscription. The paymentProcessingPolicy field determines how the billing attempt is handled depending on the validity of the payment method: If you don't provide the paymentProcessingPolicy field, or if you set it to FAIL_UNLESS_VALID_PA

In the API 2026-04 release candidate version, the paymentMethodId field is no longer required when creating a subscription contract using the subscriptionContractAtomicCreate and subscriptionContractCreate mutations. This allows you to migrate subscription contracts even if they have missing or expired payment methods. For implementation instructions, see our docs on how to build a subscription contract .

As of API Version 2026-04 third-party logistics providers (3PLs) and fulfillment apps can now report progress on fulfillment orders with the fulfillmentOrderReportProgress mutation . This feature enables fulfillment services to indicate that work has commenced and, optionally, add brief status notes so merchants see what’s happening in their fulfilment pipeline. Key Details: Reporting progress for 3PL-managed orders works with fulfillment orders in IN_PROGRESS status Reporting progress for merch

The Payments Apps API now provides more granular decline reason codes for rejected payment sessions. Multiple new rejection codes have been added to the PaymentSessionStateRejectedReason enum alongside a new source field, giving payments apps more standardized, actionable ways to communicate to merchants why a payment was declined. New rejection reason codes The following error codes expand the existing set of rejection reasons with more specific rejection information: | Error Code | Description

<h2>What's Changed</h2> <ul> <li>Add icon support to paragraph blocks (tab block items) by @notion-buildkite-app[bot] in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="4147054662" data-permission-text="Title is private" data-url="https://github.com/makenotion/notion-sdk-js/issues/697" data-hovercard-type="pull_request" data-hovercard-url="/makenotion/notion-sdk-js/pull/697/hovercard" href="https://github.com/makenotion/notion-sdk-js/pull/697">#697</a></li> <l

We have revamped the way partner organizations manage users and stores. Role-based Access Control: Assign roles to users instead of configuring permissions individually. We offer seven system roles that cover organization-wide administration, store access, app development, and merchant-granted collaborator permissions. You can also create custom roles for any needs not covered by the system roles. New Organization Structure: Partner organizations now have one Organization Owner and multiple Orga

As of March 23, 2026, customer data erasure requests will no longer be held in a pending state for 180 days from the date of the customer's most recent order. Erasure requests will now be processed 10 days after the request was submitted, regardless of when the customer's most recent order was placed. For recipients of gift cards that have been scheduled to send, the erasure request will remain in a pending state until the gift card has been delivered. This update simplifies the overall experien

<h2>What's Changed</h2> <ul> <li>Sync api-endpoints: tab block support, verification property updates by <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/ksinder/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/ksinder">@ksinder</a> in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="4122128086" data-permission-text="Title is private" data-url="https://githu

We are deprecating the --force flag on the shopify app deploy and shopify app release commands. The flag will be removed in a Shopify CLI release in May 2026. Why we're making this change The --force flag skips all confirmation prompts, including for extension deletions that can permanently remove data on installed shops. It doesn't distinguish between low-risk operations (adding or updating extensions) and high-risk ones (deleting them). The previously released --allow-updates and --allow-delet

The pre_tax_price and pre_tax_price_set fields on order line items in the REST Admin API are being removed. These fields were previously available to stores with the Avalara AvaTax 1.0 integration enabled, which was deprecated in April 2025. What you should do Use the GraphQL Admin API to access order line item pricing data.