Skip to content

[Customer Account] Document mailto and tel href support (2026-07) - #4677

Open
SteveSill wants to merge 1 commit into
2026-07from
steve/2026-07-mailto-tel-href-docs
Open

[Customer Account] Document mailto and tel href support (2026-07)#4677
SteveSill wants to merge 1 commit into
2026-07from
steve/2026-07-mailto-tel-href-docs

Conversation

@SteveSill

@SteveSill SteveSill commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

What

Clarify that the shared href field supports mailto: and tel: URLs, and regenerate the Customer Account reference data inherited by Link, Button, and Clickable.

Validation

  • yarn docs:customer-account 2026-07
  • Generated diff changes exactly eight inherited href descriptions
  • Prettier passes for both changed files

Related

Assisted-By: devx/07b6457f-9d42-46da-8bc6-b446a5debe38
@github-actions

github-actions Bot commented Sep 3, 2026

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.

@github-actions github-actions Bot added the needs-rc-port PR against a stable branch awaiting forward-port to the current RC label Sep 3, 2026
@github-actions

github-actions Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

This PR targets a stable release branch (2026-07). Once merged, the change typically also needs to be forward-ported to 2026-10-rc so it ships in the next release.

When you open the forward-port PR, include a line like this in its body so the needs-rc-port label gets removed automatically when that PR merges:

Forward-port of #4677

Accepted formats (comma-separated for multiple):

  • #4677
  • GH-4677
  • 4677
  • https://github.com/Shopify/ui-extensions/pull/4677

If a forward-port isn't needed (e.g., the change is stable-only), you can remove the needs-rc-port label manually.

@mcvinci mcvinci left a comment

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.

🌴

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-rc-port PR against a stable branch awaiting forward-port to the current RC

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants