What jitsucom/jitsu shipped
Written by FoxPlug from the repository's own releases; not affiliated with Jitsu. 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/jitsucom/jitsu; Jitsu 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
- Custom domains and identity stitching are now plan entitlements, with custom domains for Business and Enterprise and identity stitching for Enterprise only. Pull request #1529
- Meta Ads reverse ETL was added for audiences and conversions, keeping the facebook-conversions ID and existing valid event behavior. Pull request #1535
- NEXTAUTH_URL is now derived from JITSU_PUBLIC_URL when it is unset, so self-hosted deployments without a Firebase fallback can resolve sessions. Pull request #1560
- GitHub OAuth callback failures now log the underlying HTTP response instead of a generic error. Pull request #1564
- Retained reverse ETL recovery rows can be kept in a retention bucket, dormant until a run configuration carries the new optional retention field. Pull request #1552
- Webhook syncs name their retention bucket and refuse a retention of zero. Pull request #1553
- Long reverse ETL webhook runs reuse connections and keep the system error code behind
connection_errorwhile user-facing reason codes stay unchanged. Pull request #1555 - Meta reverse ETL gained ad-account and customer-list audience pickers, a read-only connection check and automatic target preflight before saving. Pull request #1559
- Unresolved deliveries stay pending with status checks refreshed for 48 hours, slowing to every two hours after the first day, and can be manually refreshed. Pull request #1557
- The first-run managed Google audience snapshot is validated before saving creation intent or calling Google. Pull request #1558
Why it matters
This week brought a large set of reverse ETL changes across Meta, Google and a webhook destination, plus retention and error reporting work. It also made plan entitlements visible for custom domains and identity stitching, and fixed self-hosted session resolution by deriving the NextAuth URL. For people running the project, the delivery paths are more predictable and failed runs are easier to explain.
Changelog entry
- Custom domains are gated to Business and Enterprise plans, and identity stitching to Enterprise. Pull request #1529
- Meta Ads (Facebook & Instagram) reverse ETL supports creating Custom Audiences and conversions. Pull request #1535
- NEXTAUTH_URL is derived from JITSU_PUBLIC_URL when unset. Pull request #1560
- GitHub OAuth callback failures log the underlying HTTP response. Pull request #1564
- Per-connection prebuilt function-chain messages are logged at debug level instead of info. Pull request #1563
- Meta reverse ETL adds ad-account and customer-list audience pickers, a read-only connection check and automatic preflight before saving. Pull request #1559
- Meta reverse ETL run logs show a current-results panel with audience size, eligibility and estimated match range. Pull request #1562
- The complete first-run managed Google audience snapshot is validated before saving creation intent or calling Google. Pull request #1558
- Unresolved deliveries stay pending with checks for 48 hours, slowing to every two hours after the first day, with a manual refresh action. Pull request #1557
- Google reverse ETL diagnostics distinguish explicit rejection from uncertain delivery and record lease-admission failures. Pull request #1556
- Webhook reverse ETL reuses connections and keeps the system error code behind
connection_error. Pull request #1555 - Webhook syncs name their retention bucket and refuse retention of zero. Pull request #1553
Reverse ETL updates: Meta Ads audiences and conversions, Google snapshot validation, webhook destinations with a retention bucket, and 48-hour pending status. Custom domains and identity stitching are now plan entitlements. NEXTAUTH_URL is derived from JITSU_PUBLIC_URL when unset
Reverse ETL saw a lot of work this week. Meta Ads audiences and conversions landed, Google audience creation now validates its first-run snapshot, webhook destinations store retained rows in a retention bucket, connections are reused, and unresolved deliveries stay pending with status refreshed for 48 hours. Meta target pickers and preflight checks reduce bad saves. Custom domains and identity stitching became plan entitlements, and self-hosted installs derive the NextAuth URL from JITSU_PUBLIC_URL when it is unset. GitHub OAuth callback failures also log the underlying HTTP response.
Week of September 28, 2026
What shipped
- Sync-sidecar now retries Postgres operations instead of panicking when the primary goes down during replica promotion. Pull request #1527
- Fixed a connection-pool leak in the shared fetch wrapper by pinning undici to >=8.11.0. Pull request #1541
- Functions-server now has a StartupProbe to prevent CrashLoopBackOff during container startup. Pull request #1528
- Updated deepmerge-ts to 8.0.2 to fix a high-severity vulnerability. Pull request #1539
- Fixed sync-service integration test that was failing due to
task_logfixture timing. Pull request #1543 - Released Jitsu 2.15.0-beta.69. Release
- Released Jitsu 2.15.0-beta.68. Release
Why it matters
This week focused on stability improvements across the platform. Better Postgres failover handling and container startup probes reduce production incidents, while the fetch connection-pool fix prevents resource exhaustion in high-volume environments. A security vulnerability was also patched.
Changelog entry
- Fix(sync-sidecar): Postgres operations now retry instead of panicking during replica promotion Pull request #1527
- Fix(functions): undici pinned to >=8.11.0 to fix connection-pool leak in shared fetch wrapper Pull request #1541
- Fix(operator): functions-server now has a StartupProbe to prevent CrashLoopBackOff Pull request #1528
- Fix(security): deepmerge-ts updated to 8.0.2 to address CVE-2026-40345 Pull request #1539
- Fix(tests): sync-service
task_logfixture now stamped relative to current time Pull request #1543
This week: Postgres failover resilience, connection-pool leak fixed, faster function-server startup, and a security update. Two beta releases shipped.
Jitsu shipped stability improvements this week: the sync-sidecar now handles Postgres failovers gracefully, a connection-pool leak in destination functions is fixed, and functions-server startup is more reliable with a new probe. A high-severity dependency vulnerability was also patched. Two beta releases went out.
Week of September 21, 2026
What shipped
- BigQuery warehouse reader and GoogleSQL dialect added to Models and Reverse ETL, supporting dry-run column inspection and paginated extraction. Pull request #1534
- Jitsu-provisioned ClickHouse now supported in Models and Reverse ETL with normalized HTTPS endpoints. Pull request #1533
- Reverse ETL console workflow implemented with full-page model editor, Monaco SQL support, and run management interface. Pull request #1525
- Reverse ETL run loading, OAuth binding fixed and full-mirror cleanup visibility added to delivery statistics. Pull request #1530
- Google Ads Developer Token field now hidden when shared token is configured; model diagnostics improved with credential redaction. Pull request #1532
- Object-backed Reverse ETL persistence layer implemented for runner deployment. Pull request #1526
- Environment endpoints removed; internal billing requests now routed through server-held credentials. Pull request #1500
- Console unit-test timeout centralized to 30 seconds across all tests. Pull request #1531
Why it matters
Reverse ETL is now production-ready with support for BigQuery and ClickHouse warehouses, a complete console UI for model creation and run management, and improved diagnostics. The week focused on warehouse compatibility and fixing critical functionality for data activation workflows.
Changelog entry
- BigQuery warehouse reader and GoogleSQL dialect for Models and Reverse ETL with dry-run inspection and paginated extraction Pull request #1534
- Jitsu-provisioned ClickHouse support in Models and Reverse ETL with normalized HTTPS endpoints Pull request #1533
- Reverse ETL console setup with full-page model editor, Monaco SQL, preview, extraction and primary-key settings Pull request #1525
- Full-mirror cleanup visibility in Record delivery statistics with status tracking and upload record distinction Pull request #1530
- Google Ads Developer Token visibility controlled by shared configuration; actionable model diagnostics with credential redaction Pull request #1532
- Object-backed Reverse ETL persistence layer for runner deployment Pull request #1526
- Environment endpoints removed; internal billing requests routed through server credentials Pull request #1500
Reverse ETL now supports BigQuery and ClickHouse. Full console UI for model editor, extraction settings, and run management shipped this week in 2.15.0 beta releases.
Reverse ETL progress: added BigQuery and ClickHouse warehouse support, shipped the complete console UI with model editor (Monaco SQL, preview, extraction settings), improved run management and diagnostics. Full-mirror cleanup visibility and OAuth binding fixes also included across beta 63-67.
Week of September 14, 2026
What shipped
- Jitsu 2.15.0-beta.62 released. Release
- Google managed audiences and snapshot membership refresh added to Data Manager adapter. Pull request #1524
- Google Data Manager adapter with scoped OAuth and independent provider recovery implemented. Pull request #1523
- Asynchronous Reverse ETL batches now supported with journal staging and reconciliation. Pull request #1522
- Reverse ETL executable Node runner and syncctl/CronJob integration added. Pull request #1521
- Zstd compression support added for S3/GCS destinations and internal batch paths. Pull request #1508
- Bulker test container pinned to quay registry to fix CI failures. Pull request #1520
Why it matters
The week focused on Reverse ETL infrastructure for Google Ads Customer Match destinations, with multiple PRs building the persistence layer, orchestration, and provider adapters. Compression improvements via klauspost/gzip and zstd provide performance options across ingest and warehouse paths.
Changelog entry
- Google managed audiences and snapshot membership refresh in Data Manager adapter Pull request #1524
- Google Data Manager adapter with scoped OAuth and independent provider recovery Pull request #1523
- Asynchronous Reverse ETL batch support with journal staging and reconciliation Pull request #1522
- Reverse ETL Node runner and syncctl/CronJob integration Pull request #1521
- Zstd compression for S3/GCS destinations and internal batch paths Pull request #1508
- Fixed Bulker test container registry to quay Pull request #1520
2.15.0-beta.62 ships Reverse ETL core for Google Ads, async batch delivery, and compression upgrades across S3/GCS and warehouse paths.
2.15.0-beta.62 brings Reverse ETL infrastructure for Google Ads Customer Match destinations, including async batch processing with journal staging and reconciliation. Compression improvements deliver klauspost/gzip on ingest paths and zstd support for S3/GCS and warehouse batches.