Skip to main content
Updates are grouped by required customer action. Product filters show only the areas that affect your integration. See News for impact definitions.
​
Lerian Console

​
Lerian Console deletion contract

What changedThe documentation now correctly states that deleting a Console user or application permanently removes it and cannot be undone. Application details show the name, description, ClientId, and ClientSecret; they do not show scopes or redirect URIs.Who is affectedTeams that administer users or applications in Lerian Console.What you need to doReview access-management runbooks before your next deletion. Do not rely on application details as a source of scope or redirect URI data.
​
Platform

​
Helm chart coverage for BYOC deployments

What changedDeployment documentation now correctly states that official Helm charts are available for the products and platform components supported through Lerian’s Helm repository; it no longer states that every product has an official chart.Who is affectedTeams planning or operating BYOC deployments with Helm.What you need to doConfirm chart availability for your target product or platform component before planning a BYOC deployment.

​
Action required

​
Matcher

​
Matcher error and idempotency contract

What changedThe documentation now correctly describes Matcher’s RFC 9457 error envelope and idempotency-key constraints and retry behavior. Runtime behavior did not change.Who is affectedTeams integrating with the Matcher API.What you need to doAlign error parsing and generated idempotency keys with the documented contract before your next client release.
​
Pix

​
SPI operations PII startup configuration

What changedThe documentation now correctly states that the SPI service requires SPI_OPERATIONS_PII_ENCRYPTION_KEY to be a valid AES-256 key and SPI_OPERATIONS_BLIND_INDEX_PEPPER to contain at least 32 characters in every environment. Missing, malformed, or too-short values prevent the service from starting.Who is affectedTeams deploying or operating the SPI service for Pix operations.What you need to doBefore the next SPI start or redeployment, verify that both values are supplied through your secret manager and meet the documented requirements. Do not commit or log either value.
​
Flowker

​
Flowker scheduler Redis isolation configuration

What changedThe documentation now correctly states that the Flowker scheduler has its own Redis configuration, but startup does not enforce isolation from the Redis used for tenant lifecycle events. Operators must provide a dedicated Redis instance or, when sharing an instance, a different logical database index.Who is affectedTeams running Flowker workers with scheduled workflows enabled.What you need to doVerify the scheduler Redis settings before enabling or continuing to run scheduled workflows. Point the scheduler to a dedicated Redis instance, or configure a logical database index that tenant lifecycle events do not use.

​
Product index