0.5.0 stabilization & docs polish#27
Merged
Merged
Conversation
…t-in trade lifecycle Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…redentials fixture)
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…, links verified) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…, exit codes) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…s in .env, not env)
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
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.
Post-release verification of v0.5.0 — proves the published artifact, CLI, and SDK are stable, and brings the GitHub-published docs into accurate agreement with the code. Tests + docs only; no production source changed.
Badge question (answered, no repo fix)
PyPI has 0.5.0 and the shields.io endpoints already return
v0.5.0; the README badges are all dynamic. A stale badge image on GitHub is the Camo image-proxy/browser cache, which self-corrects — nothing in the repo was wrong.Stability verified
pip install capitalcom-cli==0.5.0importscapital_cli.sdk+capital_cli.services(the new packages shipped); locally-built wheel contains all four subpackages.make checkgreen (253 passed, 2 skipped).Real defects found & fixed (tests/harness only)
test_16/test_23asserted a pre-NDJSON summary shape; latently broken since the P2 NDJSON change. Now parse NDJSON and assert per-linePriceTick/OHLCBarshape._credentialsfixture mis-pointedCAP_ENV_FILEat a dummy file, so the SDK e2e saw fake creds /CAP_ALLOW_TRADING=false(and only "passed" reads via leaked sessions). Addedtests/e2e/conftest.pyto re-point in-process e2e at the real.env; the SDK trade lifecycle now passes under the same env the CLI suite uses.os.environbutCAP_WS_ENABLEDlives in.env; re-gated on the loaded config so it actually exercises SDK streaming against demo.ConfirmRequiredError(no silent write) through the real risk engine.Docs polished
CAP_PERSIST_SESSIONconfig row,--limitin the command reference, SDK/session-cache discoverability.services//sdk/.Test plan
make checkgreen; full CLI + SDK e2e green against demo (account flat).🤖 Generated with Claude Code