chore: bump to 0.5.1 for the venue-unreachable logging fix - #170
Merged
Conversation
Patch: #169 changes log severity only. `cb_client.get_accounts` still raises and `executor._fetch_available_quote` still returns None, so rail 13 fails closed exactly as before -- no behaviour an operator or a rail can observe has changed, only whether a record lands at ERROR with a traceback or at WARNING on one line. uv.lock is relocked in the SAME commit, per 0.5.0. 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). Verified here with `uv sync --frozen`, which accepted the lock and rewrote nothing. The live deployment is on 0.5.0, whose TUI balance poll writes a 20-frame ERROR traceback every 30s whenever the machine is offline; cutting this release is what gets the fix 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 changes. Pairs with #169.
Patch, not minor. #169 changes log severity and nothing else:
cb_client.get_accountsstill raises,executor._fetch_available_quotestill returnsNone, and rail 13 still fails closed on a missing balance. No behaviour an operator or a rail can observe has changed — only whether a record lands at ERROR with a 20-frame traceback or at WARNING on one line.uv.lockis relocked in the same commit, per 0.5.0. Leaving it behind is what made the 0.4.0 release fail its self-identification check: CI'suv syncrewrote a tracked file, so the artifact reported(DIRTY). Verified here withuv sync --frozen, which accepted the lock and rewrote nothing beyond the fivepyproject.tomlbumps.The live deployment is on 0.5.0, whose TUI balance poll writes a full ERROR traceback every 30s for as long as the machine is offline. Cutting this release is what gets the fix there.
🤖 Generated with Claude Code