chore: bump to 0.4.0 for the rail 18 release - #165
Merged
Conversation
Minor rather than patch: rail 18 is a new un-overridable hard rail, it adds a `settlement_currencies` config field, and it introduces a load-time failure for a config whose `quote_currency` sits outside that set. It also changes admitted behaviour -- non-USD/USDC spot pairs are now vetoed. The live deployment (~/keel) is still on 0.3.2, so the rail is not yet protecting the live path; cutting this release is what gets it there. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
eaitbrahim
added a commit
that referenced
this pull request
Aug 5, 2026
The 0.4.0 release failed at "Verify the artifact identifies itself":
keel 0.4.0+eae6c0437fdd (DIRTY) [release]
::error::artifact reports a dirty tree
The version bump (#165) moved all five workspace members to 0.4.0 but left
uv.lock pinning 0.3.2. CI's `uv sync` step then relocks to match, which
modifies a TRACKED file, so by the time the verify step runs
`keel --version` inside the checkout the tree is dirty.
That is the anti-stale-stamp guard in version.build_info doing its job: a
stamp is only believed when git agrees with it, precisely so a stamped build
of a modified tree cannot claim to be a clean release. The stamp was honest;
the tree really was dirty.
`keel/_build_info.py` and `dist/` are both gitignored, so neither the stamp
nor the build output is what tripped it -- only the lock was.
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 deliberately refuses to set the version itself, so this is the reviewed PR that decision belongs in (
docs/RELEASING.md).Why minor, not patch: rail 18 (#164) is a new un-overridable hard rail, adds a
settlement_currenciesconfig field, introduces a load-timeConfigErrorfor a config whosequote_currencyfalls outside that set, and changes admitted behaviour — non-USD/USDC spot pairs are now vetoed.Why it matters now:
~/keelis still running 0.3.2. I verified directly against the deployment's venv:So the futures/equity hole rail 18 closes is still open on the live path. Cutting 0.4.0 is what actually gets the rail there.
After merge: Actions → Release → Run workflow with
0.4.0, then install the wheels by path into~/keel/.venvandkeel migrate. No schema change in this release, and the three deployment configs need no edits — all setquote_currency: USDand pick up the new field's default.🤖 Generated with Claude Code