chore: release v0.12.0 - #1002
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
1 participant
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.
Release 0.11.0 → v0.12.0 (minor).
Files touched
CHANGELOG.md: adds the## [0.12.0] - 2026-09-28section (prepended; older sections are unchanged)No manifest changes: the version comes from the git tag (hatch-vcs,
dynamic = ["version"]), sobump-my-versionhas no file entries to rewrite.Changelog section
investment_ratioproperty to Portfolio (feat: add investment_ratio property to Portfolio #1001)The
/rhiza:releaserun that opened this PR is waiting for it to merge. Once it does, the run tags the merged commitv0.12.0and pushes the tag, which starts release CI. If that run has ended by then, re-running/rhiza:releasedoes the same thing.🤖 Generated with Claude Code