…wift
Add integrations/b2b-makeswift to the Changesets Release workflow so the branch
can cut its own @bigcommerce/catalyst-b2b-makeswift releases:
- Trigger the workflow on pushes to integrations/b2b-makeswift.
- Map that branch to @bigcommerce/catalyst-b2b-makeswift when resolving the
headline package for the Linear release notes.
Both additions are inert on canary and integrations/makeswift: a push only runs
the workflow copy on the branch that was pushed, and the headline elif never
matches their ref_name. Keeping this on canary makes it the source of truth for
the shared workflow; integrations/makeswift picks it up via /sync-makeswift and
integrations/b2b-makeswift carries the same file.
Refs TRAC-1235
Co-Authored-By: Claude <noreply@anthropic.com>
Jira: TRAC-1235
What/Why?
changesets-release.ymlis shared, ref-driven infrastructure: canary andintegrations/makeswiftcarry a byte-identical copy, and per-branch behavior comes fromgithub.ref_name. To bringintegrations/b2b-makeswiftinto the release process without drift, its awareness has to originate here on canary rather than only on the integration branch.This adds
integrations/b2b-makeswiftto the workflow's push trigger and maps it to@bigcommerce/catalyst-b2b-makeswiftin the headline-package resolver. Both are inert on canary andintegrations/makeswift(a push only runs the workflow copy on the branch that was pushed, and theelifnever matches theirref_name), so this is safe to land on canary immediately.From here the change propagates to
integrations/makeswiftvia/sync-makeswift, andintegrations/b2b-makeswiftcarries the same file (see #3125, which gives that branch its distinct@bigcommerce/catalyst-b2b-makeswiftidentity + changeset guard).Part of LTRAC-1095 (consolidate B2B branches) / LTRAC-1296. The
release-catalystskill's b2b release stage and the new/sync-b2b-makeswiftskill are intentionally deferred to the WS3 upgrade (LTRAC-1297), since a b2b release stage depends on/sync-b2b-makeswiftexisting and on the branch actually being releasable.Testing
No behavior change on canary or
integrations/makeswift. End-to-end validation happens onintegrations/b2b-makeswiftonce #3125 lands: a changeset there should open aVersion Packages (integrations/b2b-makeswift)PR resolving@bigcommerce/catalyst-b2b-makeswift.Migration
None.