feat(billing): notify alpha plan users about june 4 migration#2028
Merged
feat(billing): notify alpha plan users about june 4 migration#2028
Conversation
Updates the Plan and Usage settings to make the alpha → free plan transition explicit: - Expands the alpha-plan banner to spell out that seats will be moved to the free plan on June 4, 2026 and points users at upgrading to Pro if they want to keep their current usage levels. - Hides the Upgrade button on the Pro plan card while on the alpha plan; the alpha plan already grants full Pro access, so showing Upgrade was misleading and let alpha users charge themselves $200/mo for no incremental value. Generated-By: PostHog Code Task-Id: 7ad4d917-387c-493f-8dd1-c8b8df698434
pawel-cebula
approved these changes
May 5, 2026
Contributor
pawel-cebula
left a comment
There was a problem hiding this comment.
Looks good from my side but didn't test locally (need to set up code for local dev first) so will let you ✅ and merge @k11kirky / @charlesvien
Contributor
Prompt To Fix All With AIFix the following 1 code review issue. Work through them one at a time, proposing concise fixes.
---
### Issue 1 of 1
apps/code/src/renderer/features/settings/components/sections/PlanUsageSettings.tsx:278-282
**Banner mentions upgrading but provides no path to do so**
The banner tells alpha users they'll "be able to upgrade to the Pro plan" after migration, but the Upgrade button on the Pro card is now hidden for alpha users and there is no link or CTA in the banner itself. A user who reads this and wants to act early has no obvious way to reach the billing or upgrade flow from this screen. Consider adding an `onClick={() => void openBillingPage(billingOrgId)}` link inline in the banner text, or re-showing the Upgrade button (with a tooltip explaining that the upgrade will take effect after June 4) so the copy and the UI are consistent.
Reviews (1): Last reviewed commit: "fix(billing): clarify alpha seat expiry ..." | Re-trigger Greptile |
k11kirky
approved these changes
May 5, 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
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
Updates the Plan and Usage settings so the alpha → free migration on June 4, 2026 is explicit, and stops showing the Pro Upgrade button to alpha users (alpha already grants full Pro access).
Changes
PlanUsageSettings.tsxnow spells out that alpha seats will be moved to the free plan on June 4, 2026 and points users at upgrading to Pro if they want to keep current usage levels.isAlphais true — no Upgrade button (was shown via theelsebranch when!(isOrgPro && !isAlpha)), no Cancel/Reactivate (alpha will auto-migrate).Companion change in posthog dashboard: PostHog/posthog#57629.
Test plan
pnpm --filter code typecheck(passes)pnpm exec biome check apps/code/src/renderer/features/settings/components/sections/PlanUsageSettings.tsx(passes)posthog-code-pro-0-20260422Agent context
7ad4d917-387c-493f-8dd1-c8b8df698434)isAlphaflag at line 79 instead of pushing it intouseSeat— only one caller needs it.Created with PostHog Code