Release Notes

August 2026

In the quickstart.yml file:
- Adds supported_vars for Quickstart UI customization.

Updated twitter_ads__promoted_tweet_report and twitter_ads__url_report models to source account_id and promoted_tweet_id fields from stg_twitter_ads__promoted_tweet_report rather than from *_history staging models.
- Prevents a failure on not_null test that can occur due to *_history tables hard-deleting entities like promoted tweets, while retaining related records in report tables.

Removed the dependency on the fivetran/twitter_source package.
- All functionality from the source package has been merged into this transformation package for improved maintainability and clarity.
- If you reference fivetran/twitter_source in your packages.yml, you must remove this dependency to avoid conflicts.
- Any source overrides referencing the fivetran/twitter_source package will also need to be removed or updated to reference this package.
- Update any twitter_source-scoped variables to be scoped to only under this package. See the README for how to configure the build schema of staging models.
As part of the consolidation, vars are no longer used to reference staging models, and only sources are represented by vars. Staging models are now referenced directly with ref() in downstream models.

Updated package to maintain compatibility with dbt-core versions both before and after v1.10.6, which introduced a breaking change to multi-argument test syntax (e.g., unique_combination_of_columns).
Temporarily removed unsupported tests to avoid errors and ensure smoother upgrades across different dbt-core versions. These tests will be reintroduced once a safe migration path is available.
- Removed all dbt_utils.unique_combination_of_columns tests.
- Moved loaded_at_field: _fivetran_synced under the config: block in src_twitter.yml.

Unioning capability! This adds the ability to union source data from multiple twitter connectors. Refer to the Union Multiple Connectors README section for more details.

In the source package, updated tmp models to union source data using the fivetran_utils.union_data macro.
To distinguish which source each field comes from, added source_relation column in each staging and downstream model and applied the fivetran_utils.source_relation macro.
- The source_relation column is included in all joins in the transform package.
Updated tests to account for the new source_relation column.

PR #18 includes the following updates:

Incorporated the new fivetran_utils.drop_schemas_automation macro into the end of each Buildkite integration test job.
Updated the pull request templates.