fix(ci): serialize tsc-multi builds in GitHub workflows#1076
Merged
Conversation
|
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.
This pull request fixes an intermittent CI build failure caused by
tsc-multirunning parallel target builds that can race on shared.d.tsoutputs. The failure surfaced in the coverage job as a transient TypeScriptTS7006error inpackages/agents-extensions/src/ai-sdk-ui/uiMessageStream.ts, even though the underlying source code was unchanged and reruns passed.The change adds a dedicated
build:ciscript inpackage.jsonthat preserves the normalprebuildandpostbuildlifecycle while forcingtsc-multi --maxWorkers 1on GitHub runners. It then updates the relevant workflows in.github/workflows/test.yml,.github/workflows/docs.yml,.github/workflows/release.yml, and.github/workflows/update-docs.ymlto use that serialized CI build path instead of the default parallel build.Behaviorally, local developer builds remain unchanged and fast because
pnpm buildstill uses the existing parallel configuration. Only CI builds are serialized to reduce flakiness and keep declaration generation stable across targets.