https://raw.githubusercontent.com/OrcVole/laminar-cloudron/main/CloudronVersions.json
Description
`0.3.4
Laminar
Laminar (lmnr) is an open-source observability platform for LLM applications and AI agents:
OpenTelemetry-native tracing, evaluations, datasets, labelling queues, full-text span search, and SQL
access to all of your trace data.
This package runs the self-hosted open-source (Apache-2.0) Laminar stack as a single Cloudron app — the Next.js dashboard, the Rust ingestion/API server, and bundled ClickHouse (span analytics) and Quickwit (full-text search) — with PostgreSQL provided by the Cloudron addon.
What you get
- OpenTelemetry-native trace ingestion over OTLP/HTTP, plus the Laminar Python/TypeScript SDKs.
- Trace & span explorer with full-text search, a SQL editor, and dashboards.
- Evaluations, datasets, and labelling queues for building and grading eval pipelines.
- Single sign-on via the Cloudron OIDC addon (Better Auth), or passwordless local sign-in.
- All trace data stays on your own server; nothing is sent to a third party.
Cloudron integration
Sign-in through Cloudron SSO (OIDC) when enabled; automatic backups of all state under /app/data;
one-click updates; per-project API keys for SDK and OpenTelemetry-collector ingestion on a dedicated
ingestion subdomain.
Recent Changes
Upstream Laminar 0.3.2 to 0.3.4 (includes 0.3.3). Laminar names no security advisory for this range (its GitHub release notes list none). Routine dependency updates only: "bump vulnerable deps; bump action versions" (PR #2693), the app-server's TLS crypto moves to aws-lc-rs (PR #2697), and the Next.js frontend moves to 16.4.3 (PR #2632). New features include several dashboards per project, Okta SSO with SCIM, an audit log, agent versioning rebuilt on agent prompts (off by default), a light theme, and hosted evals (needs an operator-supplied Daytona key, so inactive here).
The Rust toolchain used to build the server is 1.98, as upstream's.
Database migrations run on the first start after updating, and some are not reversible. Fourteen in PostgreSQL (0115 to 0128) and twelve in ClickHouse (72 to 83). Take a Cloudron backup before updating. In PostgreSQL the agent-versioning tables created by 0.3.x are dropped and rebuilt (0116, 0119; the feature was off by default), the legacy browser-agent and chat tables are dropped after their rows are copied (0123), and rows of signals, triggers and jobs whose project no longer exists are deleted (0117). In ClickHouse,
signal_eventsmoves to a new table type: the old one is renamedold_signal_events, its history is copied over in the background after the frontend starts, and the old table is then renamedold_signal_events_copiedand kept until dropped by hand, so ClickHouse storage and backups carry a second copy of the signal events until then.On the first start Laminar copies signal-event history into its new table. Events whose signal no longer exists are
not copied and stay in
old_signal_events_copied, which upstream never removes, so it is carried in every backup. Onceyou have checked the new signal pages, you can drop it from the ClickHouse console (
DROP TABLE old_signal_events_copied).Restoring a backup from before this update needs the restore recipe in the post-install notes: a plain restore leaves
ClickHouse at the newer schema and the older version refuses to start.
The optional "SQL access to Postgres entities" feature that upstream adds (the
CLICKHOUSE_POSTGRES_*settings) is not configured by this package and stays off.Usage telemetry is unchanged for this package: still switched off (
LAMINAR_TELEMETRY_DISABLED=true). Upstream's heartbeat now also reports licence status, trial dates and up to 20 user email domains, which is why this matters.
