docs: TRAC-1290 add integrations/b2b-makeswift stage to /release-catalyst - #3133
Conversation
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Bundle Size ReportComparing against baseline from No bundle size changes detected. |
Unlighthouse Performance Comparison — VercelComparing PR preview deployment Unlighthouse scores vs production Unlighthouse scores. Summary ScoreAggregate score across all categories as reported by Unlighthouse.
Category Scores
Core Web Vitals
|
The release-catalyst skill released catalyst-core and catalyst-makeswift but had no stage for catalyst-b2b-makeswift, so nothing moved its @latest tag (which the CLI upgrade.ts resolves). Add a b2b sync-and-release stage mirroring the makeswift one (sourced from integrations/makeswift), and extend the @latest tag-push and cleanup stages to cover the b2b package. Note the large-catch-up cadence: one b2b release per makeswift minor tag. Refs TRAC-1290 Co-Authored-By: Claude <noreply@anthropic.com>
6dfca9d to
fb01f3c
Compare
2 participants
Jira: TRAC-1290
What/Why?
Deferred piece of the b2b release wiring (LTRAC-1296).
/release-catalystreleased@bigcommerce/catalyst-coreand@bigcommerce/catalyst-makeswiftbut had no stage for@bigcommerce/catalyst-b2b-makeswift, so nothing moved its@latesttag. That tag matters, the CLI'supgrade.tsresolves@bigcommerce/catalyst-b2b-makeswift@latest, so without moving itcatalyst upgradestays pinned forever.Adds a Stage 3 (sync + release
integrations/b2b-makeswift, mirroring the makeswift stage but sourced fromintegrations/makeswift), renumbers the tag-push (now Stage 4) and cleanup (Stage 5), and extends both to cover the b2b package.Needed now rather than post-upgrade because the b2b upgrade climb (LTRAC-1297) cuts a release per rung, so the b2b release path has to exist first. The stage also notes the large-catch-up cadence: one b2b release per makeswift minor tag.
Rollout/Rollback
Local tooling only (
.claude/skills/), no runtime/app impact. Rollback = revert the commit.Testing
Skill markdown only. Verified the stage sequence reads 1 (canary) → 2 (makeswift) → 3 (b2b) → 4 (@latest tags) → 5 (cleanup). No code paths exercised; the stage will get its real exercise on the first b2b upgrade rung.