Repository navigation
ci: use Lage to schedule publish tasks - #4022
Merged
Merged
Conversation
|
Saad Najmi (Saadnajmi)
force-pushed
the
lage-runner
branch
from
February 26, 2026 20:17
8e99ac6 to
a62e5f7
Compare
Danny van Velzen (dannyvv)
approved these changes
Feb 27, 2026
Saad Najmi (Saadnajmi)
force-pushed
the
lage-runner
branch
from
February 27, 2026 21:22
c713090 to
5f73331
Compare
Jason Morse (JasonVMo)
approved these changes
Feb 27, 2026
Saad Najmi (Saadnajmi)
force-pushed
the
lage-runner
branch
from
February 28, 2026 08:46
7ac53be to
7aa1e56
Compare
Saad Najmi (Saadnajmi)
enabled auto-merge (squash)
February 28, 2026 08:49
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
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.
Platforms Impacted
Description of changes
Lage has the ability to create workers to run tasks and run then in topological order. In my tests, this was ~3x faster than
yarn workspaces foreach(10-12s vs 29s). Furthermore, lage won't exit on the first failure in a topological layer, while yarn will. This makes lage a bit more robust.While here, a couple of more fixes:
Update Yarn to 4.12 because we can
Update the changeset validation to not fail when you make a change to a dev only dependency.
Verification
Manual testing with
dry-run. Also updated our PR checks.Pull request checklist
This PR has considered (when applicable):