chore(release): bump version to 0.3.2 - #160
Merged
Merged
Conversation
Bumps all five workspace packages (keel-trader, keel-core, keel-broker-{api,coinbase,fake})
and uv.lock from 0.3.1 to 0.3.2 ahead of the v0.3.2 release. Version-only change; the release
workflow refuses to run unless pyproject.toml already carries the version being released.
Since v0.3.1: rule-rejection diagnostics on engine.no_signal (#158), the TUI refresh toast
(#159), and the deploy-a-release README section + operator-wrapper gitignore (#157).
Co-Authored-By: Claude Opus 5 (1M context) <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.
Version-only change ahead of the v0.3.2 release. Bumps all five workspace packages
(
keel-trader,keel-core,keel-broker-{api,coinbase,fake}) anduv.lockfrom 0.3.1 to 0.3.2.The release workflow refuses to run unless
pyproject.tomlalready carries the version beingreleased — the bump is a human decision and belongs in a reviewed PR, so CI never writes to
main.A patch release: one enhancement, one fix, one docs change. No schema change, no rail change, and
nothing that alters what the agent will or won't trade.
engine.no_signalnow carriesproduct,gateand the near-miss numbers(
close/entry_level/gap_pct), so a cycle reportingsignals=0explains itself insteadof needing the rules replayed against the database by hand.
rin the TUI toasts instead of looking like a dead key.🤖 Generated with Claude Code