fix(ci): TRAC-881 Scope Linear release sync to core/** changes#3086
Conversation
The "Sync Linear release" step scanned every commit on canary and integrations/makeswift, including changes to packages/client, packages/create-catalyst, and the CLI. Those ship as their own independent releases, so their issues don't belong in the "Catalyst Release" pipeline. Add include_paths so only commits touching core/** count toward this pipeline's release tracking. Refs TRAC-881 Co-Authored-By: Claude <noreply@anthropic.com>
|
|
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
|
chanceaclark
deleted the
chancellorclark/ltrac-913-linear-release-include-paths
branch
2 participants
Jira: TRAC-881
What/Why?
Fast-follow to #3085. The "Sync Linear release" step scanned every commit on
canary/integrations/makeswiftwith no path filter, so changes topackages/client,packages/create-catalyst, and the CLI were getting swept into the "Catalyst Release" Linear pipeline. Those ship as their own independent releases and shouldn't count toward this one.Adds
include_paths: core/**to thesynccall so only commits touching the storefront package are scanned.include_pathsisn't needed on thecompletecall since that targets a specific version directly rather than scanning commits.Testing
No automated tests for this workflow. Will confirm via the next real push to canary/integrations-makeswift that
synconly picks upcore/**commits.