Skip to content

Remove version-dated callouts from API descriptions#4388

Merged
sordaz00 merged 2 commits into
2025-07from
fix/remove-version-dated-callouts-2025-07
Apr 30, 2026
Merged

Remove version-dated callouts from API descriptions#4388
sordaz00 merged 2 commits into
2025-07from
fix/remove-version-dated-callouts-2025-07

Conversation

@sordaz00
Copy link
Copy Markdown
Contributor

Summary

Cascade of #4384 to 2025-07. Strip "as of version YYYY-MM" from deprecation notices and caution blocks. Includes additional cleanups specific to 2025-07:

  • storefrontUrl: Removed trailing-slash caution; states current behavior directly
  • metafields: Removed Storefront API version requirement from tip
  • storage: Removed old per-target storage migration note
  • instructions: Removed version date from caution
  • extensionPoint: Simplified @deprecated tag

Test plan

  • Verify generated docs no longer show version-dated callouts

Made with Cursor

Strip "as of version YYYY-MM" from deprecation notices, caution blocks,
and tips. Includes additional 2025-07-specific cleanups for storefrontUrl,
metafields, and storage descriptions.

Made-with: Cursor
@github-actions
Copy link
Copy Markdown
Contributor

🚨🚨🚨 Docs migration in progress 🚨🚨🚨

We are actively migrating UI extension reference docs to MDX in the areas/platforms/shopify-dev zone of the monorepo. This impacts docs for the following surfaces:

During this migration, please be aware of the following:

.doc.ts files are being deprecated. Changes to .doc.ts files in this repo will not be reflected in the new MDX-based docs. If you need to update docs for a reference that has already been migrated, make your changes directly in the areas/platforms/shopify-dev zone of the monorepo instead.

Doc comments in .ts source files (the comment blocks above types and functions) are also affected. Generating docs from these comments currently requires a newer version of the @shopify/generate-docs library that isn't yet available. Updates to doc comments may not produce the expected output until the migration is complete.

Examples that previously lived in this repo are being moved to the areas/platforms/shopify-dev zone of the monorepo and should be authored there going forward.

What should I do?

  • If your PR includes changes to .doc.ts files, doc comments, or examples, please reach out to us in #devtools-proj-templated-refs so we can help ensure your updates are captured correctly.
  • If your PR is limited to source code changes (non-docs), you can ignore this notice.

Thanks for your patience while we complete the migration! 🙏

@github-actions
Copy link
Copy Markdown
Contributor

We detected some changes in packages/*/package.json or packages/*/src, and there are no updates in the .changeset directory. If the changes are user-facing and should cause a version bump, run yarn changeset to track your changes and include them in the next release CHANGELOG. If you are making simple updates to repo configuration, examples, or documentation, you do not need to add a changeset.

Copy link
Copy Markdown
Contributor

@mcvinci mcvinci left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, @sordaz00! Left a few suggestions for consideration.

* > Caution: As of version `2024-07`, UI extension code must check for instructions before calling select APIs in case those APIs are not available.
* See the [update guide](/docs/api/checkout-ui-extensions/apis/cart-instructions#examples) for more information.
* > Caution: Check instructions before calling select APIs, as some
* > may not be available. See the [update guide](/docs/api/checkout-ui-extensions/apis/cart-instructions#examples)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This URL currently redirects to /docs/api/checkout-ui-extensions/latest/target-apis/checkout-apis/cart-instructions-api. Should we explicitly state to refer to the Cart Instructions API? Check instructions felt a bit vague to me.

*
* > Tip:
* > Cart metafields are only available on carts created via the Storefront API version `2023-04` or later.
* > Cart metafields are only available on carts created via the Storefront API.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* > Cart metafields are only available on carts created via the Storefront API.
* > Cart metafields are only available on carts created using the Storefront API.

*
* Data is shared across all activated extension targets of this extension. In versions 2023-07 and earlier,
* each activated extension target had its own storage.
* Data is shared across all activated extension targets of this extension.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Data is shared across all activated extension targets of this extension.
* Data is shared across all activated targets associated with this extension.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not quite sure what an activated target is?

*
* > Caution:
* > As of version `2024-04` this value will no longer have a trailing slash.
* The primary storefront URL. The URL does not include a trailing slash.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* The primary storefront URL. The URL does not include a trailing slash.
* The primary storefront URL. The URL doesn't include a trailing slash.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we give an example?

- market: use relative link, clarify ambiguous "It" pronoun
- instructions: reference "cart instructions" explicitly, link to Cart Instructions API
- metafields: "created via" → "created using"
- storage: "activated targets associated with" per reviewer suggestion
- storefrontUrl: "does not" → "doesn't", add @example

Made-with: Cursor
@sordaz00 sordaz00 merged commit 7793e32 into 2025-07 Apr 30, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants