Developer changelog
Subscribe to the changelog to stay up to date on recent changes to Shopify’s APIs and other developer products, as well as preview upcoming features and beta releases.
RSS updatesThere are no entries for your filter criteria.
September 25, 2024
Changing the default value of permitsSkuSharing argument in fulfillmentServiceCreate API
As of 2025-01
, the default value for the permitsSkuSharing
argument in the fulfillmentServiceCreate
mutation has been updated to true.
Please be aware that this argument is deprecated and will be removed in the version 2025-04
. Consequently, all fulfillment services will be required to permit SKU sharing by default.
September 20, 2024
Introducing metafield definition capabilities in the admin API API
As of API version 2024-10, we're launching an API to manage metafield definition capabilities. This new feature provides a flexible and extensible way to define and manage behaviors for metafield definitions across various Shopify features.
What's new?
Metafield definition capabilities can be easily enabled, disabled, and queried through the Admin API
What's next?
In future API versions, we'll be introducing new capabilities to enhance metafield functionality across various Shopify features. Stay tuned for announcements about specific capabilities and how they can benefit your app or integration.
Learn more about metafield capabilities at Shopify.dev
September 20, 2024
Action required
Metafield Definition Capability Framework and Deprecation of use_as_collection_condition
API
As of API version 2024-10, we're introducing the Metafield Definition Capability Framework and deprecating the use_as_collection_condition
field on the Metafield Definition object. The new smart_collection_condition
capability will replace the deprecated field, providing a more flexible and extensible way to manage metafield behaviors in smart collections.
What's changing?
- The
use_as_collection_condition
field on Metafield Definitions is being deprecated. - A new
smart_collection_condition
capability is being introduced as part of the Metafield Definition Capability Framework.
Why it matters
The new Capability Framework offers several benefits:
- Improved flexibility: Capabilities can be easily added, removed, or modified without changing the core Metafield Definition structure.
- Better extensibility: New capabilities can be introduced in the future without affecting existing implementations.
- Clearer semantics: Capabilities provide a more explicit way to define metafield behaviors.
How to update
To prepare for this change, update your API calls and app logic as follows:
- Instead of setting
use_as_collection_condition: true
, use:
capabilities: {
smartCollectionCondition: {
enabled: true
}
}
- When querying metafield definitions, check the
smart_collection_condition
capability instead of theuse_as_collection_condition
field:
query {
metafieldDefinition(id: "gid://shopify/MetafieldDefinition/1234") {
capabilities {
smartCollectionCondition {
enabled
}
}
}
}
Timeline
- API version 2024-10: The new capability is available, and
use_as_collection_condition
is deprecated but still functional. - Future version: The
use_as_collection_condition
field will be removed entirely.
We recommend updating your integrations to use the new capability as soon as possible to ensure a smooth transition.
Learn more about metafield capabilities at Shopify.dev Learn more about the Metafield Definition Capability Framework at Shopify.dev.
September 19, 2024
New inventory input fields in productSet mutation in version 2024-10 API
As of GraphQL API version 2024-10
, we are adding new inventory capabilities in the productSet mutation, in the form of a new field type ProductSetInventoryInput
, which allows setting available
or on_hand
quantities for new and existing product variants on locations specified.
This type can be used in the following contexts:
ProductSetInput.inventoryQuantities
field to specify inventory quantities for products with no custom variants.ProductSetVariantInput.inventoryQuantities
field to specify inventory quantities for individual custom variants.
For more detailed information and examples, visit our productSet documentation on Shopify.dev.
September 18, 2024
Shopify CLI is now easier to install and faster for Liquid theme development Themes
Today, a new version of Shopify CLI is available, bringing with it a better development experience that streamlines your setup for building Shopify themes.
The update includes the following improvements:
- Instant development server startup, so there's no need to wait for synchronization before opening a browser.
- No dependency on Ruby and unified commands implementation on TypeScript, which streamlines your development cycle with easier install & setup.
- A headless Liquid console, so you can run
shopify theme console
without opening a browser for authentication.
Learn more about Shopify CLI for themes. Happy coding!
September 18, 2024
New Full-Funnel Theme Install Parameters and Now Firing E-Commerce Events on the Theme Listing Page Themes
Two new paremeters have been added to the full-funnel theme install event for the Shopify Theme Store - shop_name
and shop_url
. These enhancements provide more insights on which merchant is installing a theme.
Learn more about the new parameters and full-funnel attribution in the Shopify Theme Store docs.
On the theme listing pages, Google e-commerce events have also been implemented to enhance tracking capabilities. The events view_item and addtocart will now be sent to Google Analytics, allowing for more precise data analysis.
For further details, check out the section on Google e-commerce events in the Shopify Theme Store docs.
September 18, 2024
JavaScript Shopify Functions are now ~40% faster Tools
As of Shopify CLI 3.67 and Javy 3.1, Shopify Functions built in JavaScript can see improved performance by as much as 40% when combined with @shopify/shopify_function 1.0
Learn more about JavaScript for Shopify Functions on Shopify.dev.
September 18, 2024
New Full-Funnel App Install Parameters and Now Firing E-Commerce Events on the App Listing Page Shopify App Store
Two new paremeters have been added to the full-funnel app install event for the Shopify App Store - shop_name
and shop_url
. These enhancements provide more insights on which merchant is installing an app.
Learn more about the new parameters and full-funnel attribution in the Shopify App Store docs.
On the app listing pages, Google e-commerce events have also been implemented to enhance tracking capabilities. The events view_item and addtocart will now be sent to Google Analytics, allowing for more precise data analysis.
For further details, check out the section on Google e-commerce events in the Shopify App Store docs.
September 18, 2024
Product Feed webhooks now support per-market inventory API
The quantityAvailable
and availableForSale
fields will now reflect country-specific inventory availability, scoped to the specified market country of the Product Feed. The Fulfillable Inventory feature must be enabled on the shop.
Learn more about Fulfillable Inventory on the Shopify help docs.
September 17, 2024
Post-purchase offers limit is increased Platform
The number of post-purchase upsell offers that customers can accept has been increased from two to three. With this change, merchants can increase their order value even more through post-purchase upsell offers.
We highly recommend that you review any custom code that pertains to post-purchase offers to ensure an optimal buyer experience.
Learn more about post purchase offers on shopify.dev
September 17, 2024
Action required
Improvements in the GiftCard GraphQL endpoints and introducing GiftCardTransaction types API
As of the GraphQL Admin API version 2024-10, we're improving the GiftCard
endpoints and introducing GiftCardTransaction
types. The gift card endpoints are now open to all apps and shops, with no additional approval scopes or flags required.
We have added the following mutations:
giftCardDeactivate
renamed fromgiftCardDisable
(deprecated).giftCardCredit
to apply credit to a gift card returning aGiftCardCreditTransaction
.giftCardDebit
to apply debit to a gift card returning aGiftCardDebitTransaction
.giftCardSendNotificationToCustomer
to send the notification to the customer.giftCardSendNotificationToRecipient
to send the notification to the recipient.
We have updated the following mutations:
giftCardCreate
to addrecipientAttributes
.giftCardUpdate
to addrecipientAttributes
.
We have added and modified fields in the GiftCard
object:
- Added
updatedAt
. - Added
recipientAttributes
. - Added
transactions
returning all transactions created by credits and debits. - Renamed
disabledAt
todeactivatedAt
(deprecated).
Developer action required
Developers using the existing giftCardDisable
mutation will need to replace it with giftCardDeactivate
Developers using the disableAt
property on the GiftCard
object will need to replace it with deactivatedAt
To learn more about gift cards, refer to the gift cards documentation. To learn more about gift card recipient functionality, refer to the help center documentation for recipient fields
September 16, 2024
Action required
The fulfillmentOrdersReleaseHolds Mutation Is Deprecated API
As of the Admin API version 2024-10, the fulfillmentOrdersReleaseHolds mutation has been deprecated.
Apps using this mutation should migrate to using the fulfillmentOrderReleaseHold mutation instead.
September 16, 2024
Admin API includes urlRedirectsCount
API
As of Admin GraphQL API version 2024-10
, you can access QueryRoot.urlRedirectsCount
field to retrieve the count of redirects.
Learn more about urlRedirectsCount
on Shopify.dev.
September 16, 2024
New query attributes on products query API
As of the 2024-10 version of the GraphQL Admin API, the products
query filter has been expanded to allow filtering on additional attributes: publication_ids
, variant_id
and variant_title
.
Check out all products query attributes at shopify.dev for more details.
September 13, 2024
Action required
Field deprecations on the abandoned checkout REST API API
The following fields have been deprecated from the Abandoned Checkout REST API: cart_token
, closed_at
, currency
, gateway
, landing_site
, fulfillment_service
, grams
, presentment_currency
, referring_site
, shipping_lines
, token
and total_weight
fields
As of 2024-10, the endpoint is available via the newly published GraphQL abandoned checkout API.
September 13, 2024
Fulfillment Holds Now Able To Be Released by ID API
As of the GraphQL Admin API version 2024-10, a id
field is being added to the FulfillmentHold
GraphQL object.
As of the GraphQL Admin API version 2024-10, an optional holdIds
argument is being added to the fulfillmentOrderReleaseHold mutation. This will give apps the ability to release a hold by ID, ensuring that only the intended hold is released. It is highly recommended that apps supply the ids of any holds when releasing them. Releasing all holds on a fulfillment order will result in the fulfillment order being released prematurely and items being incorrectly fulfilled.
September 13, 2024
Admin API includes statusPageUrl
field on Order
API
As of Admin GraphQL API version 2024-10
, you can access Order.statusPageUrl
field to retrieve the URL where the customer can check the order's current status.
Learn more about Order
on Shopify.dev.
September 12, 2024
Customer SMS Consent Collected From now returns Shopify when the buyer consents to SMS marketing in Shopify Checkout API
As of September 12, 2024, the CustomerConsentCollectedFrom
field will return SHOPIFY
whenever SMS consent is captured in Shopify Checkout. Previously, it would return OTHER
if the buyer consented to SMS marketing in checkout, but the sales channel of the checkout was not one owned by Shopify (Example, online store checkouts would return SHOPIFY
while custom storefronts would return OTHER
).
This applies to both the 1st party SMS consent UI, as well as any checkout UI extensions using the ConsentCheckbox
or ConsentPhoneField
UI components.
Other SMS consent capture flows are unaffected.
September 12, 2024
Hydrogen September 2024 release Platform
Hydrogen v2024.7.5 is out today. The September 2024 Hydrogen release contains several optimizations and bug fixes, including:
- Improved sitemaps (unstable) (#2478)
- Skeleton template search enhancements (#2363)
- Cart gift card support (#2298)
- Consent localization (#2457)
- Improved content security policy implementation (#2500)
- Infinite redirect fix for with URLs with
//
(#2449) - Improved
useOptimisticCart
to optimistically calculate totals (#2459) - Skeleton template mobile device link fix (#2450)
- Utilities
privacyBanner
andcustomerPrivacy
have been added touseAnalytics
anduseCustomerPrivacy
(#2457)
Check out our full Hydrogen September 2024 release blog post for more details. And please drop your comments, feedback, and suggestions in GitHub Discussions!
September 11, 2024
Action required
Introducing PRODUCT_CATEGORY_ID in CollectionRuleColumn and Deprecating PRODUCT_TAXONOMY_NODE_ID for automated collection creation API
As of API version 2024-10, we're adding the new PRODUCTCATEGORYID as a column for the CollectionRuleColumn
which is used to create automated collections. This field maps directly to the newly added Product Category as defined in the updated standard product taxonomy and will allow for the creation of smart collections based on this new category tree.
What's new?
- Introduction of
PRODUCT_CATEGORY_ID
Column: We are introducing a new column,PRODUCT_CATEGORY_ID
, in theCollectionRuleColumn
. This column will directly map to the category ID of a product, allowing for more precise and efficient collection rule creation based on product categories as defined in the updated standard product taxonomy.
What's deprecated?
- Deprecation of
PRODUCT_TAXONOMY_NODE_ID
Column: ThePRODUCT_TAXONOMY_NODE_ID
column is being deprecated. This column previously used the now-deprecatedproductCategory
field on products, the previous method for categorising products before the updated standard product taxonomy was introduced this year. Developers should transition to using the newPRODUCT_CATEGORY_ID
column to ensure newly created products that necessarily use the updated product taxonomy are included in automated collections as expected.
Developer action required
Developers are encouraged to update their implementations to use the new PRODUCT_CATEGORY_ID
column when specifying product attributes for populating smart collections. The deprecated PRODUCT_TAXONOMY_NODE_ID
will remain functional but is scheduled for removal in a future API version. Transitioning early will ensure smoother operations and access to the enhanced functionality provided by the new schema.
Example of updated usage
To create a smart collection using the new PRODUCT_CATEGORY_ID
, modify the collection creation mutation as follows:
mutation CollectionCreate($input: CollectionInput!) {
collectionCreate(input: $input) {
userErrors {
field
message
}
collection {
id
title
descriptionHtml
handle
sortOrder
ruleSet {
appliedDisjunctively
rules {
column
relation
condition
}
}
}
}
}
{
"input": {
"title": "Our entire shoe collection",
"descriptionHtml": "View <b>every</b> shoe available in our store.",
"ruleSet": {
"appliedDisjunctively": false,
"rules": {
"column": "PRODUCT_CATEGORY_ID",
"relation": "EQUALS",
"condition": "gid://shopify/TaxonomyCategory/aa-5"
}
}
}
}
Learn more about collection creation at [Shopify.dev](https://shopify.dev/docs/api/admin-graphql/latest/mutations/collectionCreate)
September 10, 2024
Updates to webhook retry mechanism API
Webhooks will now be retried a total of 8 times over 4 hours using an exponential backoff schedule. This should allow sufficient time for transient errors to be resolved.
When webhooks are retried, they will be delivered with the original payload from the time they were triggered. Partners should utilize the X-Shopify-Triggered-At
timestamp in the header, or a timestamp from the payload to determine if the payload is stale.
Retried webhooks will be delivered to the subscription's address that was configured when the webhook was triggered. Updating the subscription's address during a retry cycle will not result in the webhook being delivered to the new address. When migrating webhooks to a new endpoint, it is recommended to keep both endpoints active for a short period of time to ensure a smooth transition.
These changes aim to improve the consistency, efficiency and reliability of webhook delivery while minimizing the impact on partners.
September 09, 2024
Static app navigation for admin apps is no longer supported Tools
Static app navigation for admin apps is no longer supported. Creation and editing of static navigation are no longer available on the the Partners dashboard. You can delete existing menus using the Partners dashboard until December 2024. After December 2026, static navigation items will be automatically removed from apps.
To configure app navigation, use the App Bridge navigation menu web component or React component to add navigation to your app and delete the existing navigation items from the Partners dashboard.
September 09, 2024
Action required
Removing V2 suffix from fulfillmentCreateV2 and fulfillmentTrackingInfoUpdateV2 API
As of 2024-10
, we're deprecating fulfillmentCreateV2
and fulfillmentTrackingInfoUpdateV2
. Instead, please use fulfillmentCreate
and fulfillmentTrackingInfoUpdate
.
Note that the behavior of the new mutations remains the same as the previous ones; the only change is the removal of V2 to ensure consistent naming across all mutations.
September 09, 2024
Action required
The REST location resource requires locations
scope
API
As of the 2024-10 release of the Admin REST API, the location resource will be gated by the locations
scope.
Attempting to access the location resource without the read_locations
scope will return a 403 Forbidden
error.
If your app gets the location resource, then you will need to request the correct read_locations
scope before migrating to the 2024-10 API version.
September 06, 2024
Fresh theme rows for Theme Store homepage Shopify Theme Store
To help merchants discover the freshest and most well-integrated themes for their store, we've shipped an update to the Theme Store homepage to highlight Top and New themes (published in the last 60 days).
September 05, 2024
Storefront Product Taxonomy Category API API
As of GraphQL Storefront API 2024-10, you can now retrieve product taxonomy categories in storefronts. This information is also available through the Liquid API.
This will allow you to customize the buyer experience in storefronts based on product taxonomy. Learn more about product taxonomy in our help docs.
See Shopify.dev for documentation on the new Liquid object and the upcoming GraphQL type.
September 04, 2024
Allow item activation at legacy location API
As of Graphql Admin Api version 2024-10, calls to mutation inventoryActivate
can use an optional parameter stockAtLegacyLocation
. Setting this parameter to true
will allow inventory to be activated if the locationId
provided is associated with a fulfillment service that does not permit sku sharing.
If an item is activated at a location that does not permit sku sharing then the item will be deactivated at all other locations.
If an item is currently active at a location that does not permit sku sharing and you want to activate that item at another location the stockAtLegacyLocation
parameter also needs to be set to true.
Learn more about inventoryActivate
on Shopify.dev
August 30, 2024
Action required
ReverseFulfillmentOrderLineItem.fulfillmentLineItem field is nullable as of 2024-10 API
As of 2024-10, ReverseFulfillmentOrderLineItem.fulfillmentLineItem
field is nullable. A ReverseFulfillmentOrderLineItem
will not always be associated with a FulfillmentLineItem
anymore. The non-null fulfillmentLineItem
field on the older API versions will return a graphql error when the fulfillment line item does not exisit.
Learn more about ReverseFulfillmentOrderLineItem
on Shopify.dev.
August 27, 2024
Admin API removes lineItemsMutable
field on Order
API
As of Admin GraphQL API version 2024-10
, use Order.lineItems
instead of lineItemsMutable
field to get a list of the order's line items.
Learn more about Order
on Shopify.dev.
August 26, 2024
Customer, Order, Company, and Model3d GraphQL types available in MetafieldReference union for 2024-01 and onward API
We are retroactively adding Customer, Order, Company, and Model3d graphql types to the MetafieldReference union for Admin API from 2024-01 and onward.
Additionally, TaxonomyValue will be added in 2024-04 to align with the version the type was introduced.
August 26, 2024
Action required
Protected customer data access required to use the Customer Account API API
We are requiring apps to meet at least Level 1 Protected Customer Data Requirements in order to access the Customer Account GraphQL API. This change is applicable to all API versions. We recognize that this may be a breaking change for public apps that use the Customer Account API and is necessary to ensure the protection of customer data.
This change will not impact Hydrogen and Headless storefronts or Custom Apps since they already have access to Level 1 and Level 2 Protected Customer data.
Partners that are part of the Customer Account UI Extensibility developer preview and are calling the Customer Account API from their extensions will need to request access to continue to access the API.
Learn more about Protected Customer Data on shopify.dev.
August 26, 2024
Adding productVariantsCount
GraphQL field.
API
As of 2024-10
version, we are adding productVariantsCount
field to the Admin GraphQL API.
Learn more about productVariantsCount on Shopify.dev.
August 23, 2024
Built for Shopify Technical criteria checklist has been updated Built for Shopify
The following changes have been made:
- Technical criteria checklist has been renamed to
Technical criteria
- App distribution page layout has been updated, and the content for some standards have been re-worded for clarity.
- Added: A new section
Category-specific criteria
to outline criteria for specific app features. - Renamed:
Build for performance
is nowPerformance
. - Renamed:
Usefulness criteria
is nowMerchant utility
- Combined:
Protect app safety, security, and reliability
andDesign for ease of use
are nowDesign and functionality
- Removed:
Share app info and benefits
along with the standardMake sure your app listing content is up-to-date
. This standard was intended to encourage completion of new app listing form fields introduced in the past, which all partners now have completed.
- Added: A new section
August 23, 2024
Updates to Feature Filters, Theme Listing & Partner Pages Shopify Theme Store
- Merchants can now filter themes by 3 new features: "Quick Order List", "Sign in with Shop" & "Swatch Filters". And we have removed 3 feature filters: "Product reviews", "Event Calendar" & "Store Locator".
- Each Theme's listing page has been updated to include quality signals and new styling.
- The order of Theme cards on your Partner-specific "All Theme Page" has changed to be "Newest to Oldest".
August 23, 2024
Remove unused error codes from LocationDeactivateUserErrorCode API
As of the 2024-10 release of the GraphQL Admin API, we're removing the error codes: HAS_OPEN_TRANSFERS_ERROR
and FAILED_TO_RELOCATE_OPEN_TRANSFERS
from LocationDeactivateUserErrorCode.
The error codes were not being returned from the LocationDeactivate
mutation, as such, they will no longer be listed as possible error codes.
If you are explicitly checking either of these error codes, you should remove references to them.
August 21, 2024
ShopifyPaymentsAccount GraphQL Admin API unused fields removed API
As of GraphQL Admin API version 2024-10, we're cleaning up the shopifyPaymentsAccount
endpoint and removing several unused fields.
August 21, 2024
Shopify Functions log streaming and replay is now generally available Tools
As of Shopify CLI 3.66, log streaming and replay for Shopify Functions is generally available.
Log streaming for Shopify Functions enables faster development, testing, and debugging of functions by bringing function execution logs to Shopify CLI. You can also replay function executions locally using input from these logs.
Learn more about Shopify Functions log streaming on Shopify.dev.
August 20, 2024
Action required
Breaking changes to media in GraphQL API's ProductSet mutation in version 2024-10 API
As of GraphQL API version 2024-10
, we are expanding media capabilities in the productSet mutation:
We are adding a new field type
FileSetInput
, which is a derivative of the FileCreateInput, with an addedid
field, which results in being able to both work with already existing media and create new files while using the same type.ProductSet.mediaIds
field is being removed and replaced with the new**files**
field, which expands the former's functionality by allowing you to also create new files to be associated with the product specified. This field utilizes the newFileSetInput
type.ProductSetVariantInput.mediaId
is being removed and replaced with**file**
field, which will associate the file with the variant. This field utilizes the newFileSetInput
type.
For more detailed information and examples, visit our productSet documentation on Shopify.dev.
August 19, 2024
Metafields and metaobjects reserved prefixes now supported in theme app extensions Platform
When accessing metafield namespaces or metaobject types, you no longer need to hard code app--{app_id}
. The $app
reserved prefix is now available to use in your Liquid files.
Learn more about using reserved prefixes in theme app extensions on Shopify.dev developer docs.
August 16, 2024
Action required
Developer Preview: Accelerated Checkout Buttons on storefront now support Shopify Functions, Bundles, and have improved performance Themes
We have improved the design and function of Dynamic Checkout and Accelerated Checkout buttons on storefront pages. These updates ensure that the buttons now support features like Shopify Functions and Product Bundles, providing better performance and a smoother user experience. These changes are now live on development stores and will begin rolling out to all merchants September 15.
Please note that the Accelerated Checkout buttons now hide their HTML in a custom element with a closed shadow DOM. This means that any styling or event tracking that targets the existing HTML structure of these buttons will break.
Please review this guide and the Accelerated checkout button reference to ensure your customizations remain compatible with the latest updates.
August 15, 2024
Storefront API changes when Cart ID is missing the key param API
We are modifying how cart queries and mutations behave when the Storefront API Cart ID is missing the key param. This behavior is applied retroactively to all versions of the Storefront API.
An example cart ID: gid://shopify/Cart/c1-7a2abe82733a34e84aa472d57fb5c3c1?key=824bdj25mhg1242bdb385
Queries: Querying a cart without including the key param will result in a cart with the buyer's private details removed.
Mutations Updating a cart without including the key param will result in an error :
The specified cart does not exist
.
August 15, 2024
Action required
Deprecation Notice: ProductChangeStatus
in Admin GraphQL API
API
We are deprecating productChangeStatus mutation. Use productUpdate mutation instead.
You will need to migrate to the new endpoint by January 2025 when we will remove access to the productChangeStatus
mutation.
Learn more about product mutations at shopify.dev
August 14, 2024
Theme cards being updated Shopify Theme Store
Theme cards on the Theme Store have been updated. Theme cards are now:
- Visually simpler (feature tags have been removed)
- Have a link to the listing for the Theme title
- Have a badge to identify Themes that are new to the Theme Store
- Show a Themes percentage positive reviews, and the number of reviews it's received
No action is needed from Theme developers.
August 14, 2024
Updating *new* Theme promotion period Shopify Theme Store
We are extending the promotion period for new Themes. Now, new Themes will be highlighted for a longer period than before.
August 13, 2024
Link metafield type now supported in metafield Liquid filters Themes
We've added support for the Link
metafield type to the metafield_tag
filter in Liquid.
Furthermore, you can now consume Link
metafields using dynamic sources in inline_richtext
and richtext
theme settings. Link
metafields will be inserted with the metafield_tag
filter by default for these setting types.
Learn more about metafield filters in Shopify.dev
August 13, 2024
Error messages available in the Shopify Pixel Helper Tools
We've added error messages to the Shopify Pixel Helper so that you can more easily debug your custom pixels. The Pixel Helper will display uncaught errors that occur at the top level or in the callback function. Top level errors will be viewable when the Pixel Helper loads. Callback error messages will be viewable when an event with a red dot is expanded.
August 12, 2024
Action required
Removing MetafieldStorefrontVisibility-related fields and mutations from Admin GraphQL API API
As of the GraphQL Admin API version 2024-10, we're removing a number of MetafieldStorefrontVisibility
-related fields, queries, and mutations.
Use the more flexible MetafieldDefinition.access
field instead.
- We're removing
MetafieldDefinition.visibleToStorefrontApi
.- Use
MetafieldDefinition.access
instead.
- Use
- We're removing
MetafieldDefinitionInput.visibleToStorefrontApi
.- Use
MetafieldDefinitionInput.access
instead.
- Use
- We're removing
MetafieldDefinitionUpdateInput.visibleToStorefrontApi
.- Use
MetafieldDefinitionUpdateInput.access
instead.
- Use
- We're removing
metafieldStorefrontVisibilityCreate
- Use
MetafieldDefinitionUpdate
instead.
- Use
- We're removing
metafieldStorefrontVisibilityDelete
- Use
MetafieldDefinitionUpdate
instead.
- Use
- We're removing
metafieldStorefrontVisibilities
- Use
MetafieldDefinition.access
instead.
- Use
- We're removing
metafieldStorefrontVisibility
- Use
MetafieldDefinition.access
instead.
- Use
Learn more about MetafieldDefinition.access
at https://shopify.dev/docs/api/admin-graphql/2024-07/objects/MetafieldAccess
August 12, 2024
New fields added to the Address Autocomplete API API
Address autocomplete apps can now set latitude, longitude and company name when an address suggestion is selected during checkout. If provided, the coordinates of a delivery address are sent to the Carrier Service API when calculating shipping rates. The company name field can be populated in checkout if the field is enabled for the merchant’s store.
August 09, 2024
Hydrogen August 2024 release Platform
Hydrogen v2024.7.3 is out today. The August 2024 Hydrogen release contains several quality-of-life improvements, optimizations and bug fixes:
- Custom
.env
file support (#2392) - Improved performance of currency formatting (#2372)
- Improved handling of
remix.config.js
/vite.config.js
files (#2379) - Simplified context creation with a new
createHydrogenContext
function (#2333) - Script component now takes a
waitForHydration
prop (#2389) - Google web cache fix (#2334)
- Custom logger support for
vite.config.js
. (#2341) - Subrequest profiler virtual root fix (#2344)
- CLI: Auth flow fix. (#2331) \
Check out our full Hydrogen August 2024 release blog post for more details. And please drop your comments, feedback, and suggestions in GitHub Discussions!
August 09, 2024
Added new access
argument to standardMetafieldDefinitionEnable
and standardMetafieldDefinitionsEnable
GraphQL mutations
API
As of the GraphQL Admin API version 2024-10, an access
argument is being added to the standardMetafieldDefinitionEnable
and standardMetafieldDefinitionsEnable
GraphQL mutations.
As of the GraphQL Admin API version 2024-10, we're deprecating the visibleToStorefrontApi
argument on the standardMetafieldDefinitionEnable
and standardMetafieldDefinitionsEnable
GraphQL mutations. Use the new access
argument instead.
The new access
argument allows developers to specify more granular access controls when enabling a standard metafield definition template.
Learn more about standardMetafieldDefinitionEnable
and standardMetafieldDefinitionsEnable
at https://shopify.dev/docs/api/admin-graphql/2024-10/mutations/standardMetafieldDefinitionEnable and https://shopify.dev/docs/api/admin-graphql/unstable/mutations/standardMetafieldDefinitionsEnable.