fix(ci): bound jobs and bypass hanging browser installation - #82
Merged
Merged
Conversation
✅ Deploy Preview for limitless-angular-sanity-example canceled.
|
Angular canary compatibility warningThe advisory Angular canary compatibility check failed. This does not block the PR because canary targets are outside the currently required support matrix. Supported peer range:
Stable Angular compatibility rows remain required and will still fail CI if the declared peer range is broken. |
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.
PR Checklist
Release validation in run 29212494292 ran for 5h 54m before manual cancellation. The jobs had no explicit timeout and grouped Turbo logs hid the stalled subprocess. Locally, Playwright 1.44.1 on Node 24.17.0 hangs extracting Chromium after download, consistent with the upstream extraction issue. The original run's buffered logs prevent definitive attribution.
What is the new behavior?
Does this PR introduce a breaking change?
Other information
Testing
Passed locally:
pnpm turbo run test --filter=@limitless-angular/release-tools --filter=@limitless-angular/angular-compatpnpm testpnpm --filter @limitless-angular/sanity testpnpm --dir tools/angular-compat exec node cli.mjs release-paritypnpm exec prettier --check .github/workflows/release-and-publish.yml .github/workflows/release-dry-run.yml tools/release/src/pipeline.mjs tools/release/src/pipeline.test.mjs tools/angular-compat/orchestration-contract.test.mjsgit diff --checkA bounded local release dry run passed packing and artifact validation, reproduced the browser extraction hang, and was terminated. The updated Linux container workflow still needs verification on GitHub; a complete release dry run has not passed locally.
Operational impact: slow jobs now fail at their configured limit rather than consuming hours of runner time. Limits apply per job, including each matrix job. No secrets or application migrations are required. Roll back by reverting this commit. No UI changes.
[Optional] What gif best describes this PR or how it makes you feel?
N/A