Skip to content
This repository was archived by the owner on Oct 30, 2023. It is now read-only.

v0.13.0#231

Open
jaggedsoft wants to merge 386 commits into
binance-exchange:masterfrom
ccxt:master
Open

v0.13.0#231
jaggedsoft wants to merge 386 commits into
binance-exchange:masterfrom
ccxt:master

Conversation

@jaggedsoft
Copy link
Copy Markdown
Member

No description provided.

carlosmiei and others added 30 commits February 21, 2026 17:41
Bumps [rollup](https://github.com/rollup/rollup) from 4.40.0 to 4.59.0.
- [Release notes](https://github.com/rollup/rollup/releases)
- [Changelog](https://github.com/rollup/rollup/blob/master/CHANGELOG.md)
- [Commits](rollup/rollup@v4.40.0...v4.59.0)

---
updated-dependencies:
- dependency-name: rollup
  dependency-version: 4.59.0
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
Bumps [minimatch](https://github.com/isaacs/minimatch) from 3.1.2 to 3.1.5.
- [Changelog](https://github.com/isaacs/minimatch/blob/main/changelog.md)
- [Commits](isaacs/minimatch@v3.1.2...v3.1.5)

---
updated-dependencies:
- dependency-name: minimatch
  dependency-version: 3.1.5
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
The !ticker@arr stream has been removed from Spot Testnet and is
expected to be removed from mainnet. Replace with !miniTicker@arr
as recommended by Binance docs.

Futures and delivery streams are unchanged as they still support
!ticker@arr.

Closes #978
fix(ws): use !miniTicker@arr for spot prevDay stream
….1.5

build(deps-dev): bump minimatch from 3.1.2 to 3.1.5
build(deps-dev): bump rollup from 4.40.0 to 4.59.0
Route futures WebSocket streams to Binance's new category-based URLs
per the 2026-03-06 upgrade notice. Legacy URLs retire 2026-04-23.
The new /private/ endpoint requires ?listenKey=<key> format
instead of the legacy path-based /<key> format.
feat: migrate USDⓈ-M futures WS to /public /market /private endpoints
Binance's USDⓈ-M futures WebSocket split (2026-03-06) routes streams to
separate /public, /market and /private endpoints and will not push
cross-category streams on a single connection. futuresSubscribe() picked
the routing category from streams[0] only, so a combined subscription
mixing e.g. @aggTrade (market) and @Depth (public) routed everything to
one endpoint and silently dropped data for the other category.

Validate that every stream in a combined subscription shares the same
category and throw a descriptive error otherwise, so callers fail loudly
and subscribe per category (also Binance's recommendation). All built-in
helpers already build homogeneous arrays, so none are affected.
The ws-endpoints-migration test file (added in #985) was never wired into
any npm script or CI step, so its assertions — including the new
mixed-category guard — never gated PRs. Add a `ws-tests-migration` script
that runs only the hermetic (non-"Live:") describes, no network or API
keys required, and invoke it from the CI workflow.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
…uard

fix(futures-ws): reject mixed-category combined streams
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants