ccs-chat-notifications-client changelog

Versions follow semver. For the package itself see ccs-chat-notifications-client. The reference is at /sdks/ccs-chat-notifications-client/reference/.

1.2.0 (2026-10-10)

Automatic channel pickup (non-breaking).

The client now reopens its stream automatically when the user creates or is added to a CHANNEL conversation, so that channel’s message.created (and other) events start arriving with no extra call. The reconnect for being added to a channel relies on the user_id field the backend now returns from realtime-token; against an older backend that step is skipped.

1.1.0 (2026-10-03)

CommonJS build (non-breaking).

Every entry point now ships CommonJS next to ES modules.

1.0.0

Breaking. Chat on Identity Server v3.

1.0.0 targets the context-scoped Chat API. A single CCS access token now serves every tenant/application the user belongs to, so the realtime client has to be told which context it’s listening in.

0.x	1.0.0
new ChatNotificationsClient({ chatApiUrl, getAccessToken })	also requires tenantId and applicationId
GET /notifications/realtime-token?channelId=<id>	GET /tenants/:tenant_id/applications/:application_id/notifications/realtime-token?conversation_id=<id>
realtime-token response streamUrl	stream_url (snake_case, like every Chat API field)
subscribeToChannel(id) / unsubscribeFromChannel(id)	subscribeToConversation(id) / unsubscribeFromConversation(id) (Angular and React wrappers too)
camelCase event payloads (messageId, senderId, content, productId, …)	the API’s snake_case payloads, always carrying tenant_id / application_id (+ conversation_id); message.created wraps the full message as event.message
events: message.created, typing, presence.updated	adds message.updated, message.deleted, reaction.added/removed, member.added/removed, conversation.created/updated/deleted, conversation.access_revoked
new ChatPushClient({ chatApiUrl, getAccessToken })	also requires tenantId; devices live at /tenants/:tenant_id/notifications/push/devices
VAPID key response publicKey	public_key

Switching tenant or application means disconnecting and creating a new client for the new context.