Repository navigation
ci: show current and next versions in release PR titles - #374
Conversation
|
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 55 minutes. View limit details
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Summary
Merge Risk: ⚪ Minimal · up to
|
| Check name | Status | Explanation |
|---|---|---|
| Title check |  |
The title clearly and concisely describes the main change: release PR titles now show the current and next versions. |
| Docstring Coverage | |
Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 1 files. (9 skipped: 9 … |
| Linked Issues check | |
Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | |
Check skipped because no linked issues were found for this pull request. |
| Description check | |
The pull request description includes all required sections and provides clear context, changes, verification results, documentation status, changelog details, and reviewer notes. The related issue se… |
Full details: Docstring Coverage
-
Explanation
Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 1 files. (9 skipped: 9 unsupported.)
Full details: Description check
-
Explanation
The pull request description includes all required sections and provides clear context, changes, verification results, documentation status, changelog details, and reviewer notes. The related issue section references the follow-up issue instead of using the exact
Closes #format, but the description is otherwise complete.
✨ Finishing Touches
-
📝 Generate docstrings
-
- Commit to this branch
- Create a new PR
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
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.
A rabbit checks the release line,
Current and next versions align.
The title hops from old to new,
With changelog notes to guide it through.
One tidy carrot marks the queue.
Comment @coderabbitai help to get the list of available commands.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Changelog✅ Contribution check passed. Head: Base: Contribution: 1 new valid fragment(s). Policy: ordinary.
|
|
🚀 Preview is available for this pull request. |
github-project-automation
Bot
moved this from Backlog
to Released
in PHP Fast Forward Project
Related Issue
Follow-up to #372; configures the managed release PR #373 and future release PRs.
Motivation / Context
The generated release PR currently says only
chore: update changelog, hiding the version transition from the PR list.Changes
version-pr-titleinput aschore: release {current_version} → {next_version}in both the repository caller and packaged consumer template.chore: release 1.26.0 → 2.0.0.Verification
actionlintpasses for both callers; fragment validation andgit diff --checkpass.v0release v0.3.0 at 85474de5a16bb08f83c9f30e0ed72f331a210f07.composer dev-tools: 650 tests / 1,964 assertions pass; Rector and PHPDoc pass. The aggregate gate exits 1 on 61 existing style diffs outside this change and the unavailablevendor/bin/phpdocAPI-documentation shim; metrics also reports malformed local JUnit XML warnings. No unrelated files were changed to suppress these diagnostics. New-HEAD remote CI remains pending. Independent contract review found no actionable issue.Documentation / Generated Output
README, AGENTS and release/workflow guides describe the configured title. The caller and packaged template remain identical.
Changelog
Added
.changelog/release-pr-version-range.mdwith patch impact. Existing fragments and central history are preserved.Reviewer Notes
After this change is merged, the next base-branch preparation run should update the managed release PR's title using the validated plan. Its managed branch was not edited manually.
@v0andpublish: trueare retained. No release PR was merged and no tag or Release was published.