Skip to content

Chunk releases using topological sorting - #2100

Merged
Andarist merged 7 commits into
mainfrom
topological-sort
Jun 19, 2026
Merged

Chunk releases using topological sorting#2100
Andarist merged 7 commits into
mainfrom
topological-sort

Conversation

@Andarist

@Andarist Andarist commented Jun 18, 2026

Copy link
Copy Markdown
Member

fixes #238

@Andarist
Andarist requested a review from bluwy June 18, 2026 22:30
@changeset-bot

changeset-bot Bot commented Jun 18, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 3160332

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@changesets/cli Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@codecov

codecov Bot commented Jun 18, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 98.18182% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 82.98%. Comparing base (830443c) to head (3160332).

Files with missing lines Patch % Lines
...es/cli/src/commands/publish-plan/getPublishPlan.ts 95.45% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2100      +/-   ##
==========================================
+ Coverage   81.64%   82.98%   +1.34%     
==========================================
  Files          66       66              
  Lines        2479     2504      +25     
  Branches      673      679       +6     
==========================================
+ Hits         2024     2078      +54     
+ Misses        409      383      -26     
+ Partials       46       43       -3     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@bluwy

bluwy commented Jun 19, 2026

Copy link
Copy Markdown
Member

Should or can this be done in assemble-release-plan as mentioned in #238?

Also, should we allow publishing still with cycles? We can warn instead. We currently already publish non-topologically, and that has worked out fine for a long while, so publishing with a best-effort order is still fine I think.

@Andarist

Copy link
Copy Markdown
Member Author

Should or can this be done in assemble-release-plan as mentioned in #238?

See #238 (comment)

We could also sort in assemble-release-plan but that wouldn't really help with publishes interrupted in the middle etc. assemble-release-plan participates in changeset version and not changeset publish

Also, should we allow publishing still with cycles? We can warn instead. We currently already publish non-topologically, and that has worked out fine for a long while, so publishing with a best-effort order is still fine I think.

I also considered adding an option to allow/disallow cycles - but I intentionally have started with the least permissive behavior here to hear out your thoughts on this.

I think warnings would be OK for now.

@Andarist

Copy link
Copy Markdown
Member Author

I made it to warn now

@Andarist
Andarist added this pull request to the merge queue Jun 19, 2026
Merged via the queue into main with commit 90b4ad0 Jun 19, 2026
12 checks passed
@Andarist
Andarist deleted the topological-sort branch June 19, 2026 18:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Packages should be published in topological order

2 participants