Materialize int_zendesk__commenter_reply_at ephemerally (#203)

* Stage changes

* polish

* Docs

* add using_ticket_schedules (#195)

* add using_ticket_schedules

* pr template

* make pre-release

* Ready for normal release

* polishes

* Catherine feedback

* packages.yml

Author: fivetran-jamie

.quickstart/quickstart.yml

@@ -10,6 +10,8 @@ table_variables:
     - daylight_time
     - schedule
     - time_zone
+  using_ticket_schedules:
+    - ticket_schedule
   using_domain_names:
     - domain_name
   using_user_tags:

CHANGELOG.md

@@ -1,3 +1,18 @@
+# dbt_zendesk v0.24.2
+
+This release includes the following updates:
+
+## Schema/Data Changes
+
+**2 total changes • 0 possible breaking changes**
+| **Data Model** | **Change type** | **Old** | **New** | **Notes** |
+| -------------- | --------------- | ------------ | ------------ | --------- |
+| [`int_zendesk__commenter_reply_at`](https://fivetran.github.io/dbt_zendesk/#!/model/model.zendesk.int_zendesk__commenter_reply_at) | Materialization | View | Ephemeral | This intermediate model is now ephemeral, meaning the view will no longer be updated in the warehouse. While the view will still exist in the warehouse, it will become outdated. We therefore recommend manually dropping the `int_zendesk__commenter_reply_at` view. ([PR #203](https://github.com/fivetran/dbt_zendesk/pull/203)) |
+| [`stg_zendesk__ticket_chat_event`](https://fivetran.github.io/dbt_zendesk/#!/model/model.zendesk_source.stg_zendesk__ticket_chat_event) | Filter |  |  |  Excludes `ticket_chat_event` records where the `actor_id` is `__trigger` or `__system` (instead of the expected `######` or `agent:######` formats). This was done to avoid data-casting errors and maintain downstream joins and comment metrics. ([Source PR #72](https://github.com/fivetran/dbt_zendesk_source/pull/72)) |
+
+## Under the Hood
+- Added a system-facing `using_ticket_schedules` variable to the `quickstart.yml` to better support Quickstart. This variable is not available for use otherwise. ([PR #195](https://github.com/fivetran/dbt_zendesk/pull/195))
+
 # dbt_zendesk v0.24.1
 
 This release includes the following updates:
@@ -38,6 +53,13 @@ If you are using dbt Core < 1.9.6 and want to continue running Zendesk freshness
 ## Under the Hood
 - Updates to ensure integration tests use latest version of dbt.
 
+# dbt_zendesk v0.23.1-a1
+
+[PR #195](https://github.com/fivetran/dbt_zendesk/pull/195) includes the following update:
+
+## Under the Hood
+- Added a system-facing `using_ticket_schedules` variable to the `quickstart.yml` to better support Quickstart. This variable is not available for use otherwise.
+
 # dbt_zendesk v0.23.0
 [PR #193](https://github.com/fivetran/dbt_zendesk/pull/193) includes the following updates from pre-release `v0.23.0-a1`:
 

dbt_project.yml

@@ -1,5 +1,5 @@
 name: 'zendesk'
-version: '0.24.1'
+version: '0.24.2'
 
 config-version: 2
 require-dbt-version: [">=1.3.0", "<2.0.0"]
@@ -24,8 +24,9 @@ models:
     sla_policy:
       +schema: zendesk_intermediate
       +materialized: table
-      int_zendesk__commenter_reply_at:
-        +materialized: ephemeral
+      reply_time:
+        int_zendesk__commenter_reply_at:
+          +materialized: ephemeral
     ticket_history:
       +schema: zendesk_intermediate
       +materialized: ephemeral

docs/catalog.json

@@ -1,7 +1,7 @@
 config-version: 2
 
 name: 'zendesk_integration_tests'
-version: '0.24.1'
+version: '0.24.2'
 
 profile: 'integration_tests'
 

docs/manifest.json

@@ -1,3 +1,3 @@
 packages:
 - package: fivetran/zendesk_source
-  version: [">=0.18.0", "<0.19.0"]
+  version: [">=0.18.0", "<0.19.0"]