ci: TRAC-881 Hook up Linear releases via linear-release-action#3085
Merged
chanceaclark merged 1 commit intoJul 7, 2026
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Bundle Size ReportComparing against baseline from No bundle size changes detected. |
chanceaclark
force-pushed
the
chancellorclark/ltrac-913-hook-up-linear-releases-for-catalyst
branch
from
July 7, 2026 20:36
c9418a8 to
64101de
Compare
|
chanceaclark
force-pushed
the
chancellorclark/ltrac-913-hook-up-linear-releases-for-catalyst
branch
from
July 7, 2026 20:54
64101de to
d8fe268
Compare
chanceaclark
marked this pull request as ready for review
July 7, 2026 20:55
jorgemoya
approved these changes
Jul 7, 2026
Contributor
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
|
chanceaclark
force-pushed
the
chancellorclark/ltrac-913-hook-up-linear-releases-for-catalyst
branch
from
July 7, 2026 21:49
d8fe268 to
b49e092
Compare
chanceaclark
enabled auto-merge
July 7, 2026 21:50
chanceaclark
disabled auto-merge
July 7, 2026 21:52
Sync every push to canary/integrations-makeswift into Linear's "Catalyst Release" pipeline via linear/linear-release-action, so merged issues get attached to the currently open release as PRs land. Once changesets actually publishes a new @bigcommerce/catalyst-core or @bigcommerce/catalyst-makeswift version, complete that release using the GitHub Release notes changesets already generated for the tag. Refs TRAC-881 Co-Authored-By: Claude <noreply@anthropic.com>
chanceaclark
force-pushed
the
chancellorclark/ltrac-913-hook-up-linear-releases-for-catalyst
branch
from
July 7, 2026 21:54
b49e092 to
7b04f9b
Compare
chanceaclark
deleted the
chancellorclark/ltrac-913-hook-up-linear-releases-for-catalyst
branch
July 7, 2026 22:28
This was referenced Jul 7, 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-881
What/Why?
Wires up linear/linear-release-action in
changesets-release.ymlso the "Catalyst Release" pipeline in Linear (scheduled, stagesPlanned → In Progress → Merged → Released) can answer "when will this ship" questions (LTRAC-913).syncruns on every push tocanary/integrations/makeswift, attaching merged issues to whichever release is currently open in the pipeline — this is how Linear expects scheduled pipelines to be fed continuously as PRs merge.completeonly fires whenchangesets/actionactually publishes the branch's headline package (@bigcommerce/catalyst-coreoncanary,@bigcommerce/catalyst-makeswiftonintegrations/makeswift), resolved from thepublishedPackagesoutput. If a run only bumps a non-headline package (e.g.@bigcommerce/create-catalystor the CLI), it's skipped and those issues stay attached to the still-open release.completeare pulled straight from the GitHub Release body thatchangesets/actionalready generates for the published tag (gh release view), reusing the existing changeset-authored changelog instead of re-parsingCHANGELOG.mdor relying on Linear's own auto-generated notes (currently off on this pipeline).fetch-depth: 0since the Linear CLI needs real commit history to scan.Explicitly out of scope: the manual
@latesttag move (drives demo-site deploys indeploy.yml) stays untouched — a Linear release is considered shipped when changesets publishes a new version, not when@latestmoves.Testing
Can't fully dry-run this without pushing to a protected branch. Plan is to watch the Action logs on the next few real pushes/publishes to
canaryandintegrations/makeswift, confirm theLINEAR_ACCESS_KEYsecret authenticates,headlinestep resolves the right tag, and the release shows up correctly in Linear (https://linear.app/commerce/pipeline/catalyst-release/releases) with attached issues and, after a real publish, the changelog as notes.Migration
N/A — CI workflow only, no application code changes.