Repository navigation
docs(changelog): roll Unreleased into 1.25.0 and 1.26.0 - #1134
Conversation
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
v1.25.0 was tagged without a roll, so Unreleased held its nine entries plus everything merged since. Entries present in v1.25.0's CHANGELOG go under 1.25.0; the rest go under 1.26.0. No entry text changed. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
0a6bd2f to
c94c1fe
Compare
Swarmhost agentic reviewThe detailed evaluation is available to employees in the internal Slack review thread. Evaluation budget remaining for this pull request: 14 automatic and 15 manual. Updated by Swarmhost's agentic review process. |
comfy-greenlight-bot
left a comment
There was a problem hiding this comment.
This pull request at head commit c94c1fe has been reviewed and approved by Swarmhost's agentic review process.
The detailed evaluation is available to employees in the internal Slack review thread.
Step 1 of the release in CONTRIBUTING.md ("Cutting a release"): roll the changelog before creating the GitHub release.
v1.25.0 was tagged on 2026-11-02 without a changelog roll, so
## [Unreleased]held both its entries and everything merged since. This splits it:v1.25.0tag.## [Unreleased]is left empty, with the compare links updated.No entry text changed; a word-for-word comparison against the old file shows only the new headers and links added.
Please check before merging:
**Breaking:**ones. Change it if you want something else.mainand will be one low once this PR merges.After merge: publish release
v1.26.0frommain(not a draft) and confirmtest-pip-installationpasses.🤖 Generated with Claude Code
Summary by CodeRabbit