What lmnr-ai/lmnr shipped
Written by FoxPlug from the repository's own releases; not affiliated with Laminar. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/lmnr-ai/lmnr; Laminar did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.
Get a weekly update like this for your product, free
Week of October 5, 2026
What shipped
- Released v0.3.0, which adds Valkey to the default Docker compose files, bumps to a newer version, and migrates the postgres schema in a way that cannot be reversed without a backup. Release
- Merged dataset CRUD together with role-based read restrictions, system prompt versioning improvements, shared trace display, view policies, LLM profile improvements, Valkey in compose, usage breakdown changes, and an update to a related package. Pull request #2532
- Added onboarding personalization that prefills the workspace name on a first visit for a new domain. Pull request #2482
- Added compression and dedup savings visibility to the workspace usage breakdown. Pull request #2491
- Alert emails now include the signal event trace ID and event ID in the View link so the matching event is selected. Pull request #2518
- Welcome and workspace invitation emails now come from a named sender address while billing emails keep the founders address, and the welcome introduction and tracing bullet were updated. Pull request #2490
- Refreshed the welcome and workspace invitation email templates, reusing the welcome banner asset and logo for both. Pull request #2483
- Replaced all email template links with the current project domain. Pull request #2513
- Removed the bundled npm CLI from the frontend runner image to drop dependencies carrying known findings. Pull request #2524
- Fixed the open-source sidebar card so it no longer flashes during hydration. Pull request #2510
Why it matters
This week brings a release with a compose change and a postgres schema migration that cannot be rolled back without a backup, so upgrade planning matters. It also lands role-based read restrictions and dataset CRUD, which change what data different people can see and manage. Alert emails and workspace usage views give teams more context when tracing events and reviewing usage.
Changelog entry
- V0.3.0: Valkey added to default Docker compose files, dependency bumped, and an irreversible postgres schema migration that needs a backup before rollback. Release
- Dataset CRUD, role-based read restrictions, system prompt versioning improvements, shared trace display, view policies, LLM profile improvements, Valkey in compose, usage breakdown, and package update. Pull request #2532
- Removed the bundled npm CLI from the frontend runner image, dropping dependencies with known findings. Pull request #2524
- Alert emails now include the signal event trace ID and event ID so the View link opens the matching event. Pull request #2518
- Email template links now use the lmnr.ai domain, including welcome email documentation and blog links. Pull request #2513
- Set email letter spacing to zero across welcome, workspace invitation, and report emails. Pull request #2512
- Replaced raw UI colors with theme tokens so those surfaces follow light and dark themes. Pull request #2395
- Fixed the open-source sidebar card so stored visibility is known before it renders, removing the hydration flash. Pull request #2510
- Added a warning log when the default LLM header configuration fails validation. Pull request #1820
- Landing header updated with an optional mobile navigation mode, plus blog stickiness and pricing spacing changes. Pull request #2492
- Workspace usage breakdown now shows compression and dedup savings. Pull request #2491
- Added the Flow-1 announcement banner to landing, pricing, and blog pages with an animated dot grid and cloud artwork. Pull request #2489
V0.3.0 is out: Valkey in default Docker compose, a version bump, and a one-way postgres schema migration, so make a backup if you may roll back. This week also adds dataset CRUD, role-based read restrictions, alert email links straight to the event trace, and usage dedup savings.
V0.3.0 is out. The default Docker compose files now include Valkey, a bundled dependency was bumped, and the postgres schema migration is irreversible, so make a backup if you may want to roll back. Alongside the release, this week added dataset CRUD and role-based read restrictions, so read access and data management can be scoped more precisely. Alert emails now link straight to the signal event trace with the matching event selected. Workspace usage views show compression and dedup savings. Welcome and invitation emails were refreshed with updated copy and sender address, and email links now use the lmnr.ai domain.
Week of September 28, 2026
What shipped
- Signals pricing switched from monthly per-tier allowances to a pay-as-you-go model with updated rates and credit state across Postgres and ClickHouse. Pull request #2471
- Workspace Usage tab redesigned with ClickHouse-backed API and new chart interface to show detailed billing estimates. Pull request #2479
- User template versioning added to ingestion pipeline, enabling per-version regex resolution and LLM fallback caching for trace content. Pull request #2452
- Sidebar cards refactored to show Signals credit as spend against total credit and align usage progress bars with design specs. Pull request #2480
- Direct user-task extractions now cached by exact text for 5 minutes to reduce repeated processing. Pull request #2464
- Setup CTA updated with rotating agent icons and copy-on-hover interaction while keeping hero buttons responsive on mobile. Pull request #2481
- Fixed blog code blocks disappearing in long posts caused by React lazy-loading child references in production builds. Pull request #2465
- Included Signals credits reduced to $2.50 Free, $7.50 Starter, and $25 Pro with pricing display alignment across frontend and backend. Pull request #2454
- Parent ID index added on clusters table for query performance. Pull request #2475
- Landing page Signals pricing calculator unified at $0.05/1M input, $0.01/1M cached input, and $0.35/1M output tokens with measured token medians. Pull request #2378
Why it matters
The billing and pricing model changed substantially this week with Signals moving to usage-based pricing and the UI updated to reflect spend tracking. Template versioning went live for better trace content extraction. Multiple foundational pieces now support accurate credit accounting and clearer user visibility into costs.
Changelog entry
- Signals pricing updated: monthly per-tier allowances replaced with pay-as-you-go rates; Postgres/ClickHouse credit state and Stripe metering inputs adjusted Pull request #2471
- Usage tab redesigned with ClickHouse-backed API and new chart-based bill estimates interface Pull request #2479
- User template versioning added to ingestion pipeline with per-version regex resolution and direct extraction caching Pull request #2452
- Sidebar refactored: Signals credit shown as spend against total; usage progress bars aligned to design Pull request #2480
- Direct user-task extractions cached by exact text for 5 minutes Pull request #2464
- Setup CTA now rotates agent icons with copy-on-hover interaction; hero buttons remain responsive on mobile Pull request #2481
- Fixed blog code blocks disappearing in long posts due to React lazy-loading behavior Pull request #2465
- Included Signals credits reduced: $2.50 Free, $7.50 Starter, $25 Pro; pricing displays and backend detection aligned Pull request #2454
- Parent ID index added on clusters table Pull request #2475
- Landing calculator unified Signals pricing at $0.05/1M input, $0.01/1M cached input, $0.35/1M output with measured medians Pull request #2378
This week: Signals pricing moves to pay-as-you-go with real-time usage tracking, user template versioning ships for trace extraction, and billing UI redesigned for clarity.
Ship week: Signals pricing model updated to pay-as-you-go with ClickHouse-backed usage tracking and clearer billing UI. User template versioning now enables per-version regex resolution for trace content. Setup CTA rotates agent icons, sidebar cards show spend against total credit, and blog rendering fixed for long-form content.
Week of September 21, 2026
What shipped
- Fixed Responses API LLM profiles to use non-strict function tools and set store: false on response requests. Pull request #2422
- LLM profiles now reject unused fields instead of silently dropping them, and surface malformed AEAD_SECRET_KEY errors during setup. Pull request #2424
- Fixed shared trace loading with responsive layout improvements and corrected trace page initialization. Pull request #2399
- Refactored span message processing into separate stage functions, breaking down a 720-line function into manageable pieces. Pull request #2390
- Added Redis batch insert with TTL support to the cache layer for more efficient bulk key writes. Pull request #2442
- Search snippets are now withheld under masking policy on dual-mode projects to prevent PII leaks. Pull request #2393
- API keys and CLI tokens now read as masked when accessed on dual-mode projects. Pull request #2392
- Removed the CLUSTERING_ENABLED frontend feature flag since clustering is on by default in EE and OSS produces no clusters. Pull request #2420
- Added a Redis cache key constant for temporary signal throttling per project. Pull request #2439
Why it matters
Custom gateway support through Responses API expands LLM profile flexibility for self-hosted deployments. PII masking improvements strengthen security for dual-mode projects. Refactoring span processing and fixing trace loading improve code maintainability and user experience.
Changelog entry
- Fix Responses API to use non-strict function tools and set store: false on response requests Pull request #2422
- Reject unused fields in LLM profile configuration and surface malformed AEAD_SECRET_KEY errors Pull request #2424
- Fix shared trace loading and implement responsive trace layout on shared trace pages Pull request #2399
- Refactor span message processing into separate stage functions for improved maintainability Pull request #2390
- Add
batch_insert_with_ttlto cache layer for efficient bulk Redis key operations Pull request #2442 - Withhold search snippets under masking policy on dual-mode projects Pull request #2393
- Apply masking policy to API key and CLI token reads on dual-mode projects Pull request #2392
- Remove CLUSTERING_ENABLED frontend feature flag Pull request #2420
- Add Redis cache key for temporary signal throttling per project Pull request #2439
Responses API now works with custom gateways. Fixed PII masking in dual-mode projects. Improved trace loading and responsive layouts. Better error handling for LLM profile setup.
This week we expanded LLM profile support with Responses API for custom gateways, strengthened PII protection through masking policies on dual-mode projects, and improved the trace viewing experience with responsive layouts and fixed loading behavior. We also refactored span processing into stage functions and added batch Redis operations for better performance.
Week of September 14, 2026
What shipped
- Dual mode for PII handling now stores canonical text alongside byte-range masks, letting different project members read appropriate versions of the same trace. Pull request #2361
- Fixed realtime SSE to respect dual-mode access policies so masked readers don't receive unmasked agent input over the channel. Pull request #2389
- Refactored PII redactor internals to use SpanVerdict, unify index space, and properly fail batches when project mode lookup fails. Pull request #2384
- Access policies derived from actor roles are now baked into span and trace reads through the query engine. Pull request #2360
- Added dataset CRUD API with create, read, update, delete, and row operations under both project and CLI auth paths. Pull request #2340
- Span detail view now skips reasoning blocks when extracting heuristic previews from reasoning model outputs. Pull request #1865
- Declared the docs sitemap in robots.txt to improve indexing of the 139 documentation URLs. Pull request #2374
- Added static SVG brand assets (icon and wordmark) under frontend/public/brand/ for frontend use. Pull request #2375
- Reverted force-commit-on-batch change to prevent unbounded memory growth in Quickwit at high traffic. Pull request #2362
Changelog entry
- Dual mode for PII now available: stores canonical text and masks, with read paths respecting access policies per actor Pull request #2361
- Fixed realtime
agent_inputSSE to respect dual-mode masks for project subscribers Pull request #2389 - Refactored PII redactor: SpanVerdict type, unified index space, batch-level mode lookup failures Pull request #2384
- Access policies derived from actor roles now applied to span and trace reads Pull request #2360
- Dataset CRUD API: POST/GET/PATCH/DELETE datasets and rows via /v1 (project auth) and /v1/cli (user auth) Pull request #2340
- Span detail view now skips thinking blocks when extracting previews from reasoning model outputs Pull request #1865
- Reverted force-commit batching to prevent unbounded Quickwit memory growth at high traffic Pull request #2362
Shipped dual-mode PII handling: store text once, apply masks per reader. Added dataset CRUD API. Fixed realtime agent_input masking, span preview extraction, and Quickwit memory pressure.
This week we shipped the final piece of trace-level access control: dual-mode PII handling stores canonical text with byte-range masks, letting different project members read appropriate versions of the same trace. We also added a dataset CRUD API for programmatic dataset management, fixed realtime masking for dual-mode projects, improved span preview extraction for reasoning models, and resolved a Quickwit memory issue at high traffic.