Skip to content

release: v0.6.0 — SDK full-surface parity + stable positioning#30

Merged
SimonTarara62 merged 6 commits into
mainfrom
sdk-parity-stable-positioning
Jun 14, 2026
Merged

release: v0.6.0 — SDK full-surface parity + stable positioning#30
SimonTarara62 merged 6 commits into
mainfrom
sdk-parity-stable-positioning

Conversation

@SimonTarara62

Copy link
Copy Markdown
Owner

Summary

Minor release. Brings the SDK to literal full API parity and repositions it as stable within 0.x.

  • Added (SDK): app.session.server_time(), app.session.details(), app.session.encryption_key() — the three previously CLI-only connectivity reads. The SDK now covers all 41 endpoints; the coverage matrix is 164/164 (no N/A). The CLI session time/details/encryption-key commands now share these SessionManager methods (one implementation).
  • Changed (positioning): dropped "experimental" everywhere; the documented SDK surface (CapitalComApp, CapitalComConfig, RiskPolicy, services, core.models) is now stable within 0.x — no breaking changes without a deprecation cycle; breaking changes reserved for 1.0.
  • Changed (docs): README/docs/api-coverage.md describe full (not "main") coverage; the coverage badge is relabeled CLI + SDK coverage.

No breaking changes; additive public SDK methods → minor bump.

Test Plan

  • Offline: ruff + mypy clean, 305 passed; version metadata = 0.6.0.
  • Live demo e2e (read-only, real keys): 141 passed, 0 failed; the new test_sdk_session_reads and the refactored CLI session reads pass.
  • Coverage matrix 164/164 (100%), no N/A; drift + completeness guards green.
  • CI green on this PR → then tag v0.6.0 to publish.

🤖 Generated with Claude Code

@SimonTarara62 SimonTarara62 merged commit b71d9ba into main Jun 14, 2026
6 checks passed
@SimonTarara62 SimonTarara62 deleted the sdk-parity-stable-positioning branch June 14, 2026 18:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant