Skip to content

chore: release v5.3.0 - #614

Merged
hogan-yuan merged 1 commit into
mainfrom
chore/release-v5.3.0
Oct 23, 2026
Merged

hogan-yuan merged 1 commit into
mainfrom
chore/release-v5.3.0

Conversation

@hogan-yuan

Copy link
Copy Markdown
Member

Release v5.3.0. Bumps workspace 5.2.2 → 5.3.0.

Minor bump: new US-account APIs, and calls that only work in the AP data center now fail fast with a region error.

New since v5.2.2 (#613)

  • Added: US-account asset methods on TradeContext — us_cash_and_buy_power, us_available_holding, us_transaction_history, us_exchange_rates (Rust async + blocking, Node.js, Python; Java JNI entry points). US data-center tokens only.
  • Changed: account_balance, cash_flow, stock_positions, fund_positions, margin_ratio, order_detail, all_executions and PortfolioContext.exchange_rate are AP-only. A US data-center account gets HttpClientError::DcRegionRestricted without a request, instead of gateway code 12 / HTTP 500.
  • Changed: the DcRegionRestricted message keeps its existing text and appends ; <hint> naming the alternative endpoint. Code that matches the message by exact equality must be updated; prefix matching keeps working.
  • Fixed: Execution.side defaults to Unknown when the response omits it (US /v1/trade/execution/history), so history_executions no longer fails to deserialize.
  • Fixed: USCryptoEntry carries the full set of fields returned by the gateway (quantity, market, name, prices, ...).
  • Fixed: option_chain_info_by_date calls POST /v1/quote/options/strikes.

Verified on a Longbridge US production account before merge: all new US methods return data, history_executions parses fills without side, and every AP-only method returns the region error with its hint.

Only Cargo.toml (workspace version + internal dep reqs) and CHANGELOG.md change.

🤖 Generated with Claude Code

@hogan-yuan
hogan-yuan merged commit c275573 into main Oct 23, 2026
6 checks passed
@hogan-yuan
hogan-yuan deleted the chore/release-v5.3.0 branch October 23, 2026 08:42
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