-
Notifications
You must be signed in to change notification settings - Fork 524
Update plan tier hierarchy for sponsorship policies #6853
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update plan tier hierarchy for sponsorship policies #6853
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
size-limit report 📦
|
TL;DR
Updated plan tier hierarchy by swapping
starter
andstarter_legacy
positions, and lowered the required plan for sponsorship policies fromaccelerate
tostarter
.What changed?
planToTierRecordForGating
by changing:starter_legacy
from tier 1 to tier 2starter
from tier 2 to tier 1accelerate
tostarter
in theGatedSwitch
componentHow to test?
starter
plan can now access sponsorship policiesstarter_legacy
plans maintain their expected access levelsWhy make this change?
This change makes sponsorship policies available to more users by lowering the tier requirement. The plan hierarchy adjustment ensures that the
starter
plan is positioned correctly in the tier structure, making it more accessible than the legacy version while maintaining the proper feature gating across the platform.