pins
pins keeps adding a storage backend per release while retiring its original API
A side-by-side editorial comparison of dbt Core and tsibble — release velocity, themes, recent moves, and the top alternatives to consider.
dbt keeps three maintenance branches alive while Fusion 2.0 crosses into beta.
dbt-core is running two lines at once: a Python 1.x maintenance train across 1.10, 1.11 and 1.12, and the Rust Fusion 2.0 rewrite now in its first beta. The August 12 batch pushed the same deprecated-version warning into all three maintenance branches on one day, with the substantive work isolated to 1.12.1 (OpenTelemetry spans for node and hook execution) and 1.11.13 (deterministic unit-test resolution). Fusion is where the capability surface is actually widening.
tsibble shipped one release in five and a half years - the data structure is finished
tsibble defines the tidy time-series data structure that fable and feasts are built on. The design churned heavily through 2018 and 2019, settled with the 0.9.0 move onto vctrs in mid-2020, and then went quiet: the next release, 1.2.0, arrived in February 2026 with a summary() method and some tidyselect helpers.
dbt-core is running two lines at once: a Python 1.x maintenance train across 1.10, 1.11 and 1.12, and the Rust Fusion 2.0 rewrite now in its first beta. The August 12 batch pushed the same deprecated-version warning into all three maintenance branches on one day, with the substantive work isolated to 1.12.1 (OpenTelemetry spans for node and hook execution) and 1.11.13 (deterministic unit-test resolution). Fusion is where the capability surface is actually widening.
The 1.x branches are converging on housekeeping — deprecation warnings, jsonschema definitions synced down from Fusion, parse-order determinism, adapter config recognition. That is the signature of a codebase being held stable rather than extended. Fusion 2.0 is absorbing the new work: catalog-free binding, a lint rule engine, node selection for lint and format, a self-hostable docs server.
Expect the maintenance branches to keep taking cross-branch warnings and adapter-config fixes while Fusion moves through further betas. The OpenTelemetry work in 1.12.1 is flag-gated behind --snowflake-projects-otel, which suggests tracing arrives unflagged in a later release.
tsibble defines the tidy time-series data structure that fable and feasts are built on. The design churned heavily through 2018 and 2019, settled with the 0.9.0 move onto vctrs in mid-2020, and then went quiet: the next release, 1.2.0, arrived in February 2026 with a summary() method and some tidyselect helpers.
This is a package that reached its final shape and stopped. The early releases are a rapid sequence of breaking changes to the key and interval metadata, each one warning that previously stored objects are corrupt; once the interval became a formal vctrs record type there was nothing structural left to change. The five-year gap is the trajectory, not a lapse.
Expect further releases to be small compatibility and convenience additions at long intervals; with the type system settled and windowing delegated to slider, there is no visible pressure for another breaking change.
Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either dbt Core or tsibble.
pins keeps adding a storage backend per release while retiring its original API
yardstick made fairness metrics a first-class part of tidymodels evaluation
tune extends tuning past the model itself to postprocessors, and adds a second parallel backend
leaflet relicensed to MIT and finished migrating off R's retired spatial stack
ggpubr reached 1.0.0 with p-value formatting presets for specific journals
bigrquery went MIT, then handed its slowest path to the BigQuery Storage API
See all dbt Core alternatives → · See all tsibble alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. dbt Core is currently shipping more aggressively (velocity 7.5 vs 0.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dbt Core is currently shipping more aggressively (velocity 7.5 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top dbt Core alternatives in Analytics are ranked by recent ship velocity. Browse the "dbt Core alternatives" section above for the current picks, or visit /alternatives/dbt-core for the full list with editorial commentary on each.
Top tsibble alternatives in Analytics are ranked by recent ship velocity. Browse the "tsibble alternatives" section above for the current picks, or visit /alternatives/tsibble for the full list with editorial commentary on each.