v0.9.1 dbt_github_source

PR #45 includes the following updates:

Feature Updates

• Added the following variables to account for potentially missing tables. For dbt Core users, each is True by default and will need to be set to False in the root project's dbt_project.yml. For Fivetran Quickstart users, they will be dynamically enabled/disabled based on the presence of the associated source table.
  • github__using_issue_assignee: Disable if missing ISSUE_ASSIGNEE
  • github__using_issue_label: Disable if missing ISSUE_LABEL
  • github__using_label: Disable if missing LABEL
  • github__using_requested_reviewer_history: Disable if missing REQUESTED_REVIEWER_HISTORY

Under the Hood

• Updated package maintainer PR template.

Full Changelog: v0.9.0...v0.9.1

v0.9.0 dbt_github_source

PR #44 includes the following updates:

Breaking Change for dbt Core < 1.9.6

Note: This is not relevant to Fivetran Quickstart users.

Migrated freshness from a top-level source property to a source config in alignment with recent updates from dbt Core. This will resolve the following deprecation warning that users running dbt >= 1.9.6 may have received:

[WARNING]: Deprecated functionality
Found `freshness` as a top-level property of `github` in file
`models/src_github.yml`. The `freshness` top-level property should be moved
into the `config` of `github`.

IMPORTANT: Users running dbt Core < 1.9.6 will not be able to utilize freshness tests in this release or any subsequent releases, as older versions of dbt will not recognize freshness as a source config and therefore not run the tests.

If you are using dbt Core < 1.9.6 and want to continue running Github Source freshness tests, please elect one of the following options:

1. (Recommended) Upgrade to dbt Core >= 1.9.6
2. Do not upgrade your installed version of the github_source package. Pin your dependency on v0.8.0 in your packages.yml file.
3. Utilize a dbt override to overwrite the package's github source and apply freshness via the previous release top-level property route. This will require you to copy and paste the entirety of the previous release src_github.yml file and add an overrides: github_source property.

Documentation

• Corrected references to connectors and connections in the README. (#42)

Under the Hood

• Updates to ensure integration tests use latest version of dbt.

Full Changelog: v0.8.0...v0.9.0

v0.8.0 dbt_github_source

PR #39 contains the following updates:

🚨 Breaking Change 🚨

• For consistency with other Fivetran packages, added default target schemas in dbt_project.yml. This is a breaking change since the model outputs will now be stored in a schema called <your target schema>_github_source by default. You will need to update any of your downstream use cases to point to the new schema.
  • Refer to the Change the Build Schema section of the README for instructions on how to adjust the output schema.

Feature updates

• Added field created_at to model stg_github__issue_comment.
• Updated the source freshness test enablement/disablement to leverage the dbt-core config: enabled architecture.

Contributors

• @rajan-lw (PR #33)

Full Changelog: v0.7.1...v0.8.0

v0.7.1 dbt_github_source

Fixes

• Updated src_github.yml to capitalize Fivetran in the loader definition, to mirror use in other Fivetran packages. (PR #37)

Under the Hood

• Incorporated the new fivetran_utils.drop_schemas_automation macro into the end of each Buildkite integration test job. (PR #34)
• Updated the pull request templates. (PR #34)

Contributors

• @raphaelvarieras (PR #37)

Full Changelog: v0.7.0...v0.7.1

v0.7.0 dbt_github_source

Hope you're having a good day! This release of the dbt_github_source package includes the following updates:

🚨 Breaking Change 🚨

• Expanded the variable github__using_repo_team to also toggle on/off the TEAM table along with and in addition to the REPO_TEAM table. This was done to fix issues with dependent models in our transform package, where TEAM is only ever used in conjunction with REPO_TEAM. (#32)

🎉 Features 🎉

• PostgreSQL compatibility! (#32)

Full Changelog: v0.6.0...v0.7.0

dbt_github_source v0.6.0

PR #26 includes the following breaking changes:

🚨 Breaking Changes 🚨:

• Dispatch update for dbt-utils to dbt-core cross-db macros migration. Specifically {{ dbt_utils.<macro> }} have been updated to {{ dbt.<macro> }} for the below macros:
  • any_value
  • bool_or
  • cast_bool_to_text
  • concat
  • date_trunc
  • dateadd
  • datediff
  • escape_single_quotes
  • except
  • hash
  • intersect
  • last_day
  • length
  • listagg
  • position
  • replace
  • right
  • safe_cast
  • split_part
  • string_literal
  • type_bigint
  • type_float
  • type_int
  • type_numeric
  • type_string
  • type_timestamp
  • array_append
  • array_concat
  • array_construct
• For current_timestamp and current_timestamp_in_utc macros, the dispatch AND the macro names have been updated to the below, respectively:
  • dbt.current_timestamp_backcompat
  • dbt.current_timestamp_in_utc_backcompat
• Dependencies on fivetran/fivetran_utils have been upgraded, previously [">=0.3.0", "<0.4.0"] now [">=0.4.0", "<0.5.0"].

🎉 Documentation and Feature Updates 🎉:

• Updated README documentation for easier navigation and dbt package setup #26.
• Included the github_[source_table_name]_identifier variables for easier flexibility of the package models to refer to differently named sources tables #26.
• Added Databricks compatibility #29.

dbt_github_source 0.5.0

Happy Thursday!

This release of the dbt_github_source package includes the following updates:

🚨 Breaking Changes 🚨

• Addition of the label source table. This was necessary as the issue_label depreciated the label column. The respective label information will now be synced within the label table. (#22)
  • If you do not have the new label table in your source, we highly recommend you enable schema changes on your connector and kick off a resync to see the new tables reflected in your source.

dbt_github_source 0.4.1

Happy Tuesday!

This release of the dbt_github_source package includes the following updates:

Fixes

• Added the {{ dbt_utils.type_timestamp() }} cast function to timestamp fields within the staging models. This is required for Redshift users that have the fields originally synced as timestamptz. Without the casting of fields the downstream date functions will fail. (#19)

dbt_github_source 0.4.0

🎉 dbt v1.0.0 Compatibility 🎉

🚨 Breaking Changes 🚨

• Adjusts the require-dbt-version to now be within the range [">=1.0.0", "<2.0.0"]. Additionally, the package has been updated for dbt v1.0.0 compatibility. If you are using a dbt version <1.0.0, you will need to upgrade in order to leverage the latest version of the package.
  • For help upgrading your package, I recommend reviewing this GitHub repo's Release Notes on what changes have been implemented since your last upgrade.
  • For help upgrading your dbt project to dbt v1.0.0, I recommend reviewing dbt-labs upgrading to 1.0.0 docs for more details on what changes must be made.
• Upgrades the package dependency to refer to the latest dbt_fivetran_utils. The latest dbt_fivetran_utils package also has a dependency on dbt_utils [">=0.8.0", "<0.9.0"].
  • Please note, if you are installing a version of dbt_utils in your packages.yml that is not in the range above then you will encounter a package dependency error.

dbt 0.20.0 Compatibility

🎉 dbt 0.20.0 Compatibility 🎉

🚨 This is a breaking change! 🚨 dbt v0.20.0 or greater is required for this release. If you are not ready to upgrade, consider using a previous release of this package.

Additional considerations when upgrading to this package:

• This package utilizes the latest v0.7.x release of the dbt-labls/dbt_utils package. If your project also utilizes a version of the fishtown-analytics/dbt_utils package then you will receive a duplicate package error. If this is the case you will need to consider upgrading your other packages to be compatible with this update or use a previous release of this package.
• Similar to the above point, all previous Fivetran dbt packages utilize the fishtown-analytics/dbt_utils package and you will need to upgrade all Fivetran dbt packages to the latest dbt 0.20.0 compatibility releases in order for your packages to run without package conflicts.