Release 25.05.0

[philippotto]

Branched from 3e7e5c3.

(Please delete unneeded items, merge only when none are left open)

• Updated changelog
• Updated migration guide if applicable

[coderabbitai]

📝 Walkthrough

Walkthrough

This update finalizes documentation for the 25.05.0 release. The changelog and migration guide now include new entries for this version, outlining features such as toolkits, workflow enhancements, UI improvements, bug fixes, and changes to annotation update behavior. The unreleased sections in both the changelog and migration guide were reset, with prior content cleared and comparison links updated to use 25.05.0 as the new base. No changes were made to exported or public entities in the codebase.

Changes

Files	Change Summary
CHANGELOG.released.md, MIGRATIONS.released.md	Added new entries for version 25.05.0, summarizing new features, workflow changes, fixes, and migrations.
CHANGELOG.unreleased.md, MIGRATIONS.unreleased.md	Cleared previous unreleased content and updated comparison links to use 25.05.0 as the new base.

Poem

A hop, a skip, release anew,
Toolkits and workflows—so much to do!
Changelogs polished, migrations neat,
Bugs are squashed beneath our feet.
With every leap, the garden grows—
Onward to 25.05.0, the rabbit knows!
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3e7e5c3 and 0233348.

📒 Files selected for processing (4)

• CHANGELOG.released.md (1 hunks)
• CHANGELOG.unreleased.md (1 hunks)
• MIGRATIONS.released.md (1 hunks)
• MIGRATIONS.unreleased.md (1 hunks)

🧰 Additional context used

🪛 markdownlint-cli2 (0.17.2)

MIGRATIONS.released.md

12-12: Trailing punctuation in heading
Punctuation: ':'

(MD026, no-trailing-punctuation)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: build-smoketest-push
• GitHub Check: backend-tests

🔇 Additional comments (4)

MIGRATIONS.unreleased.md (1)

9-9: Update comparison link to new base tag
The link now correctly compares 25.05.0...HEAD, reflecting the new release baseline for unreleased migrations.

MIGRATIONS.released.md (1)

9-10: Add new release entry for 25.05.0
The version header, release date (2025-04-29), and commits link (25.04.0...25.05.0) have been updated to document the 25.05.0 release.

CHANGELOG.unreleased.md (1)

11-11: Reset unreleased changelog comparison link
The comparison link now points to 25.05.0...HEAD, clearing out previous entries and preparing the section for upcoming changes.

CHANGELOG.released.md (1)

10-34: LGTM: Well-documented changelog entry for version 25.05.0

The new release entry follows the established format and provides clear, detailed information about the changes in this version. The entry is properly organized into the standard sections (Highlights, Added, Changed, Fixed, Removed), with each item linked to its corresponding GitHub PR for reference.

The highlights section effectively summarizes the key features like toolkits, workflow enhancements, and changes to annotation update behavior. The descriptions are informative and help users understand what changed and why.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[fm3]

Thanks! I guess there is no good way of testing the new split tool / workflow concepts before including them in a release, is there?

[philippotto]

Thanks! I guess there is no good way of testing the new split tool / workflow concepts before including them in a release, is there?

we had some lab feedback for a dev instance. I guess our best chance to get more feedback is to land the feature in prod.