You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Sling v1.5.15 (2026-04-15T22:44:09Z)
New Features
CDC support for PostgreSQL, SQL Server, Oracle, and MongoDB: Change Data Capture now works with PostgreSQL (logical replication), SQL Server, Oracle, and MongoDB sources — previously only MySQL was supported.
CDC initial snapshot cursor-based resume: Initial CDC snapshots now use keyset-based chunking for string/UUID primary keys, enabling reliable cursor-based resume after interruption.
CDC catch-up mode with end position: CDC ReadChanges now captures the current position before streaming so catch-up runs terminate without waiting for new events.
Default adjust_column_type for CDC: CDC replications now default adjust_column_type to true, automatically widening target columns (varchar length, decimal precision) when the source schema changes.
adjust_column_type precision expansion: The adjust_column_type option now detects and expands varchar length and decimal precision/scale when the source columns grow wider, avoiding truncation or precision loss.
description parameter for SQL query actions: MCP database.query and worksheet logging now accept an optional description field for improved context and observability.
MCP worksheet query logging: MCP SQL queries are now appended to a worksheet log file with metadata (connection, description, timestamp, duration, columns, row count), with automatic size trimming.
Bug Fixes
Oracle SID/service_name conflict: Fixed Oracle connection strings where the SID option could conflict with service_name, causing connection failures.
Progress update crash when replication is nil: Fixed a panic when updating task progress on a task with no associated replication.
API spec record limit not stopping iteration: Fixed an issue where the API spec record limit was not properly stopping inner iteration loops during rule evaluation.