update changelog

CHANGELOG.md

@@ -2,6 +2,7 @@
 [PR #54](https://github.com/fivetran/dbt_linkedin_source/pull/54) includes the following updates:
 
 ## Breaking changes
+- Updated materializations of non-`tmp` staging models from views to tables. This is to bring the materializations into alignment with other ad reporting packages and eliminate errors in Redshift. 
 - Updated the name of the source created by this package from `linkedin` to `linkedin_ads`. This was to bring the naming used in this package in alignment with our other ad packages and for compatibility with the union schema feature.
   - ❗ If you are using this source, you will need to update the name.
 - Updated the following identifiers for consistency with the source name and compatibility with the union schema feature:
@@ -24,7 +25,6 @@
 - 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 model and applied the `fivetran_utils.source_relation` macro.
 - Updated tests to account for the new `source_relation` column.
-- Updated materializations of staging models from views to tables. Tmp models will still be views. This is brings the materializations into alignment with other ad reporting packages and eliminates errors in Redshift. 
 
 [PR #51](https://github.com/fivetran/dbt_linkedin_source/pull/51) includes the following updates:
 - Incorporated the new `fivetran_utils.drop_schemas_automation` macro into the end of each Buildkite integration test job.