Changelog

This page lists Livqeno's packages, explains how versions work, and records big changes. Check it before you upgrade a package, or when an example in an old blog post or repo doesn't match what you see today.

Packages

Each package has its own version number, so the numbers don't match across packages. (Why: see How versioning works.)

Package	Where to get it
`@livqeno/rtc`	npm
`@livqeno/chat`	npm
`@livqeno/live`	npm
`@livqeno/react`	npm
`@livqeno/react-native`	npm
`@livqeno/server`	npm
`@livqeno/cli`	npm
`livqeno_rtc`	pub.dev
`livqeno_chat`	pub.dev
`livqeno_live`	pub.dev
`livqeno`	PyPI

To see a package's current version, check its latest tag on npm. Release notes for each version will appear here once there are enough to be useful.

Notable changes

Coming in the next release

These are fixed in the source and documented here, but not on npm yet:

@livqeno/chat 0.1.1: after a reconnect, the client sends your presence status again, so other members keep seeing you online. With 0.1.0 (the current latest on npm), call setPresence() again after a reconnected event.
@livqeno/cli: livqeno projects use and livqeno projects inspect will also accept a project's exact name. With 0.1.0, pass the project ID.
@livqeno/server: getOrCreate on rooms.create() and chat.createConversation() is added to the TypeScript types. 0.1.0 already sends it and the API already honours it, but TypeScript rejects the property. Until the release, add // @ts-expect-error above that line.
livqeno 0.2.0 (Python): get_or_create=True on rooms.create() and CreateConversationParams. 0.1.0 (the current version on PyPI) raises TypeError for it. Until the release, catch the LivqenoError with code == "RAVEN_CONFLICT" and find the room with rooms.list().

Effects removed

The Effects product (camera filters and presets) has been removed.

@livqeno/effects is no longer developed or documented.
These were removed from the other SDKs:
- LocalTrack.attachEffects() / detachEffects() in @livqeno/rtc
- The useCameraEffects hook in @livqeno/react
- The effects pipeline in the React Native and Flutter SDKs
- The EffectsErrorCode error list
The /effects/* and /live-streaming/filters pages now redirect.

Want to process camera frames yourself? Publish the result as a custom track. See A source Livqeno does not capture.

How versioning works

Each package is versioned on its own. A fix to the CLI doesn't give @livqeno/rtc a new version with no changes in it.

Every change to a published package comes with a written note. Those notes become the release notes. Nothing is published without one.

What is stable

Part	How stable it is today
REST API (`/v1`)	Only additions. New fields may appear. Ignore ones you don't know.
Error codes	`RAVEN_*` codes are stable. `legacyCode` is old and will be removed.
Chat WebSocket messages	A published protocol, versioned separately from the SDK.
RTC signaling messages	A published protocol, versioned separately from the SDK.
SDK APIs	Before 1.0. Any function signature may change.

What this means in practice: your REST calls and error handling are safe to build on. For the SDKs, pin exact versions in your package.json or pubspec.yaml, and read the release notes before you upgrade.

Where to watch for changes

Each package's npm release notes, starting with the first tagged release.
Known limitations: what isn't finished yet, updated as things ship.