Skip to content

v0.12.0

Latest

Choose a tag to compare

@github-actions github-actions released this 19 Nov 22:25
· 11 commits to main since this release
77a6fbe

Lightspeed v0.12.0 adds workload identity for Platform automation and makes MCP tools more reliable. Upgrading from v0.11.0 requires a new Temporal namespace.

  • Platform service users can authenticate with short-lived OIDC tokens from a trusted issuer. Administrators can manage federated credentials from the service user’s details or declare them in GitOps configuration.

  • A pipeline can enroll its own organization and apply its configuration with lightspeed config apply --enroll. Repeated runs reuse the organization. The CLI rereads --token-file or LIGHTSPEED_API_TOKEN_FILE on each request so jobs can use rotated tokens. Configure a trusted issuer on Platform and add enrollment rules for workloads that may create organizations. Workload identity setup

  • Runtime-injected MCP tools whose combined server and tool name exceeds 64 bytes now get a stable, shortened name. Calls and approvals still identify the original server and remote tool. #185

  • A broken credential on a provider-hosted MCP server no longer fails the whole turn. The session reports which server needs attention, including when a runtime server’s tool listing fails. Healthy servers remain usable. #180

  • Profile attachment menus hide MCP servers, workspaces and environments already selected in another row. Add picks the next eligible resource and disables when all choices are in use. #147

  • Chat Completions combines nonempty instruction layers into one leading message and sends tool catalogs as user context. The Platform model-provider form also uses the correct OpenRouter API base URL.

  • Platform closes event streams cleanly when a watch expires and shows the running Lightspeed version in the user menu.

scripts/release/workflow-compat.sh v0.11.0 reports breaking. Session workflows now record the resolved target of a tool call. There is no conversion for retained Temporal histories or pending calls that relied on the old MCP naming scheme.

  1. Stop new submissions and drain or cancel open work on v0.11.0. Stop the old workers and back up both databases, object storage and deployment secrets.
  2. Create a fresh Temporal namespace. Set TEMPORAL_NAMESPACE on every runtime process and custom workflow worker before starting matching v0.12.0 components. Namespace cutover guide
  3. Reuse both v0.11.0 databases. The runtime database stays at schema revision 7. Platform applies the federated credential and organization enrollment migrations on startup, advancing its schema from 1 to 3. Verify both services are healthy before reopening traffic.

Full changelog