Repository navigation
Add a read-only release plan - #86
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 46 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
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.
Tagging the bundled packages showed that
release generateonly looks at open milestones, so it misses the cases that need a maintainer's decision. I had to find them by hand:generatewould have put the notes on the old tag (block-command)wp maintenance release planmakes that check repeatable. For each repository it compares the default branch against the latest version tag and looks at the pull requests merged since. It reportsup_to_date,ready(everything sits on one open milestone thatgeneratecan release), orneeds_humanwith the blockers that explain why. The output is JSON when piped, so an agent can act on it.The plan never picks a version or creates a milestone. Versions are a maintainer's decision, so anything that needs one is reported as a blocker rather than resolved. Routine Dependabot and GitHub Actions pull requests only count when a maintainer has put them on a milestone; otherwise every repository would always look unreleased.
The unit tests are built from the cases above.
The bundle currently comes out
up_to_datethroughout. Across the org, the plan also finds six packages outside the bundle whose milestones are ready (doctor, find, profile, scaffold-package, restful and google-sitemap-generator).