Skip to content

Releases: ProjectOpenSea/stream-js

v0.4.0

Choose a tag to compare

@ryanio ryanio released this 01 Jun 21:29

What's Changed

  • Add server-side event type filtering support. The onEvents method now passes an event_types array in the Phoenix channel join params, enabling the backend to filter events at subscription time. Individual on* methods remain backward-compatible (no event_types param — the server sends all events). (#375)

This is the SDK counterpart to the backend support for subscription-time event filtering.

Full Changelog: v0.3.1...v0.4.0

v0.3.1

Choose a tag to compare

@ryanio ryanio released this 24 Apr 20:12

What's Changed

  • Migrate default WebSocket endpoint from wss://stream.openseabeta.com/socket to wss://stream-api.opensea.io/socket. The new endpoint connects to the Kotlin stream API service which reads directly from Kafka, reducing event delivery latency. No protocol or API changes — existing client code works without modification. (#113)

Full Changelog: ProjectOpenSea/opensea-devtools@stream-v0.3.0...stream-v0.3.1

v0.3.0

Choose a tag to compare

@ryanio ryanio released this 17 Apr 19:21

Minor changes

  • Add version field to BaseStreamMessage for out-of-order event resolution (#70, OS2-31317)

Every stream event now includes a numeric version field that is monotonically increasing per source entity. Use it to handle out-of-order event delivery: when two events arrive for the same entity, the one with the higher version is newer state.

Version scale depends on event type

Event types version semantic
item_listed, item_cancelled, item_received_offer, item_received_bid, collection_offer, trait_offer, order_invalidate, order_revalidate Order revision counter (small monotonic integer per order)
item_transferred, item_sold, item_metadata_updated Epoch milliseconds of the event's source timestamp

Both representations are monotonic and sufficient for resolving out-of-order delivery, but the two scales are not comparable to each other. Compare version only for the same entity within the same event family. See the Event Versioning section of the README for usage examples.

Notes

  • This is an additive change: BaseStreamMessage<Payload> gains a required version: number field.
  • No code changes required for existing consumers — events previously continued to work without the field at runtime; upgrading picks up the new typed field for those who want to use it.

v0.2.3

Choose a tag to compare

@ryanio ryanio released this 12 Nov 23:46
e21442b

What's Changed

New Contributors

Full Changelog: v0.2.2...v0.2.3

v0.2.2

Choose a tag to compare

@ryanio ryanio released this 03 Nov 18:40
11aa30a

What's Changed

  • Add item field to OrderValidationEventPayload by @ryanio in #491
  • chore(deps): update dependency phoenix to v1.8.1 by @renovate[bot] in #481

Full Changelog: v0.2.1...v0.2.2

v0.2.1

Choose a tag to compare

@ryanio ryanio released this 26 Aug 21:11
aae332f

What's Changed

v0.2.0 was missing dist folder, added prepublish build step.

Full Changelog: v0.2.0...v0.2.1

v0.2.0

Choose a tag to compare

@ryanio ryanio released this 25 Jul 16:28
3ea5d31

What's Changed

Full Changelog: v0.1.3...v0.2.0

v0.1.3

Choose a tag to compare

@ryanio ryanio released this 13 Nov 18:13
d18562e

What's Changed

Full Changelog: v0.1.1...v0.1.3

v0.1.2

Choose a tag to compare

@0xdeployer 0xdeployer released this 05 Sep 18:09
cf72273

Adding chain to event payload type.

v0.1.1

Choose a tag to compare

@ryanio ryanio released this 05 Sep 18:06
cf72273

PRs included:

  • fix exports types, #302
  • add src to files, #293
  • update dev deps to carat range, #296