ci: TRAC-1235 wire integrations/b2b-makeswift into its own changesets release#3125
Open
chanceaclark wants to merge 1 commit into
Open
Conversation
… release integrations/b2b-makeswift published core/package.json as @bigcommerce/catalyst-makeswift, colliding with the integrations/makeswift package, and ran a stale single-step (NPM_TOKEN) release workflow that never triggered on its own branch. Give the branch a distinct release identity that mirrors integrations/makeswift: - Rename core/package.json to @bigcommerce/catalyst-b2b-makeswift, matching the existing @bigcommerce/catalyst-b2b-makeswift@latest git tag. - Point .changeset/config.json baseBranch at integrations/b2b-makeswift and ignore @bigcommerce/catalyst + @bigcommerce/create-catalyst. - Replace changesets-release.yml with canary's current pipeline (Linear sync, changeset:version, headline resolution), trigger it on integrations/b2b-makeswift, and map that branch to @bigcommerce/catalyst-b2b-makeswift. - Retarget the prevent-invalid-changesets guard to integrations/b2b-makeswift and @bigcommerce/catalyst-b2b-makeswift. - Add the changeset:version script and sync-catalyst-version.mts so core's catalyst field (version + ref) stays synced on release. - Update CONTRIBUTING.md package-identity rules to the b2b-makeswift name. Refs TRAC-1235 Co-Authored-By: Claude <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
chanceaclark
marked this pull request as ready for review
July 22, 2026 19:17
parthshahp
approved these changes
Jul 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Jira: TRAC-1235
What/Why?
integrations/b2b-makeswifthad no release identity of its own. Itscore/package.jsonwas named@bigcommerce/catalyst-makeswift(the same npm package asintegrations/makeswift, so any publish would clobber the real Makeswift package), and itschangesets-release.ymlwas a stale single-step (NPM_TOKEN) workflow that only triggered oncanary/integrations/makeswift, never on this branch.This gives the branch a distinct identity and mirrors the current
integrations/makeswiftrelease setup:core/package.jsonto@bigcommerce/catalyst-b2b-makeswift(matches the existing@bigcommerce/catalyst-b2b-makeswift@latestgit tag and the CLIupgradecommand's package map).baseBranchatintegrations/b2b-makeswiftand ignores@bigcommerce/catalyst+@bigcommerce/create-catalyst.changeset:version, headline-package resolution), now triggering onintegrations/b2b-makeswiftwith a headline case mapping the branch to@bigcommerce/catalyst-b2b-makeswift.prevent-invalid-changesets) fires on PRs intointegrations/b2b-makeswiftand only allows@bigcommerce/catalyst-b2b-makeswift.changeset:version+sync-catalyst-version.mtskeepcore'scatalystfield (version + git ref) synced on each bump.Part of LTRAC-1095 (consolidate B2B branches). Follow-up LTRAC-1297 revives the makeswift >=1.9.0 upgrade on top of this.
Intentionally not included: the
release-catalystskill's b2b tag-push stage and a/sync-b2b-makeswiftskill. Those are.claude/skillstooling that should land oncanary, not on this branch.Testing
node .github/scripts/sync-catalyst-version.mts: producesref: @bigcommerce/catalyst-b2b-makeswift@1.1.3(then restored, so the commit is name-only).pnpm-lock.yamlhas zero references to the old package name and no workspace package depends oncoreby name, so no lockfile regen is needed.Version Packages (integrations/b2b-makeswift)PR resolving@bigcommerce/catalyst-b2b-makeswift, andprevent-invalid-changesetsshould reject any non-b2b package.Migration
Consumers pinned to this branch's package should note the npm name changes from
@bigcommerce/catalyst-makeswiftto@bigcommerce/catalyst-b2b-makeswift.Do not squash or rebase-and-merge this PR into
integrations/b2b-makeswift; use a merge commit (or a local fast-forward) to preserve the merge base withintegrations/makeswiftfor future syncs.