Release Notes
August 2026
v1.5.1
Feature Updates
- Adds DuckDB as a supported destination.
July 2026
v1.5.0
Schema/Data Change
6 total changes • 6 possible breaking changes
| Data Model(s) | Change type | Old | New | Notes |
|---|---|---|---|---|
stg_linkedin_pages__share_historystg_linkedin_pages__ugc_post_historyint_linkedin_pages__latest_post_history | Removed columns | created_actor last_modified_actor | Deprecated by LinkedIn. No replacement. |
June 2026
v1.4.0
Schema/Data Changes (--full-refresh required after upgrading)
1 total change • 1 possible breaking change
| Data Model(s) | Change type | Old | New | Notes |
|---|---|---|---|---|
| All models | source_relation column (when using a single LinkedIn Pages schema) | Empty string ('') | <database>.<schema> |
Feature Updates
- Introduces the new (recommended)
linkedin_pages_sourcesvariable for more robust union data configuration. The oldlinkedin_pages_union_schemasandlinkedin_pages_union_databasesvariables will still be supported. See the README for specific details.
Under the Hood
- 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. - Introduces
fivetran_utils.partition_by_source_relationto conditionally includesource_relationin partition clauses only when multiple sources are configured. - Removed unnecessary
--depends-onconfig withinstg_linkedin_pages__organization_tmp.
February 2026
v1.3.0
Schema/Data Change (--full-refresh required after upgrading)
19 total changes • 13 of which are breaking in the form of materialization updates
| Data Model(s) | Change type | Old | New | Notes |
|---|---|---|---|---|
stg_linkedin_pages__organizationstg_linkedin_pages__organization_ugc_poststg_linkedin_pages__post_contentstg_linkedin_pages__share_statisticstg_linkedin_pages__ugc_post_historystg_linkedin_pages__ugc_post_share_statistic(as well as the upstream tmp models for each model) | Materialization | Table | View | Breaking: These staging models are now views. Upon full refresh, the package will automatically drop the tables and recreate them as views. However, we recommend reviewing your schema and manually dropping any remaining staging models materialized as tables as they will no longer be updated in favor of the materialized views. |
linkedin_pages__posts | Renamed column | ugc_post_id | post_id | Breaking: Column renamed to reflect that the model now includes both UGC posts and shares. |
linkedin_pages__posts | Data expansion | UGC posts only | UGC posts + shares | Model now includes both UGC posts and LinkedIn shares. |
linkedin_pages__posts | Added column | content_type | Indicates whether the post is from 'ugc' (UGC post) or 'share' (LinkedIn share). | |
stg_linkedin_pages__organization_share | New model | Mapping table between organizations and shares. | ||
stg_linkedin_pages__share_content | New model | Content of shares (articles, images, polls, text). | ||
stg_linkedin_pages__share_history | New model | Version history of shares with metadata. | ||
stg_linkedin_pages__share_share_statistic | New model | Mapping between shares and share statistics. |
Under the Hood
- Added seed files for new LinkedIn data sources, as well as designed column types to ensure no data type confusion errors.
- Share URNs are formatted downstream with the
urn:li:share:<id>format to ensure Linkedin URLs properly link to social share posts. - Added consistency test to compare
linkedin_pages__posts.
Documentation Update
- Added new table descriptions and fields for share sources.
January 2026
v1.1.0
Features
- Increases the required dbt version upper limit to v3.0.0.
v1.2.0
Documentation
- Updates README with standardized Fivetran formatting.
Under the Hood
- In the
quickstart.ymlfile:- Adds
table_variablesfor relevant sources to prevent missing sources from blocking downstream Quickstart models. - Adds
supported_varsfor Quickstart UI customization.
- Adds
October 2025
v1.0.1
Bug Fixes
- Removed extra tab spacing within the
src_linkedin_pages.ymlandstg_linkedin_pages.ymlto resolve a potential error when persisting docs.