chore: bump to 0.5.0 for the rail 19 release - #168
Merged
Conversation
Minor: rail 19 (#167) is a new un-overridable hard rail, adds a screen criterion, and adds a load-time failure for a non-uppercase allowlist entry. It also tightens --products at the CLI on every command that writes or trades. uv.lock is relocked in the SAME commit this time. Leaving it behind is what made the 0.4.0 release fail its self-identification check: CI's `uv sync` rewrote a tracked file, so the artifact reported (DIRTY). The live deployment is on 0.4.0, which has rail 18 but not rail 19; cutting this release is what gets it there. 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 bump only — no code change. The release workflow refuses to set the version itself, so this is the reviewed PR that decision belongs in (
docs/RELEASING.md).Why minor: rail 19 (#167) is a new un-overridable hard rail, adds a
spot_instrumentscreen criterion, adds a load-time failure for a non-uppercase allowlist entry, and tightens--productsat the CLI on every command that writes or trades.Why now:
~/keelruns 0.4.0, which has rail 18 but not rail 19. TheBTC-PERP-USDresidual — an id that passes rails 1 and 18 and is stopped only by rail 19 — is still open on the live path until this ships.uv.lockis relocked in the same commit. Leaving it behind is exactly what failed the 0.4.0 release: CI'suv syncrewrote a tracked file, so the artifact self-reported(DIRTY).Verified by replaying the full CI sequence on a clean clone — sync (tree stays clean) → stamp →
uv build --all-packages→ install the wheel by path:No
(DIRTY). 1888 tests pass, ruff clean.After merge: Actions → Release → Run workflow with
0.5.0.🤖 Generated with Claude Code