dbt bump to v3.0.0

.quickstart/quickstart.yml

@@ -1,7 +1,7 @@
 database_key: github_database
 schema_key: github_schema
 
-dbt_versions: ">=1.3.0 <2.0.0"
+dbt_versions: ">=1.3.0 <3.0.0"
 
 table_variables:
   github__using_issue_assignee:

CHANGELOG.md

@@ -1,3 +1,9 @@
+# dbt_github v1.2.0
+[PR #75](https://github.com/fivetran/dbt_github/pull/75) includes the following updates:
+
+## Features  
+- Increases the required dbt version upper limit to v3.0.0.
+
 # dbt_github v1.1.0
 
 ## Schema/Data Change

README.md

@@ -5,7 +5,7 @@
         href="https://github.com/fivetran/dbt_github/blob/main/LICENSE">
         <img src="https://img.shields.io/badge/License-Apache%202.0-blue.svg" /></a>
     <a alt="dbt-core">
-        <img src="https://img.shields.io/badge/dbt_Core™_version->=1.3.0_,<2.0.0-orange.svg" /></a>
+        <img src="https://img.shields.io/badge/dbt_Core™_version->=1.3.0,_<3.0.0-orange.svg" /></a>
     <a alt="Maintained?">
         <img src="https://img.shields.io/badge/Maintained%3F-yes-green.svg" /></a>
     <a alt="PRs">
@@ -60,7 +60,7 @@ Include the following github package version in your `packages.yml` file.
 ```yaml
 packages:
   - package: fivetran/github
-    version: [">=1.1.0", "<1.2.0"] # we recommend using ranges to capture non-breaking changes automatically
+    version: [">=1.2.0", "<1.3.0"] # we recommend using ranges to capture non-breaking changes automatically
 ```
 
 > All required sources and staging models are now bundled into this transformation package. Do not include `fivetran/github_source` in your `packages.yml` since this package has been deprecated.

dbt_project.yml

@@ -1,7 +1,7 @@
 config-version: 2
 name: 'github'
-version: '1.1.0'
-require-dbt-version: [">=1.3.0", "<2.0.0"]
+version: '1.2.0'
+require-dbt-version: [">=1.3.0", "<3.0.0"]
 models:
   github:
     +materialized: table

integration_tests/dbt_project.yml

@@ -1,5 +1,5 @@
 name: 'github_integration_tests'
-version: '1.1.0'
+version: '1.2.0'
 config-version: 2
 profile: 'integration_tests'
 vars: