Releasesby GlyphEstuary Flow 0.6.5
This release includes support for the upcoming materialization triggers feature, in addition to several other bugfixes and improvements. Fix double-slash in journal list selector breaking collection reads Include flowctl version in publication details Improve error message for concurrent spec modifications Add support for materialization triggers
Also shipped Mar 25, 2026Estuary in March 2026 →
Modal 1.4.0
We've made significant CLI enhancements so that Modal logs can be more accessible to coding agents: The modal app logs and modal container logs commands now have the ability to fetch historical logs using counting (e.g. --tail 1000) or time-based (e.g., --since 4h, --until 2026-03-15, etc.) configuration.
Attribution Alerts
Set alerts scoped to specific teams, services, environments, and more using cost attribution labels We’re excited to announce the general availability of Attribution Alerts in the Cost Management and Billing app!
The Shopify CLI app release `--force` flag is deprecated and will be removed
We are deprecating the --force flag on the shopify app deploy and shopify app release commands. The flag will be removed in a Shopify CLI release in May 2026. Why we're making this change The --force flag skips all confirmation prompts, including for extension deletions that can permanently remove data on installed shops.
New Filters for List Session Replays
What it is: Two new filters are now available on the List Session Replays API endpoint. 'amplitude_id' (integer) returns replays tied to a specific Amplitude user ID. 'replay_id' accepts up to 100 IDs in 'device_id/session_id' format and fetches those sessions directly, bypassing pagination.
Improvements to Distributions
What it is: Frequency charts, histogram charts, session length, and time-to-convert now support normalization, PDF, and CDF views. Normalization scales each series so its bars sum to 1, making groups with different sample sizes directly comparable , for example, U.S.
More from Estuary FlowEvery Estuary Flow release →
Estuary Flow 0.6.6
This releases the new Target Naming setting on materializations, in addition to a couple of other smaller changes that impact flowctl : models: strip minLength and maxLength from relaxed write schema models,ops: add a task flags mechanism for runtime feature flags Shuffle v2: disk-backed log pipeline with zero-copy combiner pass-through discovers: replace...
Estuary Flow 0.6.4
This release includes some bug fixes to some validation behavior in cases where a key field has a default annotation
Estuary Flow 0.6.7
Fix missing User-Agent on postgrest client, encourage users to upgrade when new flowctl version is available
Estuary Flow 0.6.8
- control-plane: fix silent success of flowctl catalog test when tests fail flowctl: fix false "outdated version" warning
Estuary Flow 6.0.9
- shuffle(slice): require broker observation of journal create_revision data-plane-controller: let vpc exist Reject footguns in redact annotation placement data-plane-controller: periodic converge mise: wasm-bindgen changed repos validation: cascade backfill on collection reset regardless of onIncompatibleSchemaChange docs/source-ga4-bigquery: New connector...
Estuary Flow 0.6.10
- docs/redaction: document hash salting and redactSalt override ops-catalog: materialize stats to Bigtable Docs: Add more missing connector properties docs: add my_domain field for source-salesforce-native docs: add marketing events stream to source-hubspot-native Authz refactor w/ orthogonal capabilities billing: split invoices_ext data view from...
Estuary Flow 0.6.11
- runtime: periodically store primary FSMHints of V2 shards mise build:flowctl for a local flowctl binary go.mod: bump gazette to latest data-plane-controller: dns and s3 passthroughs Self-service private-link configuration supabase: scoped refresh tokens so CI writes via PostgREST instead of direct psql docs: Describe SQL Server replica suport...
Estuary Flow 0.6.12
- docs: surface MCP and agent skills for coding agents dekaf: serve the document containing a mid-document fetch offset runtime: let docker atomically assign published connector host ports runtime-next: discard hinted frontier when committed frontier is rebuilt docs/source-postgres: Sync statement_timeout change Provide capture/materializations created_at...