From 5b5d7b4e4f25f67daba1efa418b4a28bffabdf02 Mon Sep 17 00:00:00 2001 From: Kim Gustyr Date: Fri, 24 Apr 2026 15:44:50 +0100 Subject: [PATCH] test(Billing): Post-deploy E2E does not include plans MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Vercel's flagsmith-frontend-staging project bundles with ENV=dev and already ships the full plan catalogue, while the staging E2E bundle (e.g. the post-API-deploy run in .reusable-deploy-ecs.yml) is built with ENV=staging and was missing the plans field — trial buttons were gated on chargebeePlanId so they silently didn't render. Copy the plan IDs from project_dev.js into project_staging.js so both staging bundles are configured identically. project_prod.js already has its own plans block (prod Chargebee tenant uses different plan IDs) and doesn't need changes. beep boop --- frontend/env/project_staging.js | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/frontend/env/project_staging.js b/frontend/env/project_staging.js index 611eb27345f8..d69548f70853 100644 --- a/frontend/env/project_staging.js +++ b/frontend/env/project_staging.js @@ -16,6 +16,10 @@ const Project = { flagsmithClientEdgeAPI: 'https://edge.bullet-train-staging.win/api/v1/', // This is used for Sentry tracking maintenance: false, + plans: { + scaleUp: { annual: 'Scale-Up-v4-USD-Yearly', monthly: 'Scale-Up-v4-USD-Monthly' }, + startup: { annual: 'startup-annual-v2', monthly: 'startup-v2' }, + }, useSecureCookies: true, ...(_globalThis.projectOverrides || {}), }