What langfuse/langfuse shipped
Written by FoxPlug from the repository's own releases; not affiliated with Langfuse. 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/langfuse/langfuse; Langfuse 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 November 2, 2026
What shipped
- Amazon S3 blob storage exports can now authenticate with an IAM role instead of access keys, across settings, the API and the export worker. Pull request #19723
- External media storage on Amazon S3 can now use IAM role auth from the customer AWS account instead of stored access keys. Pull request #19721
- Monitor alerts now include the evaluated metric value and unit alongside the threshold that was crossed. Pull request #19872
- Observation usage is no longer inferred from content, since tokenization cannot account for provider-side cache usage or hidden reasoning. Pull request #19802
- Trace-level correction scores now render in the single-trace UI instead of only being returned by the API. Pull request #19700
- Dashboard queries with a far-future end timestamp no longer loop forever in ClickHouse fill, which previously ignored the execution time limit and grew a replica by 172 GiB. Pull request #19886
- Widget chart CSV exports now escape header names so columns stay aligned when breakdown names contain commas, quotes or line breaks. Pull request #18128
- The view observations link on monitor alerts now carries the alert filters instead of falling back to session-stored filters. Pull request #19781
- Generations that omit provider usage now show a usage not submitted chip linking to model settings. Pull request #19803
Why it matters
This week adds IAM role auth for S3 in two places, so exports and media storage no longer require stored access keys. Several fixes target dashboards and monitors: overflowing chart lists get a scroll cue, far-future end timestamps no longer hang ClickHouse, and alerts now show the metric value that triggered them. Usage estimates from content inference were removed because they can mislead when providers use caching or hidden reasoning.
Changelog entry
- S3 blob storage exports support IAM role auth. Pull request #19723
- External media storage on S3 supports IAM role auth. Pull request #19721
- Monitor alerts include the metric value and unit. Pull request #19872
- Observation usage is no longer inferred from content. Pull request #19802
- Trace-level correction scores render in the single-trace UI. Pull request #19700
- Dashboard queries with far-future end timestamps no longer hang ClickHouse fill. Pull request #19886
- Deleted scores are excluded from the scores join when FINAL is skipped. Pull request #19884
- Oversized score fields are truncated in PostHog and Mixpanel exports. Pull request #19798
- Widget CSV exports escape header rows. Pull request #18128
- Monitor alert links carry their filters to the observations view. Pull request #19781
- Generations without submitted usage show a usage not submitted chip. Pull request #19803
Week of October 26, 2026
What shipped
- Version 4.72.0 shipped, including AI gateway span attribution to their gateway API key and service, AI gateway request counts from self-hosted instances, and PagerDuty alerts for project notifications and prompt changes. Release
- A new AI_GATEWAY organization membership role lets an organization give a member AI Gateway access without granting access to the rest of the organization. Pull request #19262
- The AI Gateway settings gained an analytics tab that builds on gateway span attribution on the events tables. Pull request #19417
- AI Gateway analytics can now be filtered by user and API key, narrowing every widget to the selection. Pull request #19458
- Skill changes can now trigger version automations for version creation, label and tag updates, and deletion, with name, label and tag filters. Pull request #19296
- A new monitor automation dialog replaces the generic automation form for creating monitor-triggered automations. Pull request #19448
- Prisma reads now retry on transient Postgres connection errors, so a brief Postgres restart no longer fails every query in that window. Pull request #19480
- ClickHouse migration 0050 now materializes legacy scores columns, fixing self-hosted upgrades that failed when scores still had small Compact parts. Pull request #19443
- Gateway key authentication now rejects user-bound keys whose owner no longer has an organization role that grants gateway invoke. Pull request #19542
- Support engineers can be added to customer organizations with short-lived access that revokes itself after some hours. Pull request #19278
Why it matters
This week the AI Gateway moved from setup work toward day-to-day use: a dedicated membership role, analytics with user and API key filters, invite flows, and requests always recorded on Cloud. Beyond the gateway, self-hosted operators get safer upgrades and fewer failed queries during Postgres restarts, and automations now cover skill changes.
Changelog entry
- Release v4.72.0 with AI gateway span attribution, self-hosted gateway request counts, and PagerDuty alerts. Release
- Add an AI_GATEWAY organization membership role scoped to the gateway. Pull request #19262
- Add an analytics tab to the AI Gateway settings. Pull request #19496
- Filter AI Gateway analytics by user and API key across all widgets. Pull request #19458
- Support version automations triggered by skill creation, label and tag updates, and deletion. Pull request #19296
- Add a dedicated monitor automation dialog for monitor-triggered automations. Pull request #19448
- Retry Prisma reads on transient Postgres connection errors. Pull request #19480
- Skip Prisma read retries inside transactions. Pull request #19508
- Materialize legacy scores columns in ClickHouse migration 0050 for self-hosted upgrades. Pull request #19443
- Reject gateway keys whose owner can no longer invoke the gateway. Pull request #19542
- Attach event query attributes to procedure spans. Pull request #19496
- Bump @hono/node-server to 2.1.3 to address a dependency advisory. Pull request #19465
Langfuse 4.72.0 is out. AI Gateway requests are attributed to their gateway API key and service, a new AI_GATEWAY org role limits access to the gateway alone, and analytics can be filtered by user and API key. Also this week: skill changes can trigger automations, and Prisma read
Langfuse 4.72.0 is out. AI Gateway spans are now attributed to their gateway API key and service, self-hosted instances report gateway request counts, and PagerDuty can receive alerts, project notifications and prompt changes. The AI Gateway settings gained an analytics tab, and analytics can be filtered by user and API key. A new AI_GATEWAY organization membership role gives a member gateway access without the rest of the organization. Outside the gateway: skill changes can trigger version automations, a dedicated monitor automation dialog is in, and Prisma reads retry on transient Postgres connection errors. ClickHouse migration 0050 now handles legacy scores columns so self-hosted upgrades complete.
Week of October 19, 2026
What shipped
- Added read-only Topics endpoints under the unstable public API, marked unstable because Topics is in closed beta. Pull request #19104
- The Cmd+K menu can now jump to prompts, datasets, annotation queues and evaluators by name. Pull request #18921
- Added a runBatchEvaluation tool and a
batch_action_idon batch run outputs, backed by a shared BatchEvaluationService. Pull request #19314 - Changing a webhook or PostHog destination URL now requires secrets again, so stored write-only secrets are not sent to a new host. Pull request #19261
- Legacy plaintext webhook headers are now masked and encrypted instead of returned unmasked by the automations endpoints. Pull request #19207
- Added separate Skill Names (Available) and Skill Names (Loaded) filters to the trace sidebar and user tables. Pull request #19279
- Added assembleTranscriptContext, which returns the assembled transcript together with the trace's execution issues. Pull request #18993
- Staff admins viewing a customer project or organization through staff access now see a persistent banner. Pull request #19266
- Setup snippets for shell, TOML and JSON are now syntax-highlighted in the gateway key created dialog. Pull request #19306
- The first Topics run now shows analyzing, waiting and failed screens instead of a blank view. Pull request #19285
Why it matters
This week adds the first public API surface for Topics, more ways to find and filter material across the app, and clearer first-run and setup screens. It also tightens how stored secrets are handled when destinations change and adds more checks around batch runs and transcripts.
Changelog entry
- Add read-only Topics endpoints under the unstable public API. Pull request #19104
- Jump to prompts, datasets, annotation queues and evaluators from Cmd+K. Pull request #18921
- Add a runBatchEvaluation tool and
batch_action_idon batch run outputs. Pull request #19314 - Require secrets again when a webhook or PostHog destination URL changes. Pull request #19261
- Mask and encrypt legacy plaintext webhook headers. Pull request #19207
- Add Skill Names (Available) and Skill Names (Loaded) filters to the trace sidebar and user tables. Pull request #19279
- Collect execution issues next to the assembled transcript. Pull request #18993
- Show a banner to staff admins viewing customer data through staff access. Pull request #19266
- Syntax-highlight shell, TOML and JSON setup snippets. Pull request #19306
- Show analyzing, waiting and failed screens on the first Topics run. Pull request #19285
- Show a single setup action as the Topics first-run empty state. Pull request #19291
- Show a deploy placeholder on self-hosted instances without a gateway. Pull request #19269
This week: read-only Topics endpoints under the unstable public API, Cmd+K jumps to prompts, datasets, queues and evaluators, a batch evaluation tool with batch_action_id on outputs, and webhook or PostHog destination changes now require secrets again.
This week's release work on Langfuse: read-only Topics endpoints land under the unstable public API while Topics stays in closed beta. The Cmd+K menu now jumps to prompts, datasets, annotation queues and evaluators, and a batch evaluation tool adds a batch_action_id on batch run outputs. Changing a webhook or PostHog destination URL requires secrets again so stored write-only secrets are not sent to a new host, and legacy plaintext webhook headers are now masked and encrypted. Trace and user tables gain separate Skill Names Available and Loaded filters, and the first Topics run shows analyzing, waiting and failed screens.
Week of October 12, 2026
What shipped
- Project API key permissions are now on by default, with ingestion keys able to read the project. Pull request #18950
- The public API now refuses project keys whose path names another project, closing a cross-project access gap under enforced auth. Pull request #18957
- Processing runs for topics now show recorded summary and embedding costs, with batch totals saved. Pull request #18668
- AI Gateway keys are separated from organization API keys and are managed only on the Gateway keys page. Pull request #18936
- Query events reads no longer opt out of the soft-delete filter, so deleted rows stay hidden. Pull request #18869
- The query AST now resolves CTE names the way ClickHouse does in tenancy, soft-delete, dedup and bind typing. Pull request #18865
- The billable units ledger now counts observations that arrive through event propagation, not only direct OTel writes. Pull request #18954
- Skill management is available as a public opt-in feature preview with Beta badges, retaining the v4 requirement. Pull request #18948
- Cmd+K can now run create actions such as New dashboard, New prompt and New evaluator, plus recent picks. Pull request #18910
Why it matters
This week tightens access control on API keys and the public API, and makes query and billing paths more consistent for self-hosted and cloud users. Cost and usage views gain more accurate numbers, and skills move into a public preview so teams can browse and measure them.
Changelog entry
- Project API key permissions are enabled by default, and ingestion keys can read the project. Pull request #18950
- The public API refuses project keys whose path names another project. Pull request #18957
- Topics processing runs show recorded summary and embedding costs. Pull request #18668
- AI Gateway keys are separated from organization API keys. Pull request #18936
- Events reads consistently hide soft-deleted rows. Pull request #18869
- CTE names are resolved like ClickHouse in tenancy, soft-delete, dedup and bind typing. Pull request #18865
- The billable units ledger counts observations from event propagation. Pull request #18954
- Skill management is a public opt-in feature preview. Pull request #18948
- Cmd+K adds create actions and recent picks. Pull request #18910
- Each skill version gets a Metrics tab with available and loaded counts. Pull request #18947
- Annotation queue setup is visible in the sidebar with draggable score config order. Pull request #18819
This week: project API key permissions on by default with ingestion read access, public API refuses cross-project keys, topics show run costs, AI Gateway keys split from org keys, soft-deleted rows hidden on events reads, and skills open as a public preview. v4.62.0 and v4.63.0 r
Week of October 5, 2026
What shipped
- Version v4.56.0 was released with a design-system CodeSection replacing CodeView, syntax highlighting for session tool previews, ClickHouse spend alerts, and more. Release
- Passwords are now hashed and verified with PBKDF2-HMAC-SHA256 when FIPS mode is required, so bcrypt never runs. Pull request #18444
- FIPS mode now refuses to start when storage options that compute MD5 are enabled. Pull request #18443
- New API keys no longer bcrypt-hash the secret and instead store a placeholder, while still authenticating through the fast hash. Pull request #18442
- Tables with the row-height switch can now be dragged to a custom height so long outputs are readable without opening a peek. Pull request #18445
- List-view observation score reads can be routed to the read replica instead of always reading the primary. Pull request #18502
- The two v1 dashboard score-widget reads now route to the read replica. Pull request #18498
- Events observations list queries now disable read-in-order buffering. Pull request #18542
- Workers can now add optional startup jitter before queue registration to spread Redis connection opens. Pull request #18525
Why it matters
This week brought a major release with UI and session improvements, plus stronger credential handling for FIPS mode and faster list and dashboard reads through the read replica. It also added worker startup jitter to smooth Redis load and graduated decision-model evaluators out of experimental status. Together these changes affect security, database read performance, and daily evaluation workflows.
Changelog entry
- Released v4.56.0 with features including a design-system CodeSection, session tool preview syntax highlighting, and ClickHouse spend alerts. Release
- Hash and verify email and password credentials with PBKDF2-HMAC-SHA256 in FIPS mode. Pull request #18444
- FIPS mode now refuses to start when storage options that compute MD5 are set. Pull request #18443
- New API keys store a placeholder instead of a bcrypt hash of the secret. Pull request #18442
- Tables with the row-height switch can be dragged to a custom row height. Pull request #18445
- List-view observation score reads can use the read replica. Pull request #18502
- V1 dashboard score-widget reads now use the read replica. Pull request #18498
- Events observations list queries disable read-in-order buffering. Pull request #18542
- Workers can add optional startup jitter before registering queues. Pull request #18525
- Decision-model evaluators are no longer marked experimental. Pull request #18541
- Row resizing no longer triggers expensive cell renders, keeping tables responsive with large values. Pull request #18536
- Inline media tags use a readable height and fit their content. Pull request #18524
V4.56.0 is out with a design-system CodeSection, syntax highlighting in session tool previews, and ClickHouse spend alerts. Also this week: PBKDF2 password hashing in FIPS mode, read-replica routing for score and dashboard reads, custom table row heights, and worker startup jitte
Version v4.56.0 shipped this week. It replaces CodeView with a design-system CodeSection, adds syntax highlighting to session tool previews, sends spend alerts for ClickHouse-billed organizations, and more. On the backend, FIPS mode now hashes and verifies passwords with PBKDF2-HMAC-SHA256, new API keys no longer bcrypt-hash their secret, and FIPS mode refuses to start with storage options that compute MD5. List-view observation score reads and v1 dashboard score-widget reads can now go to the read replica, and events list queries disable read-in-order buffering. Workers gained optional startup jitter before queue registration. In the UI, tables with the row-height switch can be dragged to a custom height, and decision-model evaluators are no longer marked experimental.
Week of September 28, 2026
What shipped
- Released v4.50.0 with evaluation facet types, built-in evaluator protection, rule idle time tracking, and error ID visibility in tRPC error toasts. Release
- Added MCP-only support for decision-model evaluators with create, update, test, and template discovery capabilities. Pull request #18166
- Added facet type as a reserved evaluator type, built-in protection flag on evaluators, and nullable
idle_timefield to evaluation rules. Pull request #18144 - Replaced last-five-run indicators with seven-day execution health tracking in evaluator status and tables. Pull request #18113
- Added tool filters (available-tool, called-tool, tool-call) to the session table. Pull request #17884
- Fixed dashboards to return 404 instead of 500 when deleting a missing widget. Pull request #17673
- Fixed API auth to return 404 instead of 500 when updating or deleting a missing API key. Pull request #17677
- Error toasts now display an Error ID from the tRPC trace and include it in issue reports to the Langfuse team. Pull request #17427
- Avatar tooltips now show the view owner's name and email on hover. Pull request #18032
- Metadata on traces, observations and scores is now typed as objects instead of unknown in read schemas for better SDK generation. Pull request #18122
Why it matters
This week focused on error handling consistency and evaluation features. Multiple PRs fixed HTTP 500 errors that should have been 404s when operations target missing resources, improving API correctness. Evaluation improvements include decision-model evaluator support, execution health tracking, and rule idle time configuration, making evaluators more flexible and observable.
Changelog entry
- V4.50.0 released with evaluation facet types, built-in evaluator protection, rule idle time, and error ID visibility Release
- MCP support for decision-model evaluators with create, update, test, and template discovery Pull request #18166
- Facet type evaluators, built-in evaluator flag, and nullable
idle_timeon evaluation rules Pull request #18144 - Seven-day execution health replaces last-five-run indicators in evaluator status Pull request #18113
- Tool filters (available-tool, called-tool, tool-call) added to session table Pull request #17884
- Dashboard widget deletion returns 404 for missing resources Pull request #17673
- API key mutation returns 404 for missing keys Pull request #17677
- Model and LLM-connection deletion returns 404 for missing resources Pull request #17672
- Error toasts show tRPC Error ID with copy button and include it in issue reports Pull request #17427
- Metadata on traces, observations, and scores typed as objects in read schemas Pull request #18122
- Avatar tooltips display view owner name and email on hover Pull request #18032
- V4.49.0 released with org-level ingestion overview and analytics view Release
V4.50.0 is out. Added decision-model evaluators, seven-day execution health tracking, facet types, and fixed a dozen 500→404 error responses. Error IDs now visible in toasts.
V4.50.0 released. New evaluation features include decision-model evaluators, seven-day execution health tracking, facet types, and rule idle time configuration. On the API side, a dozen endpoints now correctly return 404 for missing resources instead of 500 errors. Error IDs are now visible in tRPC error toasts and included in issue reports. Tool filters added to session tables.
Week of September 21, 2026
What shipped
- V4.46.0 released with experiment comparison improvements, dataset formatting, skill management, and larger page size options. Release
- Experiment side-by-side comparison now defaults to one column per experiment with collapsible summary and shared score details. Pull request #17929
- Basic skill management endpoints added to the REST API for creating, reading, and updating skills. Pull request #17803
- Dataset items now render formatted JSON in code editors for input, expected output, and metadata fields. Pull request #17932
- Dataset run-items reads routed to read replica for improved performance on v3 API. Pull request #17919
- Dashboard query parameters with large filter values now sent as multipart body to avoid proxy rejections. Pull request #17970
- Decision-model evaluators now correctly link to their scores, fixing empty scores tables. Pull request #17954
- Trace playback feature removed from trace navigation header. Pull request #17927
- Topics traces now render and measure dedicated trace transcripts with fixed sections for facts, tools, and state. Pull request #17925
- Scores list query performance improved by deduplicating events rows via GROUP BY and INNER JOIN. Pull request #17883
Why it matters
This week brings significant UX refinements to experiment comparison and dataset viewing, new skill management capabilities, and multiple performance optimizations for dashboard queries and data retrieval. The changes make core workflows faster and cleaner, with better defaults and improved data presentation throughout the interface.
Changelog entry
- Feat(experiments): streamline side-by-side comparison by defaulting to one column per experiment with collapsible summary Release
- Feat(web): add formatted json display to dataset items for input, output and metadata Release
- Feat(skills): basic skill management via REST endpoints for CRUD operations Release
- Feat(web): add 100-row page size option to tracing tables Release
- Fix(dashboard): send large query params as multipart body to avoid proxy rejections Pull request #17970
- Fix(evals): link decision-model evaluators to their scores by evaluator ID Pull request #17954
- Perf(datasets): route v3 dataset-run-items reads to the read replica Pull request #17919
- Perf(scores): dedup events rows via GROUP BY and INNER JOIN for faster list queries Pull request #17883
- Fix(web): remove trace playback feature and related controls Pull request #17927
- Feat(topics): render and measure dedicated trace transcripts with fixed sections Pull request #17925
- Fix(experiments): hide cost column by default in experiment comparison grid Pull request #17947
- Fix(web): reduce tooltip open delay from 700ms to 300ms app-wide Pull request #17946
- Fix(web): update breadcrumb styling with thinner slashes and smaller chevrons Pull request #17934
V4.46.0 ships cleaner experiment comparisons, formatted dataset JSON views, skill management APIs, and performance improvements across dashboard queries and data retrieval.
V4.46.0 is out. Experiment side-by-side comparisons now feature collapsible summaries and better score details. Dataset items display formatted JSON for easier viewing. New REST endpoints enable skill management. Performance optimizations route dataset queries to read replicas and fix dashboard query parameter handling. Plus UI improvements throughout including faster tooltips and better breadcrumb styling.
Week of September 14, 2026
What shipped
- Thread API now returns conversation history and current turn per thread for better transcript organization. Pull request #17613
- Gateway generation metadata reorganized into consistent namespaces with proper HTTP status prefixes. Pull request #17645
- Every ingestion event now authorized through the policy core for improved access control. Pull request #16715
- Automations can now filter prompt events by label with live label loading in the UI. Pull request #17612
- Trace-level scores moved from tree visualization to the trace header for better visibility. Pull request #17642
- Table rows now clear when switching between saved views, filters, or searches to prevent stale data. Pull request #17692
- JSON viewer restyled with unified table appearance across the application. Pull request #17402
- Trace batch dispatcher now measures pending trace size estimates and reports batch size distributions. Pull request #17586
- Capacity experiment telemetry added for trace batch scaling to track admitted volume and queue snapshots. Pull request #17614
- Web processes publish event-loop delay metrics for CloudWatch autoscaling. Pull request #17632
Why it matters
This week includes structural improvements to core data APIs like threads and gateways, better trace observability with metrics and UI reorganization, and expanded automation capabilities. Infrastructure changes improve event-loop monitoring and batch processing visibility for production deployments.
Changelog entry
- Feat: conversation history and current turn now returned per thread Pull request #17613
- Fix(ai-gateway): reorganized generation metadata into consistent namespaces Pull request #17645
- Feat(auth): all ingestion events authorized through policy core Pull request #16715
- Feat(automations): label filtering added for prompt events in GitHub dispatch and webhooks Pull request #17612
- Fix(web): trace-level scores moved from tree visualization to trace header Pull request #17642
- Fix(table): stale rows cleared when switching filter scope Pull request #17692
- Fix(web): JSON viewer restyled with unified table appearance Pull request #17402
- Feat(web): event-loop delay metrics published for CloudWatch autoscaling Pull request #17632
- Feat(trace-batching): pending trace size estimates measured and reported Pull request #17586
- Fix(logging): severity field added to JSON logs for GCP Cloud Logging compatibility Pull request #17606
This week: thread transcripts with conversation history, gateway metadata reorganization, label-based prompt automation filters, and improved trace-level visibility. Full details at the preview links.
This week's releases focus on better data organization and observability. Threads now return full conversation history per turn, gateway generation metadata is consistently namespaced, and automations support label-based filtering. Infrastructure improvements include event-loop delay metrics for autoscaling and batch processing visibility. Check the preview links for details.