Merge branch 'release/v0.21.0' into bugfix/ticket-pipeline-id-casting

Author: fivetran-avinash

.github/workflows/auto-release.yml

@@ -11,4 +11,4 @@ jobs:
       (github.event.pull_request.merged == true && github.event.pull_request.base.ref == 'main') ||
       github.event.label.name == 'pre-release'
     uses: fivetran/dbt_package_automations/.github/workflows/auto-release.yml@main
-    secrets: inherit
+    secrets: inherit

.gitignore

@@ -69,5 +69,5 @@ service-account.json
 ENV/
 env/
 env.bak/
-venv/
-venv.bak/
+venv/ 
+venv.bak/ 

CHANGELOG.md

@@ -1,4 +1,4 @@
-# dbt_hubspot_source v0.21.0
+# dbt_hubspot_source v0.21.0 
 This release includes the following updates: 
 
 ## Schema Changes 
@@ -24,6 +24,7 @@ This release includes the following updates:
 - Refreshed README tag block [PR #147](https://github.com/fivetran/dbt_hubspot_source/pull/147):
   - Left-aligned and positioned below the H1 title. 
 - Updated `.gitignore` to exclude additional DBT, Python, and system artifacts. [PR #147](https://github.com/fivetran/dbt_hubspot_source/pull/147)
+ 
 
 # dbt_hubspot_source v0.20.0
 

README.md

@@ -10,9 +10,6 @@
         <img src="https://img.shields.io/badge/Maintained%3F-yes-green.svg" /></a>
     <a alt="PRs">
         <img src="https://img.shields.io/badge/Contributions-welcome-blueviolet" /></a>
-    <a alt="Fivetran Quickstart Compatible"
-        href="https://fivetran.com/docs/transformations/dbt/quickstart">
-        <img src="https://img.shields.io/badge/Fivetran_Quickstart_Compatible%3F-yes-green.svg" /></a>
 </p>
 
 ## What does this dbt package do?
@@ -220,11 +217,11 @@ models:
     hubspot_source:
       +schema: my_new_schema_name # leave blank for just the target_schema
 ```
-    
+
 #### Change the source table references
 If an individual source table has a different name than the package expects, add the table name as it appears in your destination to the respective variable:
 > IMPORTANT: See this project's [`dbt_project.yml`](https://github.com/fivetran/dbt_hubspot_source/blob/main/dbt_project.yml) variable declarations to see the expected names.
-    
+
 ```yml
 vars:
     hubspot_<default_source_table_name>_identifier: your_table_name 
@@ -246,7 +243,7 @@ packages:
     - package: dbt-labs/spark_utils
       version: [">=0.3.0", "<0.4.0"]
 ```
-          
+
 ## How is this package maintained and can I contribute?
 ### Package Maintenance
 The Fivetran team maintaining this package _only_ maintains the latest version of the package. We highly recommend that you stay consistent with the [latest version](https://hub.getdbt.com/fivetran/hubspot_source/latest/) of the package and refer to the [CHANGELOG](https://github.com/fivetran/dbt_hubspot_source/blob/main/CHANGELOG.md) and release notes for more information on changes across versions.

docs/catalog.json

@@ -255,5 +255,5 @@ dispatch:
     search_order: ['spark_utils', 'dbt_utils']
 
 flags:
-  send_anonymous_usage_stats: False
-  use_colors: True
+  send_anonymous_usage_stats: False 
+  use_colors: True 

docs/manifest.json

@@ -448,11 +448,11 @@ sources:
             description: Whether the pipeline stage is currently in use.
           - name: closed_won
             description: >
-              Boolean indicating if the pipeline stage is closed.
+              Boolean indicating if the pipeline stage is closed. 
               
               NOTE: This field is deprecated in favor of the `is_closed` column.
           - name: is_closed
-            description: Boolean indicating if the pipeline stage is closed.          
+            description: Boolean indicating if the pipeline stage is closed.      
           - name: display_order
             description: Used to determine the order in which the stages appear when viewed in HubSpot.
           - name: label

integration_tests/dbt_project.yml

@@ -20,7 +20,7 @@ models:
         description: Used to determine the order in which the stages appear when viewed in HubSpot.
       - name: is_active
         description: Whether the pipeline stage is currently in use.
-      - name: is_closed
+      - name: is_closed 
         description: Boolean indicating if the pipeline stage is closed. For the state of the closed deal ("Closed Won" vs "Closed Lost"), refer to the pipeline_stage_label column.      
       - name: pipeline_stage_label
         description: The human-readable label for the stage. The label is used when showing the stage in HubSpot.