Repository navigation
ci: skip re-testing on the release PR and parallelize the slowest jobs - #1474
Merged
Merged
Conversation
The Version Packages PR changes only versions, changelogs and spent changesets. main takes only up-to-date, green PRs, so its tree is what the last merged PR already tested. Skip the test, browser, compiler, Chromatic, size and CodeQL jobs there. A job skipped by its `if` reports success, so the required `Tests & lint` check still passes, and a new job marks the commit as passing in Chromatic (`skip: true`) so `UI Tests` and `UI Review` report without a build. That build re-snapshotted all ~1100 stories with TurboSnap disabled. `Build & canary release` still builds the tree about to ship. Updates of that PR never ran CI at all: changesets pushed them with the `GITHUB_TOKEN` that actions/checkout persists, which takes precedence over the PAT, so each run waited at `action_required`. Check out without persisted credentials so the push uses the PAT. On regular PRs, browser tests run each compiler mode as its own matrix job instead of two serial ~4.5-minute steps, and the compiled full suite runs beside the Form and package checks instead of among them. CodeQL cancels the analysis of a superseded PR push. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
📦 NPM canary releaseDeployed canary version 0.0.0-canary-0486611. |
Contributor
🧪 Storybook is successfully deployed!
|
Contributor
🏋️ Size limit report
Compared against main at 225b7e4 — run 37469139459, 2026-10-06T13:13:40Z.To see which modules changed, download the size-limit-statoscope-report artifact from this run and open report.html. |
tenphi
force-pushed
the
andrew/ci-release-pr-and-parallel-tests
branch
from
October 6, 2026 13:04
872109a to
6d361ba
Compare
This branch was successfully deployed
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
1 participant
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.
Describe changes
Version Packages PR (
changeset-release/main)UIKIT_GITHUB_TOKEN, so the run on the opening commit works. Every later update is agit pushthat authenticates with theGITHUB_TOKENactions/checkoutpersists, which beats the PAT changesets writes to~/.netrc. Those runs are created asgithub-actions[bot], wait ataction_required, and are marked failed on merge (Version Packages #1469, Version Packages #1473).publish-releasenow checks out withpersist-credentials: false, so the push uses the PAT. The PAT already creates the GitHub releases, so it hascontents: write.maintakes only up-to-date green PRs. Tests & lint, the React Compiler jobs, browser tests, Chromatic, size-limit and CodeQL now skip it.ifreports success, so the requiredTests & lintcheck still passes.skip-chromaticjob runschromaui/actionwithskip: true, which marks the commit as passing, so the requiredUI Tests/UI Reviewstatuses report without a build. Its real builds ran with TurboSnap disabled and snapshotted all 1085 stories.Build & canary releasestill builds the tree about to ship (it already skipped the canary publish).Regular PRs (same coverage, shorter critical path; ~590s today, from "Browser tests / React 18")
test:compiled(~330s) moves into its own job on the same React matrix, beside the Form and package checks instead of among them.Expected critical path afterwards:
Tests & lint, ~430s. Required check names are unchanged. The renamed jobs (React Compiler, Browser tests) are not required checks.Checklist
No changeset: CI only.
Closes: N/A
Other information
Measured on this PR
Tests & lint(420s),React Compiler / React 18 / All components(350s) and the slowest browser job (326s).UI TestsandUI Reviewreported success ("Skipped build."), the test jobs reported skipped,Build & canary releasepassed in 77s, and the PR's merge state wasCLEAN, so all four required checks were satisfied.persist-credentials: falseonly takes effect on the first release-PR update after this merges.🤖 Generated with Claude Code