From 30da1f18cb99dc90e0432873a949a8195b96fc26 Mon Sep 17 00:00:00 2001 From: Chancellor Clark Date: Wed, 22 Jul 2026 11:58:52 -0600 Subject: [PATCH] ci: TRAC-1235 make changesets release aware of integrations/b2b-makeswift 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 --- .github/workflows/changesets-release.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/.github/workflows/changesets-release.yml b/.github/workflows/changesets-release.yml index 37121218b..00e6ca320 100644 --- a/.github/workflows/changesets-release.yml +++ b/.github/workflows/changesets-release.yml @@ -5,6 +5,7 @@ on: branches: - canary - integrations/makeswift + - integrations/b2b-makeswift concurrency: ${{ github.workflow }}-${{ github.ref }} @@ -72,6 +73,8 @@ jobs: PACKAGE_NAME="@bigcommerce/catalyst-core" if [ "${{ github.ref_name }}" = "integrations/makeswift" ]; then PACKAGE_NAME="@bigcommerce/catalyst-makeswift" + elif [ "${{ github.ref_name }}" = "integrations/b2b-makeswift" ]; then + PACKAGE_NAME="@bigcommerce/catalyst-b2b-makeswift" fi VERSION=$(echo '${{ steps.changesets.outputs.publishedPackages }}' | jq -r --arg name "$PACKAGE_NAME" '.[] | select(.name == $name) | .version') if [ -z "$VERSION" ]; then