Release Notes
August 2026
v1.4.1
Feature Updates
- Adds DuckDB as a supported destination.
June 2026
v1.4.0
Under the Hood
- Migrates the
union_connections,apply_source_relation, andpartition_by_source_relationmacros to thedbt_fivetran_utilspackage. - Adds the
fivetran_using_source_casingvariable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.
March 2026
v1.3.3
Documentation
- Updates
user_idcolumn descriptions instg_amplitude,amplitude_event_enhanced, andamplitude_session_enhancedfor clarity and conciseness. - Updates the README to remove badge images and add dbt Core™ supported version information in plain text.
Under the Hood
- Adds
persist_docsconfiguration tointegration_tests/dbt_project.ymlto validate column-level documentation persistence.
February 2026
v1.3.2
Under the Hood
- Prepends
materializedconfigs in thedbt_project.ymlwith a plus sign (+). The plus sign is optional in dbt Core, but required for dbt Fusion.
January 2026
v1.2.0
Features
- Increases the required dbt version upper limit to v3.0.0
v1.3.0
Documentation
- Updates README with standardized Fivetran formatting.
Under the Hood
- In the
quickstart.ymlfile:- Adds
supported_varsfor Quickstart UI customization.
- Adds
v1.3.1
Under the Hood
- Removes the
amplitude__date_range_endvariable from thequickstart.yml. - Adjusts the data type of
amplitude__date_range_startin thequickstart.ymlfrom string to date.
August 2025
v1.0.0
Breaking Changes
Source Package Consolidation
- Removed the dependency on the
fivetran/amplitude_sourcepackage.- All functionality from the source package has been merged into this transformation package for improved maintainability and clarity.
- If you reference
fivetran/amplitude_sourcein yourpackages.yml, you must remove this dependency to avoid conflicts. - Any source overrides referencing the
fivetran/amplitude_sourcepackage will also need to be removed or updated to reference this package. - Update any amplitude_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.
dbt Fusion Compatibility Updates
- 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.
- Moved
loaded_at_field: _fivetran_syncedunder theconfig:block insrc_amplitude.yml.
Under the Hood
- Updated conditions in
.github/workflows/auto-release.yml. - Added
.github/workflows/generate-docs.yml.