chore(repo): Discord (support → community), X, and support email updates#8650
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
🦋 Changeset detectedLatest commit: 41aaa26 The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
This was referenced May 26, 2026
Merged
This was referenced May 26, 2026
Discord (support → community), X, and support email updates
clerk/clerk-nextjs-quickstart-demo-app#5
Merged
Merged
This was referenced May 26, 2026
Merged
Merged
Merged
… handles Discord support officially ends 2026-06-15; Discord is positioned as a community space only. Also canonicalizes Twitter/X URLs and handles in the same surfaces. Package READMEs (18 packages): - Split monolithic "## Support" section into "## Support" (clerk.com/ contact/support, preserving each package's UTM medium) and "## Community" (Discord). Mirrors the namespace split done in lead-agent. - Normalize Twitter follow badges: shields.io handle Clerk(Dev) -> clerk, intent URL twitter.com -> x.com, screen_name Clerk(Dev) -> clerk. Banners: - Root README and integration/templates/tanstack-react-start README: canonicalize Discord URL (discord.com/invite/... -> clerk.com/discord) and X URL (twitter.com/(clerk|clerkdev) -> x.com/clerk). Label updated from "Twitter" -> "X". Template body (integration/templates/tanstack-react-start): - "Feel free to create a support thread on our Discord..." rewritten to point support requests at clerk.com/contact/support + support@clerk.com. - Community paragraph keeps Discord but switches the URL to clerk.com/ discord; closing line reframed from "find support through our Twitter" to "follow @clerk on X for updates". Pre-pass-surfaced canonicalizations: - packages/upgrade/src/versions/core-2/*.md (9 upgrade guide entries) + packages/upgrade/src/versions/core-3/changes/needs-client-trust-sign-in- status-added.md: clerk.com/support -> clerk.com/contact/support; latter also support@clerk.dev -> support@clerk.com. - packages/backend/CHANGELOG.md: 2 historical entries normalized so users reading old version notes land at the canonical support URL. - packages/vue/src/errors/messages.ts + packages/react/src/errors/messages .ts: runtime "invalidStateError" message URL normalized. - .github/ISSUE_TEMPLATE/BUG_REPORT.yml: support URL normalized. Out of scope (deliberately untouched): - createClerkDevCache / ClerkDevCache / clerkDevelopmentCache code identifiers in packages/shared and packages/nextjs. - Notion workspace URLs (clerkdev.notion.site/..., notion.so/clerkdev/...) in docs/CONTRIBUTING.md, .github/workflows/lock-threads.yml, and packages/ui code comments. - 5 terminal error files (express, fastify, tanstack-react-start, react- router, nuxt) — already use clerk.com/discord with community framing. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
manovotny
force-pushed
the
manovotny/discord-x-sweep
branch
from
45d6aea to
894c746
Compare
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughWalkthroughThis PR updates Clerk's support/contact URLs from /support to /contact/support across documentation and error messages, replaces Twitter follow badges with X follow badges in the root and package READMEs and integration templates, restructures README support/community sections into single-line support-page and Discord statements, and changes a support email address in upgrade docs. A new changeset file was added. Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
@clerk/astro
@clerk/backend
@clerk/chrome-extension
@clerk/clerk-js
@clerk/dev-cli
@clerk/expo
@clerk/expo-passkeys
@clerk/express
@clerk/fastify
@clerk/hono
@clerk/localizations
@clerk/nextjs
@clerk/nuxt
@clerk/react
@clerk/react-router
@clerk/shared
@clerk/tanstack-react-start
@clerk/testing
@clerk/ui
@clerk/upgrade
@clerk/vue
commit: |
manovotny
commented
May 26, 2026
manovotny
commented
May 26, 2026
manovotny
commented
May 26, 2026
Co-authored-by: Michael Novotny <manovotny@gmail.com>
wobsoriano
changed the title
wobsoriano
approved these changes
May 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
Clerk Discord support officially ends 2026-06-15. After that date, Discord is a community space only — all support will then route through
clerk.com/contact/supportorsupport@clerk.com.This PR aligns this repo's copy and links with that change. While in the same files, it also fixes adjacent updates for our X.com handle and support email.
Changes (if needed)
https://clerk.com/discordinstead of direct invitation URL.https://clerk.com/contact/supportorsupport@clerk.com. Also updatingsupport@clerk.dev→support@clerk.com.twitter.com→x.comand@ClerkDev→@clerkon Clerk-owned URLs only. Third-party author handles, OAuth-protocol examples, and quoted-tweet permalinks intentionally untouched.Companion PRs