RStudio
RStudio's first October patch is a branch merge, extending a long run of release-train upkeep.
A side-by-side editorial comparison of dbt Core and Tableau — release velocity, themes, recent moves, and the top alternatives to consider.
dbt's 1.x releases now point users at v2 straight from the command line.
dbt 2.0 GA split the project into a proprietary 'dbt' binary and dbt-oss, and the 2.0 dev channel has since added read-only Databricks Unity Catalog access through Lake Compute. The 1.x line is still shipping: 1.13.0b1 adds an opt-in --use-v2-parser that hands parsing to the Fusion parser, and today's 1.12.6 prints a v2 availability notice on dbt --version and relays Fusion parser logs through the otel log format.
Tableau's feed captures download indexes, so a cadence change is the only real news in it.
The crawled entries are Tableau's release infrastructure rather than release content: a downloads index listing every supported version, two captures of the Desktop and Web Authoring release-notes page whose feature list lives inside an embedded viz, and a stray resources link. The one substantive item is a notice that Tableau has changed its product and maintenance release cadence, published ahead of the download pages.
dbt 2.0 GA split the project into a proprietary 'dbt' binary and dbt-oss, and the 2.0 dev channel has since added read-only Databricks Unity Catalog access through Lake Compute. The 1.x line is still shipping: 1.13.0b1 adds an opt-in --use-v2-parser that hands parsing to the Fusion parser, and today's 1.12.6 prints a v2 availability notice on dbt --version and relays Fusion parser logs through the otel log format.
The 1.x branch is being turned into an on-ramp for v2: a PyPI banner in 1.12.5, a CLI notice in 1.12.6, deprecated-version warnings and the Fusion parser opt-in in 1.13. Meanwhile 2.0 work concentrates on adapter parity (ClickHouse, Databricks) and Lake Compute.
Expect 1.13 to reach GA with the v2 parser opt-in and more migration prompts, and 2.0.x to extend Lake Compute past read-only Unity access. The entries don't show an end-of-life date for 1.x.
The crawled entries are Tableau's release infrastructure rather than release content: a downloads index listing every supported version, two captures of the Desktop and Web Authoring release-notes page whose feature list lives inside an embedded viz, and a stray resources link. The one substantive item is a notice that Tableau has changed its product and maintenance release cadence, published ahead of the download pages.
What is visible is a versioning rhythm, not a product direction: 2026.1 shipped in March 2026 while the 2025.3 and 2025.1 lines continued taking maintenance patches, and 2025.2 moved to limited support. Because the feature list is rendered inside a visualization rather than as text, what actually changed for analysts in each release never reaches the feed.
Maintenance releases on the 2025.x lines will keep appearing alongside the newer 2026.x line, and the cadence change is the item worth watching for how far apart major releases land. The entries give no basis for calling what ships inside those releases.
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 Tableau.
RStudio's first October patch is a branch merge, extending a long run of release-train upkeep.
OpenReplay moves its Go backend to pgx v5 and patches vulnerable deps across 1.25–1.27.
Basedash automations can now attach scheduled CSV exports to Slack and email.
OpenPanel tags three more note-free builds in one evening, reaching 3.16.4.
Fulcrum turns on Insights, its AI assistant for field data, for every customer.
Holistics lets admins put a key dashboard on everyone's Home page.
See all dbt Core alternatives → · See all Tableau 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 6.3 vs 0.0), with 0 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 6.3 vs 0.0), with 0 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 Tableau alternatives in Analytics are ranked by recent ship velocity. Browse the "Tableau alternatives" section above for the current picks, or visit /alternatives/tableau for the full list with editorial commentary on each.