Skip to content

docs(v1): use posthog instead of segment - #13955

Merged
shahednasser merged 3 commits into
v1.xfrom
docs/add-posthog-v1
Nov 4, 2025
Merged

docs(v1): use posthog instead of segment#13955
shahednasser merged 3 commits into
v1.xfrom
docs/add-posthog-v1

Conversation

@shahednasser

Copy link
Copy Markdown
Member
  • Use posthog in v1 docs
  • Remove segment usage from v1 docs
  • Add note to deployment guides

Closes DX-2274

@shahednasser
shahednasser requested a review from a team as a code owner November 4, 2025 12:19
@changeset-bot

changeset-bot Bot commented Nov 4, 2025

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 2014209

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@vercel

vercel Bot commented Nov 4, 2025

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
api-reference Building Building Preview Comment Nov 4, 2025 0:36am
api-reference-v2 Error Error Nov 4, 2025 0:36am
cloud-docs Error Error Nov 4, 2025 0:36am
docs-ui Error Error Nov 4, 2025 0:36am
docs-v2 Error Error Nov 4, 2025 0:36am
medusa-docs Error Error Nov 4, 2025 0:36am
resources-docs Error Error Nov 4, 2025 0:36am
user-guide Error Error Nov 4, 2025 0:36am

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.

1 participant