fmt

.bumpversion.cfg

@@ -1,19 +1,13 @@
 [bumpversion]
-current_version = 1.7.0b2
-parse = (?P<major>[\d]+) # major version number
-	\.(?P<minor>[\d]+) # minor version number
-	\.(?P<patch>[\d]+) # patch version number
-	(?P<prerelease>  # optional pre-release - ex: a1, b2, rc25
-	(?P<prekind>a|b|rc) # pre-release type
-	(?P<num>[\d]+) # pre-release version number
+current_version = 0.21.0b2
+parse = (?P<major>\d+)
+	\.(?P<minor>\d+)
+	\.(?P<patch>\d+)
+	((?P<prekind>a|b|rc)
+	(?P<pre>\d+)  # pre-release version num
 	)?
-	( # optional nightly release indicator
-	\.(?P<nightly>dev[0-9]+) # ex: .dev02142023
-	)? # expected matches: `1.15.0`, `1.5.0a11`, `1.5.0a1.dev123`, `1.5.0.dev123457`, expected failures: `1`, `1.5`, `1.5.2-a1`, `text1.5.0`
-serialize =
-	{major}.{minor}.{patch}{prekind}{num}.{nightly}
-	{major}.{minor}.{patch}.{nightly}
-	{major}.{minor}.{patch}{prekind}{num}
+serialize = 
+	{major}.{minor}.{patch}{prekind}{pre}
 	{major}.{minor}.{patch}
 commit = False
 tag = False
@@ -21,27 +15,36 @@ tag = False
 [bumpversion:part:prekind]
 first_value = a
 optional_value = final
-values =
+values = 
 	a
 	b
 	rc
 	final
 
-[bumpversion:part:num]
+[bumpversion:part:pre]
 first_value = 1
 
-[bumpversion:part:nightly]
+[bumpversion:file:setup.py]
 
 [bumpversion:file:core/setup.py]
 
 [bumpversion:file:core/dbt/version.py]
 
+[bumpversion:file:core/scripts/create_adapter_plugins.py]
+
 [bumpversion:file:plugins/postgres/setup.py]
 
+[bumpversion:file:plugins/redshift/setup.py]
+
+[bumpversion:file:plugins/snowflake/setup.py]
+
+[bumpversion:file:plugins/bigquery/setup.py]
+
 [bumpversion:file:plugins/postgres/dbt/adapters/postgres/__version__.py]
 
-[bumpversion:file:docker/Dockerfile]
+[bumpversion:file:plugins/redshift/dbt/adapters/redshift/__version__.py]
 
-[bumpversion:file:tests/adapter/setup.py]
+[bumpversion:file:plugins/snowflake/dbt/adapters/snowflake/__version__.py]
+
+[bumpversion:file:plugins/bigquery/dbt/adapters/bigquery/__version__.py]
 
-[bumpversion:file:tests/adapter/dbt/tests/adapter/__version__.py]

.changes/0.0.0.md

@@ -1,23 +0,0 @@
-## Previous Releases
-
-For information on prior major and minor releases, see their changelogs:
-
-
-* [1.6](https://github.com/dbt-labs/dbt-core/blob/1.6.latest/CHANGELOG.md)
-* [1.5](https://github.com/dbt-labs/dbt-core/blob/1.5.latest/CHANGELOG.md)
-* [1.4](https://github.com/dbt-labs/dbt-core/blob/1.4.latest/CHANGELOG.md)
-* [1.3](https://github.com/dbt-labs/dbt-core/blob/1.3.latest/CHANGELOG.md)
-* [1.2](https://github.com/dbt-labs/dbt-core/blob/1.2.latest/CHANGELOG.md)
-* [1.1](https://github.com/dbt-labs/dbt-core/blob/1.1.latest/CHANGELOG.md)
-* [1.0](https://github.com/dbt-labs/dbt-core/blob/1.0.latest/CHANGELOG.md)
-* [0.21](https://github.com/dbt-labs/dbt-core/blob/0.21.latest/CHANGELOG.md)
-* [0.20](https://github.com/dbt-labs/dbt-core/blob/0.20.latest/CHANGELOG.md)
-* [0.19](https://github.com/dbt-labs/dbt-core/blob/0.19.latest/CHANGELOG.md)
-* [0.18](https://github.com/dbt-labs/dbt-core/blob/0.18.latest/CHANGELOG.md)
-* [0.17](https://github.com/dbt-labs/dbt-core/blob/0.17.latest/CHANGELOG.md)
-* [0.16](https://github.com/dbt-labs/dbt-core/blob/0.16.latest/CHANGELOG.md)
-* [0.15](https://github.com/dbt-labs/dbt-core/blob/0.15.latest/CHANGELOG.md)
-* [0.14](https://github.com/dbt-labs/dbt-core/blob/0.14.latest/CHANGELOG.md)
-* [0.13](https://github.com/dbt-labs/dbt-core/blob/0.13.latest/CHANGELOG.md)
-* [0.12](https://github.com/dbt-labs/dbt-core/blob/0.12.latest/CHANGELOG.md)
-* [0.11 and earlier](https://github.com/dbt-labs/dbt-core/blob/0.11.latest/CHANGELOG.md)

.changes/1.7.0-b1.md

@@ -1,70 +0,0 @@
-## dbt-core 1.7.0-b1 - August 17, 2023
-
-### Breaking Changes
-
-- Removed the FirstRunResultError and AfterFirstRunResultError event types, using the existing RunResultError in their place. ([#7963](https://github.com/dbt-labs/dbt-core/issues/7963))
-
-### Features
-
-- Enable re-population of metadata vars post-environment change during programmatic invocation ([#8010](https://github.com/dbt-labs/dbt-core/issues/8010))
-- Added support to configure a delimiter for a seed file, defaults to comma ([#3990](https://github.com/dbt-labs/dbt-core/issues/3990))
-- Allow specification of `create_metric: true` on measures ([#8125](https://github.com/dbt-labs/dbt-core/issues/8125))
-
-### Fixes
-
-- Copy dir during `dbt deps` if symlink fails ([#7428](https://github.com/dbt-labs/dbt-core/issues/7428), [#8223](https://github.com/dbt-labs/dbt-core/issues/8223))
-- Fixed double-underline ([#5301](https://github.com/dbt-labs/dbt-core/issues/5301))
-- Copy target_schema from config into snapshot node ([#6745](https://github.com/dbt-labs/dbt-core/issues/6745))
-- Enable converting deprecation warnings to errors ([#8130](https://github.com/dbt-labs/dbt-core/issues/8130))
-- Add status to Parse Inline Error ([#8173](https://github.com/dbt-labs/dbt-core/issues/8173))
-- Ensure `warn_error_options` get serialized in `invocation_args_dict` ([#7694](https://github.com/dbt-labs/dbt-core/issues/7694))
-- Stop detecting materialization macros based on macro name ([#6231](https://github.com/dbt-labs/dbt-core/issues/6231))
-- Update `dbt deps` download retry logic to handle `EOFError` exceptions ([#6653](https://github.com/dbt-labs/dbt-core/issues/6653))
-- Improve handling of CTE injection with ephemeral models ([#8213](https://github.com/dbt-labs/dbt-core/issues/8213))
-- Fix unbound local variable error in `checked_agg_time_dimension_for_measure` ([#8230](https://github.com/dbt-labs/dbt-core/issues/8230))
-- Ensure runtime errors are raised for graph runnable tasks (compile, show, run, etc) ([#8166](https://github.com/dbt-labs/dbt-core/issues/8166))
-- Fix retry not working with log-file-max-bytes ([#8297](https://github.com/dbt-labs/dbt-core/issues/8297))
-- Detect changes to model access, version, or latest_version in state:modified ([#8189](https://github.com/dbt-labs/dbt-core/issues/8189))
-- Add connection status into list of statuses for dbt debug ([#8350](https://github.com/dbt-labs/dbt-core/issues/8350))
-- fix fqn-selection for external versioned models ([#8374](https://github.com/dbt-labs/dbt-core/issues/8374))
-- Fix: DbtInternalError after model that previously ref'd external model is deleted ([#8375](https://github.com/dbt-labs/dbt-core/issues/8375))
-- Fix using list command with path selector and project-dir ([#8385](https://github.com/dbt-labs/dbt-core/issues/8385))
-- Remedy performance regression by only writing run_results.json once. ([#8360](https://github.com/dbt-labs/dbt-core/issues/8360))
-
-### Docs
-
-- Corrected spelling of "Partiton" ([dbt-docs/#8100](https://github.com/dbt-labs/dbt-docs/issues/8100))
-- Remove static SQL codeblock for metrics ([dbt-docs/#436](https://github.com/dbt-labs/dbt-docs/issues/436))
-- fixed comment util.py ([dbt-docs/#None](https://github.com/dbt-labs/dbt-docs/issues/None))
-- Display contract and column constraints on the model page ([dbt-docs/#433](https://github.com/dbt-labs/dbt-docs/issues/433))
-- Display semantic model details in docs ([dbt-docs/#431](https://github.com/dbt-labs/dbt-docs/issues/431))
-
-### Under the Hood
-
-- Refactor flaky test pp_versioned_models ([#7781](https://github.com/dbt-labs/dbt-core/issues/7781))
-- format exception from dbtPlugin.initialize ([#8152](https://github.com/dbt-labs/dbt-core/issues/8152))
-- A way to control maxBytes for a single dbt.log file ([#8199](https://github.com/dbt-labs/dbt-core/issues/8199))
-- Ref expressions with version can now be processed by the latest version of the high-performance dbt-extractor library. ([#7688](https://github.com/dbt-labs/dbt-core/issues/7688))
-- Bump manifest schema version to v11, freeze manifest v10 ([#8333](https://github.com/dbt-labs/dbt-core/issues/8333))
-- add tracking for plugin.get_nodes calls ([#8344](https://github.com/dbt-labs/dbt-core/issues/8344))
-- add internal flag: --no-partial-parse-file-diff to inform whether to compute a file diff during partial parsing ([#8363](https://github.com/dbt-labs/dbt-core/issues/8363))
-- Add return values to a number of functions for mypy ([#8389](https://github.com/dbt-labs/dbt-core/issues/8389))
-- Fix mypy warnings for ManifestLoader.load() ([#8401](https://github.com/dbt-labs/dbt-core/issues/8401))
-- Use python version 3.10.7 in Docker image. ([#8444](https://github.com/dbt-labs/dbt-core/issues/8444))
-
-### Dependencies
-
-- Bump mypy from 1.3.0 to 1.4.0 ([#7912](https://github.com/dbt-labs/dbt-core/pull/7912))
-- Bump mypy from 1.4.0 to 1.4.1 ([#8219](https://github.com/dbt-labs/dbt-core/pull/8219))
-- Update pin for click<9 ([#8232](https://github.com/dbt-labs/dbt-core/pull/8232))
-- Add upper bound to sqlparse pin of <0.5 ([#8236](https://github.com/dbt-labs/dbt-core/pull/8236))
-- Support dbt-semantic-interfaces 0.2.0 ([#8250](https://github.com/dbt-labs/dbt-core/pull/8250))
-
-### Contributors
-- [@anjutiwari](https://github.com/anjutiwari) ([#7428](https://github.com/dbt-labs/dbt-core/issues/7428), [#8223](https://github.com/dbt-labs/dbt-core/issues/8223))
-- [@d-kaneshiro](https://github.com/d-kaneshiro) ([#None](https://github.com/dbt-labs/dbt-core/issues/None))
-- [@gem7318](https://github.com/gem7318) ([#8010](https://github.com/dbt-labs/dbt-core/issues/8010))
-- [@lllong33](https://github.com/lllong33) ([#5301](https://github.com/dbt-labs/dbt-core/issues/5301))
-- [@marcodamore](https://github.com/marcodamore) ([#436](https://github.com/dbt-labs/dbt-core/issues/436))
-- [@pgoslatara](https://github.com/pgoslatara) ([#8100](https://github.com/dbt-labs/dbt-core/issues/8100))
-- [@ramonvermeulen](https://github.com/ramonvermeulen) ([#3990](https://github.com/dbt-labs/dbt-core/issues/3990))

.changes/1.7.0-b2.md

@@ -1,29 +0,0 @@
-## dbt-core 1.7.0-b2 - September 01, 2023
-
-### Features
-
-- Add node attributes related to compilation to run_results.json ([#7519](https://github.com/dbt-labs/dbt-core/issues/7519))
-- Support configuration of semantic models with the addition of enable/disable and group enablement. ([#7968](https://github.com/dbt-labs/dbt-core/issues/7968))
-
-### Fixes
-
-- Add support for swapping materialized views with tables/views and vice versa ([#8449](https://github.com/dbt-labs/dbt-core/issues/8449))
-- Turn breaking changes to contracted models into warnings for unversioned models ([#8384](https://github.com/dbt-labs/dbt-core/issues/8384), [#8282](https://github.com/dbt-labs/dbt-core/issues/8282))
-- Ensure parsing does not break when `window_groupings` is not specified for `non_additive_dimension` ([#8453](https://github.com/dbt-labs/dbt-core/issues/8453))
-- fix ambiguous reference error for tests and versions when model name is duplicated across packages ([#8327](https://github.com/dbt-labs/dbt-core/issues/8327), [#8493](https://github.com/dbt-labs/dbt-core/issues/8493))
-- Fix "Internal Error: Expected node <unique-id> not found in manifest" when depends_on set on ModelNodeArgs ([#8506](https://github.com/dbt-labs/dbt-core/issues/8506))
-- Fix snapshot success message ([#7583](https://github.com/dbt-labs/dbt-core/issues/7583))
-
-### Docs
-
-- Fix newline escapes and improve formatting in docker README ([dbt-docs/#8211](https://github.com/dbt-labs/dbt-docs/issues/8211))
-
-### Under the Hood
-
-- Switch from hologram to mashumaro jsonschema ([#8426](https://github.com/dbt-labs/dbt-core/issues/8426))
-- Re-organize jinja macros: relation-specific in /macros/adapters/relations/<relation>, relation agnostic in /macros/relations ([#8449](https://github.com/dbt-labs/dbt-core/issues/8449))
-- Update typing to meet mypy standards ([#8396](https://github.com/dbt-labs/dbt-core/issues/8396))
-- Mypy errors - adapters/factory.py ([#8387](https://github.com/dbt-labs/dbt-core/issues/8387))
-
-### Contributors
-- [@jamezrin](https://github.com/jamezrin) ([#8211](https://github.com/dbt-labs/dbt-core/issues/8211))

.changes/1.7.0/Breaking Changes-20230725-171359.yaml

@@ -1,7 +0,0 @@
-kind: Breaking Changes
-body: Removed the FirstRunResultError and AfterFirstRunResultError event types, using
-  the existing RunResultError in their place.
-time: 2023-07-25T17:13:59.441682-04:00
-custom:
-  Author: peterallenwebb
-  Issue: "7963"

.changes/1.7.0/Dependencies-20230621-005752.yaml

@@ -1,6 +0,0 @@
-kind: "Dependencies"
-body: "Bump mypy from 1.3.0 to 1.4.0"
-time: 2023-06-21T00:57:52.00000Z
-custom:
-  Author: dependabot[bot]
-  PR: 7912

.changes/1.7.0/Dependencies-20230726-201740.yaml

@@ -1,6 +0,0 @@
-kind: "Dependencies"
-body: "Bump mypy from 1.4.0 to 1.4.1"
-time: 2023-07-26T20:17:40.00000Z
-custom:
-  Author: dependabot[bot]
-  PR: 8219

.changes/1.7.0/Dependencies-20230727-145703.yaml

@@ -1,6 +0,0 @@
-kind: Dependencies
-body: Update pin for click<9
-time: 2023-07-27T14:57:03.180458-05:00
-custom:
-  Author: emmyoop
-  PR: "8232"

.changes/1.7.0/Dependencies-20230727-145726.yaml

@@ -1,6 +0,0 @@
-kind: Dependencies
-body: Add upper bound to sqlparse pin of <0.5
-time: 2023-07-27T14:57:26.40416-05:00
-custom:
-  Author: emmyoop
-  PR: "8236"

.changes/1.7.0/Dependencies-20230728-135227.yaml

@@ -1,6 +0,0 @@
-kind: Dependencies
-body: Support dbt-semantic-interfaces 0.2.0
-time: 2023-07-28T13:52:27.207241-07:00
-custom:
-  Author: QMalcolm
-  PR: "8250"

.changes/1.7.0/Docs-20230715-200907.yaml

@@ -1,6 +0,0 @@
-kind: Docs
-body: Corrected spelling of "Partiton"
-time: 2023-07-15T20:09:07.057361092+02:00
-custom:
-  Author: pgoslatara
-  Issue: "8100"

.changes/1.7.0/Docs-20230718-192422.yaml

@@ -1,6 +0,0 @@
-kind: Docs
-body: Remove static SQL codeblock for metrics
-time: 2023-07-18T19:24:22.155323+02:00
-custom:
-  Author: marcodamore
-  Issue: "436"

.changes/1.7.0/Docs-20230727-170900.yaml

@@ -1,6 +0,0 @@
-kind: Docs
-body: fixed comment util.py
-time: 2023-07-27T17:09:00.089237+09:00
-custom:
-  Author: d-kaneshiro
-  Issue: None

.changes/1.7.0/Docs-20230728-193438.yaml

@@ -1,6 +0,0 @@
-kind: Docs
-body: Fix newline escapes and improve formatting in docker README
-time: 2023-07-28T19:34:38.351042747+02:00
-custom:
-  Author: jamezrin
-  Issue: "8211"

.changes/1.7.0/Docs-20230804-131815.yaml

@@ -1,6 +0,0 @@
-kind: Docs
-body: Display contract and column constraints on the model page
-time: 2023-08-04T13:18:15.627005-05:00
-custom:
-  Author: emmyoop
-  Issue: "433"

.changes/1.7.0/Docs-20230807-152548.yaml

@@ -1,6 +0,0 @@
-kind: Docs
-body: Display semantic model details in docs
-time: 2023-08-07T15:25:48.711627-05:00
-custom:
-  Author: emmyoop
-  Issue: "431"

.changes/1.7.0/Features-20230702-122813.yaml

@@ -1,7 +0,0 @@
-kind: Features
-body: Enable re-population of metadata vars post-environment change during programmatic
-  invocation
-time: 2023-07-02T12:28:13.416305-04:00
-custom:
-  Author: gem7318
-  Issue: "8010"

.changes/1.7.0/Features-20230714-202445.yaml

@@ -1,6 +0,0 @@
-kind: Features
-body: Added support to configure a delimiter for a seed file, defaults to comma
-time: 2023-07-14T20:24:45.513847165+02:00
-custom:
-  Author: ramonvermeulen
-  Issue: "3990"

.changes/1.7.0/Features-20230803-151824.yaml

@@ -1,6 +0,0 @@
-kind: Features
-body: 'Allow specification of `create_metric: true` on measures'
-time: 2023-08-03T15:18:24.351003-07:00
-custom:
-  Author: QMalcolm
-  Issue: "8125"

.changes/1.7.0/Features-20230821-103357.yaml

@@ -1,6 +0,0 @@
-kind: Features
-body: Add node attributes related to compilation to run_results.json
-time: 2023-08-21T10:33:57.200883-04:00
-custom:
-  Author: peterallenwebb
-  Issue: "7519"

.changes/1.7.0/Features-20230828-092100.yaml

@@ -1,6 +0,0 @@
-kind: Features
-body: Support configuration of semantic models with the addition of enable/disable and group enablement.
-time: 2023-08-28T09:21:00.551633-05:00
-custom:
-  Author: emmyoop
-  Issue: "7968"

.changes/1.7.0/Fixes-20230424-210734.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Copy dir during `dbt deps` if symlink fails
-time: 2023-04-24T21:07:34.336797+05:30
-custom:
-  Author: anjutiwari
-  Issue: "7428 8223"

.changes/1.7.0/Fixes-20230625-142731.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Fixed double-underline
-time: 2023-06-25T14:27:31.231253719+08:00
-custom:
-  Author: lllong33
-  Issue: "5301"

.changes/1.7.0/Fixes-20230717-160652.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Copy target_schema from config into snapshot node
-time: 2023-07-17T16:06:52.957724-04:00
-custom:
-  Author: gshank
-  Issue: "6745"

.changes/1.7.0/Fixes-20230718-125518.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Enable converting deprecation warnings to errors
-time: 2023-07-18T12:55:18.03914-04:00
-custom:
-  Author: michelleark
-  Issue: "8130"

.changes/1.7.0/Fixes-20230720-122723.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Add status to Parse Inline Error
-time: 2023-07-20T12:27:23.085084-07:00
-custom:
-  Author: ChenyuLInx
-  Issue: "8173"

.changes/1.7.0/Fixes-20230720-161513.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Ensure `warn_error_options` get serialized in `invocation_args_dict`
-time: 2023-07-20T16:15:13.761813-07:00
-custom:
-  Author: QMalcolm
-  Issue: "7694"

.changes/1.7.0/Fixes-20230720-170112.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Stop detecting materialization macros based on macro name
-time: 2023-07-20T17:01:12.496238-07:00
-custom:
-  Author: QMalcolm
-  Issue: "6231"

.changes/1.7.0/Fixes-20230720-172422.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Update `dbt deps` download retry logic to handle `EOFError` exceptions
-time: 2023-07-20T17:24:22.969951-07:00
-custom:
-  Author: QMalcolm
-  Issue: "6653"

.changes/1.7.0/Fixes-20230726-104448.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Improve handling of CTE injection with ephemeral models
-time: 2023-07-26T10:44:48.888451-04:00
-custom:
-  Author: gshank
-  Issue: "8213"

.changes/1.7.0/Fixes-20230727-125830.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Fix unbound local variable error in `checked_agg_time_dimension_for_measure`
-time: 2023-07-27T12:58:30.673803-07:00
-custom:
-  Author: QMalcolm
-  Issue: "8230"

.changes/1.7.0/Fixes-20230728-115620.yaml

@@ -1,7 +0,0 @@
-kind: Fixes
-body: Ensure runtime errors are raised for graph runnable tasks (compile, show, run,
-  etc)
-time: 2023-07-28T11:56:20.863718-04:00
-custom:
-  Author: michelleark
-  Issue: "8166"

.changes/1.7.0/Fixes-20230802-141556.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Fix retry not working with log-file-max-bytes
-time: 2023-08-02T14:15:56.306027-07:00
-custom:
-  Author: ChenyuLInx
-  Issue: "8297"

.changes/1.7.0/Fixes-20230806-222319.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Detect changes to model access, version, or latest_version in state:modified
-time: 2023-08-06T22:23:19.166334-04:00
-custom:
-  Author: michelleark
-  Issue: "8189"

.changes/1.7.0/Fixes-20230810-184859.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Add connection status into list of statuses for dbt debug
-time: 2023-08-10T18:48:59.221344+01:00
-custom:
-  Author: aranke
-  Issue: "8350"

.changes/1.7.0/Fixes-20230811-204144.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: fix fqn-selection for external versioned models
-time: 2023-08-11T20:41:44.725144-04:00
-custom:
-  Author: michelleark
-  Issue: "8374"

.changes/1.7.0/Fixes-20230811-212008.yaml

@@ -1,7 +0,0 @@
-kind: Fixes
-body: 'Fix: DbtInternalError after model that previously ref''d external model is
-  deleted'
-time: 2023-08-11T21:20:08.145554-04:00
-custom:
-  Author: michelleark
-  Issue: "8375"

.changes/1.7.0/Fixes-20230814-145702.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Fix using list command with path selector and project-dir
-time: 2023-08-14T14:57:02.02816-04:00
-custom:
-  Author: gshank
-  Issue: "8385"

.changes/1.7.0/Fixes-20230815-104444.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Remedy performance regression by only writing run_results.json once.
-time: 2023-08-15T10:44:44.836991-04:00
-custom:
-  Author: peterallenwebb
-  Issue: "8360"

.changes/1.7.0/Fixes-20230817-130915.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Use python version 3.10.7 in Docker image.
-time: 2023-08-17T13:09:15.936349-05:00
-custom:
-  Author: McKnight-42
-  Issue: "8444"

.changes/1.7.0/Fixes-20230817-185739.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Add support for swapping materialized views with tables/views and vice versa
-time: 2023-08-17T18:57:39.01958-04:00
-custom:
-  Author: mikealfare
-  Issue: "8449"

.changes/1.7.0/Fixes-20230818-095348.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Ensure parsing does not break when `window_groupings` is not specified for `non_additive_dimension`
-time: 2023-08-18T09:53:48.154848-07:00
-custom:
-  Author: QMalcolm
-  Issue: "8453"

.changes/1.7.0/Fixes-20230818-103802.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Turn breaking changes to contracted models into warnings for unversioned models
-time: 2023-08-18T10:38:02.251286-05:00
-custom:
-  Author: emmyoop
-  Issue: 8384 8282

.changes/1.7.0/Fixes-20230824-161024.yaml

@@ -1,7 +0,0 @@
-kind: Fixes
-body: fix ambiguous reference error for tests and versions when model name is duplicated across
-  packages
-time: 2023-08-24T16:10:24.437362-04:00
-custom:
-  Author: michelleark
-  Issue: "8327 8493"

.changes/1.7.0/Fixes-20230828-125858.yaml

@@ -1,7 +0,0 @@
-kind: Fixes
-body: 'Fix "Internal Error: Expected node <unique-id> not found in manifest" when
-  depends_on set on ModelNodeArgs'
-time: 2023-08-28T12:58:58.061228-04:00
-custom:
-  Author: michelleark
-  Issue: "8506"

.changes/1.7.0/Fixes-20230830-150803.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Fix snapshot success message
-time: 2023-08-30T15:08:03.429373-04:00
-custom:
-  Author: gshank
-  Issue: "7583"

.changes/1.7.0/Under the Hood-20230718-145428.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Switch from hologram to mashumaro jsonschema
-time: 2023-07-18T14:54:28.41453-04:00
-custom:
-  Author: gshank
-  Issue: "8426"

.changes/1.7.0/Under the Hood-20230719-124611.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Refactor flaky test pp_versioned_models
-time: 2023-07-19T12:46:11.972481-04:00
-custom:
-  Author: gshank
-  Issue: "7781"

.changes/1.7.0/Under the Hood-20230719-163334.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: format exception from dbtPlugin.initialize
-time: 2023-07-19T16:33:34.586377-04:00
-custom:
-  Author: michelleark
-  Issue: "8152"

.changes/1.7.0/Under the Hood-20230724-150654.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: A way to control maxBytes for a single dbt.log file
-time: 2023-07-24T15:06:54.263822-07:00
-custom:
-  Author: ChenyuLInx
-  Issue: "8199"

.changes/1.7.0/Under the Hood-20230725-102609.yaml

@@ -1,7 +0,0 @@
-kind: Under the Hood
-body: Ref expressions with version can now be processed by the latest version of the
-  high-performance dbt-extractor library.
-time: 2023-07-25T10:26:09.902878-04:00
-custom:
-  Author: peterallenwebb
-  Issue: "7688"

.changes/1.7.0/Under the Hood-20230807-164509.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Bump manifest schema version to v11, freeze manifest v10
-time: 2023-08-07T16:45:09.712744-04:00
-custom:
-  Author: gshank
-  Issue: "8333"

.changes/1.7.0/Under the Hood-20230809-094834.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: add tracking for plugin.get_nodes calls
-time: 2023-08-09T09:48:34.819445-04:00
-custom:
-  Author: michelleark
-  Issue: "8344"

.changes/1.7.0/Under the Hood-20230811-100902.yaml

@@ -1,7 +0,0 @@
-kind: Under the Hood
-body: 'add internal flag: --no-partial-parse-file-diff to inform whether to compute
-  a file diff during partial parsing'
-time: 2023-08-11T10:09:02.832241-04:00
-custom:
-  Author: michelleark
-  Issue: "8363"

.changes/1.7.0/Under the Hood-20230815-170307.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Add return values to a number of functions for mypy
-time: 2023-08-15T17:03:07.895252-04:00
-custom:
-  Author: gshank
-  Issue: "8389"

.changes/1.7.0/Under the Hood-20230817-134548.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Fix mypy warnings for ManifestLoader.load()
-time: 2023-08-17T13:45:48.937252-04:00
-custom:
-  Author: gshank
-  Issue: "8401"

.changes/1.7.0/Under the Hood-20230821-134801.yaml

@@ -1,7 +0,0 @@
-kind: Under the Hood
-body: 'Re-organize jinja macros: relation-specific in /macros/adapters/relations/<relation>,
-  relation agnostic in /macros/relations'
-time: 2023-08-21T13:48:01.474731-04:00
-custom:
-  Author: mikealfare
-  Issue: "8449"

.changes/1.7.0/Under the Hood-20230823-194237.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Update typing to meet mypy standards
-time: 2023-08-23T19:42:37.130694-04:00
-custom:
-  Author: mikealfare
-  Issue: "8396"

.changes/1.7.0/Under the Hood-20230830-140231.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Mypy errors - adapters/factory.py
-time: 2023-08-30T14:02:31.519929-04:00
-custom:
-  Author: gshank
-  Issue: "8387"

.changes/README.md

@@ -1,53 +0,0 @@
-# CHANGELOG Automation
-
-We use [changie](https://changie.dev/) to automate `CHANGELOG` generation.  For installation and format/command specifics, see the documentation.
-
-### Quick Tour
-
-- All new change entries get generated under `/.changes/unreleased` as a yaml file
-- `header.tpl.md` contains the contents of the entire CHANGELOG file
-- `0.0.0.md` contains the contents of the footer for the entire CHANGELOG file.  changie looks to be in the process of supporting a footer file the same as it supports a header file.  Switch to that when available.  For now, the 0.0.0 in the file name forces it to the bottom of the changelog no matter what version we are releasing.
-- `.changie.yaml` contains the fields in a change, the format of a single change, as well as the format of the Contributors section for each version.
-
-### Workflow
-
-#### Daily workflow
-Almost every code change we make associated with an issue will require a `CHANGELOG` entry.  After you have created the PR in GitHub, run `changie new` and follow the command prompts to generate a yaml file with your change details.  This only needs to be done once per PR.
-
-The `changie new` command will ensure correct file format and file name.  There is a one to one mapping of issues to changes.  Multiple issues cannot be lumped into a single entry. If you make a mistake, the yaml file may be directly modified and saved as long as the format is preserved.
-
-Note: If your PR has been cleared by the Core Team as not needing a changelog entry, the `Skip Changelog` label may be put on the PR to bypass the GitHub action that blacks PRs from being merged when they are missing a `CHANGELOG` entry.
-
-#### Prerelease Workflow
-These commands batch up changes in `/.changes/unreleased` to be included in this prerelease and move those files to a directory named for the release version.  The `--move-dir` will be created if it does not exist and is created in `/.changes`.
-
-```
-changie batch <version>  --move-dir '<version>' --prerelease 'rc1'
-changie merge
-```
-
-Example
-```
-changie batch 1.0.5  --move-dir '1.0.5' --prerelease 'rc1'
-changie merge
-```
-
-#### Final Release Workflow
-These commands batch up changes in `/.changes/unreleased` as well as `/.changes/<version>` to be included in this final release and delete all prereleases.  This rolls all prereleases up into a single final release.  All `yaml` files in `/unreleased` and `<version>` will be deleted at this point.
-
-```
-changie batch <version>  --include '<version>' --remove-prereleases
-changie merge
-```
-
-Example
-```
-changie batch 1.0.5  --include '1.0.5' --remove-prereleases
-changie merge
-```
-
-### A Note on Manual Edits & Gotchas
-- Changie generates markdown files in the `.changes` directory that are parsed together with the `changie merge` command.  Every time `changie merge` is run, it regenerates the entire file.  For this reason, any changes made directly to `CHANGELOG.md` will be overwritten on the next run of `changie merge`.
-- If changes need to be made to the `CHANGELOG.md`, make the changes to the relevant `<version>.md` file located in the `/.changes` directory.  You will then run `changie merge` to regenerate the `CHANGELOG.MD`.
-- Do not run `changie batch` again on released versions.  Our final release workflow deletes all of the yaml files associated with individual changes.  If for some reason modifications to the `CHANGELOG.md` are required after we've generated the final release `CHANGELOG.md`, the modifications need to be done manually to the `<version>.md` file in the `/.changes` directory.
-- changie can modify, create and delete files depending on the command you run.  This is expected.  Be sure to commit everything that has been modified and deleted.

.changes/header.tpl.md

@@ -1,6 +0,0 @@
-# dbt Core Changelog
-
-- This file provides a full account of all changes to `dbt-core` and `dbt-postgres`
-- Changes are listed under the (pre)release in which they first appear. Subsequent releases include changes from previous releases.
-- "Breaking changes" listed under a version may require action from end users or external maintainers when upgrading to that version.
-- Do not edit this file directly. This file is auto-generated using [changie](https://github.com/miniscruff/changie). For details on how to document a change, see [the contributing guide](https://github.com/dbt-labs/dbt-core/blob/main/CONTRIBUTING.md#adding-changelog-entry)

.changes/unreleased/Features-20230823-140407.yaml

@@ -1,6 +0,0 @@
-kind: Features
-body: Add --no-inject-ephemeral-ctes flag for `compile` command, for usage by linting.
-time: 2023-08-23T14:04:07.617476-04:00
-custom:
-  Author: benmosher
-  Issue: "8480"

.changes/unreleased/Features-20230830-212828.yaml

@@ -1,6 +0,0 @@
-kind: Features
-body: Accept a `dbt-cloud` config in dbt_project.yml
-time: 2023-08-30T21:28:28.976746-05:00
-custom:
-  Author: emmyoop
-  Issue: "8438"

.changes/unreleased/Features-20230831-204804.yaml

@@ -1,6 +0,0 @@
-kind: Features
-body: Support atomic replace in the global replace macro
-time: 2023-08-31T20:48:04.098933-04:00
-custom:
-  Author: mikealfare
-  Issue: "8539"

.changes/unreleased/Features-20230912-153013.yaml

@@ -1,6 +0,0 @@
-kind: Features
-body: Allow setting "access" as a config in addition to as a property
-time: 2023-09-12T15:30:13.859595-04:00
-custom:
-  Author: gshank
-  Issue: "8383"

.changes/unreleased/Features-20230913-182707.yaml

@@ -1,8 +0,0 @@
-kind: Features
-body: Loosen typing requirement on renameable/replaceable relations to Iterable to
-  allow adapters more flexibility in registering relation types, include docstrings
-  as suggestions
-time: 2023-09-13T18:27:07.974612-04:00
-custom:
-  Author: mikealfare
-  Issue: "8647"

.changes/unreleased/Features-20230915-123733.yaml

@@ -1,6 +0,0 @@
-kind: Features
-body: 'Allow adapters to include package logs in dbt standard logging '
-time: 2023-09-15T12:37:33.862862-07:00
-custom:
-  Author: colin-rogers-dbt
-  Issue: "7859"

.changes/unreleased/Features-20230925-182237.yaml

@@ -1,6 +0,0 @@
-kind: Features
-body: Add git_branch and git_sha to the Jinja context
-time: 2023-09-25T18:22:37.142445+02:00
-custom:
-  Author: b-per
-  Issue: "8690"

.changes/unreleased/Fixes-20230424-161642.yaml

@@ -1,7 +0,0 @@
-kind: Fixes
-body: If --profile specified with dbt-init, create the project with the specified
-  profile
-time: 2023-04-24T16:16:42.994547-04:00
-custom:
-  Author: ezraerb
-  Issue: "6154"

.changes/unreleased/Fixes-20230803-093502.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Add explicit support for integers for the show command
-time: 2023-08-03T09:35:02.163968-05:00
-custom:
-  Author: dave-connors-3
-  Issue: "8153"

.changes/unreleased/Fixes-20230906-120212.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Update metric helper functions to work with new semantic layer metrics
-time: 2023-09-06T12:02:12.156534-07:00
-custom:
-  Author: QMalcolm
-  Issue: "8134"

.changes/unreleased/Fixes-20230906-142213.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: make version comparison insensitive to order
-time: 2023-09-06T14:22:13.114549-04:00
-custom:
-  Author: michelleark
-  Issue: "8571"

.changes/unreleased/Fixes-20230906-162427.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Parse the correct schema version from manifest
-time: 2023-09-06T16:24:27.849069+01:00
-custom:
-  Author: aranke
-  Issue: "8544"

.changes/unreleased/Fixes-20230912-225329.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Warn when --state == --target
-time: 2023-09-12T22:53:29.869746+01:00
-custom:
-  Author: aranke
-  Issue: "8160"

.changes/unreleased/Under the Hood-20230831-164435.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Added more type annotations.
-time: 2023-08-31T16:44:35.737954-04:00
-custom:
-  Author: peterallenwebb
-  Issue: "8537"

.changes/unreleased/Under the Hood-20230906-110249.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Add functional test for advanced ref override
-time: 2023-09-06T11:02:49.253486-04:00
-custom:
-  Author: michelleark
-  Issue: "8566"

.changes/unreleased/Under the Hood-20230906-132435.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Fix untyped functions in task/runnable.py (mypy warning)
-time: 2023-09-06T13:24:35.448782-04:00
-custom:
-  Author: michelleark
-  Issue: "8402"

.changes/unreleased/Under the Hood-20230906-141616.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Audit potential circular dependencies
-time: 2023-09-06T14:16:16.58457+01:00
-custom:
-  Author: aranke
-  Issue: "8349"

.changes/unreleased/Under the Hood-20230906-164901.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Add typing to __init__ in base.py
-time: 2023-09-06T16:49:01.150713+01:00
-custom:
-  Author: aranke
-  Issue: "8398"

.changes/unreleased/Under the Hood-20230912-230619.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: add a test for ephemeral cte injection
-time: 2023-09-12T23:06:19.938207+01:00
-custom:
-  Author: michelleark
-  Issue: "8376"

.changes/unreleased/Under the Hood-20230913-141651.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Fix test_numeric_values to look for more specific strings
-time: 2023-09-13T14:16:51.453247-04:00
-custom:
-  Author: gshank
-  Issue: "8470"

.changie.yaml

@@ -1,140 +0,0 @@
-changesDir: .changes
-unreleasedDir: unreleased
-headerPath: header.tpl.md
-versionHeaderPath: ""
-changelogPath: CHANGELOG.md
-versionExt: md
-envPrefix: "CHANGIE_"
-versionFormat: '## dbt-core {{.Version}} - {{.Time.Format "January 02, 2006"}}'
-kindFormat: '### {{.Kind}}'
-changeFormat: |-
-  {{- $IssueList := list }}
-  {{- $changes := splitList " " $.Custom.Issue }}
-  {{- range $issueNbr := $changes }}
-    {{- $changeLink := "[#nbr](https://github.com/dbt-labs/dbt-core/issues/nbr)" | replace "nbr" $issueNbr }}
-    {{- $IssueList = append $IssueList $changeLink  }}
-  {{- end -}}
-  - {{.Body}} ({{ range $index, $element := $IssueList }}{{if $index}}, {{end}}{{$element}}{{end}})
-
-kinds:
-  - label: Breaking Changes
-  - label: Features
-  - label: Fixes
-  - label: Docs
-    changeFormat: |-
-      {{- $IssueList := list }}
-      {{- $changes := splitList " " $.Custom.Issue }}
-      {{- range $issueNbr := $changes }}
-        {{- $changeLink := "[dbt-docs/#nbr](https://github.com/dbt-labs/dbt-docs/issues/nbr)" | replace "nbr" $issueNbr }}
-        {{- $IssueList = append $IssueList $changeLink }}
-      {{- end -}}
-      - {{.Body}} ({{ range $index, $element := $IssueList }}{{if $index}}, {{end}}{{$element}}{{end}})
-  - label: Under the Hood
-  - label: Dependencies
-    changeFormat: |-
-      {{- $PRList := list }}
-      {{- $changes := splitList " " $.Custom.PR }}
-      {{- range $pullrequest := $changes }}
-        {{- $changeLink := "[#nbr](https://github.com/dbt-labs/dbt-core/pull/nbr)" | replace "nbr" $pullrequest }}
-        {{- $PRList = append $PRList $changeLink  }}
-      {{- end -}}
-      - {{.Body}} ({{ range $index, $element := $PRList }}{{if $index}}, {{end}}{{$element}}{{end}})
-    skipGlobalChoices: true
-    additionalChoices:
-      - key: Author
-        label: GitHub Username(s) (separated by a single space if multiple)
-        type: string
-        minLength: 3
-      - key: PR
-        label: GitHub Pull Request Number (separated by a single space if multiple)
-        type: string
-        minLength: 1
-  - label: Security
-    changeFormat: |-
-      {{- $PRList := list }}
-      {{- $changes := splitList " " $.Custom.PR }}
-      {{- range $pullrequest := $changes }}
-        {{- $changeLink := "[#nbr](https://github.com/dbt-labs/dbt-core/pull/nbr)" | replace "nbr" $pullrequest }}
-        {{- $PRList = append $PRList $changeLink  }}
-      {{- end -}}
-      - {{.Body}} ({{ range $index, $element := $PRList }}{{if $index}}, {{end}}{{$element}}{{end}})
-    skipGlobalChoices: true
-    additionalChoices:
-      - key: Author
-        label: GitHub Username(s) (separated by a single space if multiple)
-        type: string
-        minLength: 3
-      - key: PR
-        label: GitHub Pull Request Number (separated by a single space if multiple)
-        type: string
-        minLength: 1
-
-newlines:
-  afterChangelogHeader: 1
-  afterKind: 1
-  afterChangelogVersion: 1
-  beforeKind: 1
-  endOfVersion: 1
-
-custom:
-- key: Author
-  label: GitHub Username(s) (separated by a single space if multiple)
-  type: string
-  minLength: 3
-- key: Issue
-  label: GitHub Issue Number (separated by a single space if multiple)
-  type: string
-  minLength: 1
-
-footerFormat: |
-  {{- $contributorDict := dict }}
-  {{- /* ensure all names in this list are all lowercase for later matching purposes */}}
-  {{- $core_team := splitList " " .Env.CORE_TEAM }}
-  {{- /* ensure we always skip snyk and dependabot in addition to the core team */}}
-  {{- $maintainers := list "dependabot[bot]" "snyk-bot"}}
-  {{- range $team_member := $core_team }}
-    {{- $team_member_lower := lower $team_member }}
-    {{- $maintainers = append $maintainers $team_member_lower }}
-  {{- end }}
-  {{- range $change := .Changes }}
-    {{- $authorList := splitList " " $change.Custom.Author }}
-    {{- /* loop through all authors for a single changelog */}}
-    {{- range $author := $authorList }}
-      {{- $authorLower := lower $author }}
-      {{- /* we only want to include non-core team contributors */}}
-      {{- if not (has $authorLower $maintainers)}}
-        {{- $changeList := splitList " " $change.Custom.Author }}
-          {{- $IssueList := list }}
-          {{- $changeLink := $change.Kind }}
-          {{- if or (eq $change.Kind "Dependencies") (eq $change.Kind "Security") }}
-            {{- $changes := splitList " " $change.Custom.PR }}
-            {{- range $issueNbr := $changes }}
-              {{- $changeLink := "[#nbr](https://github.com/dbt-labs/dbt-core/pull/nbr)" | replace "nbr" $issueNbr }}
-              {{- $IssueList = append $IssueList $changeLink  }}
-            {{- end -}}
-          {{- else }}
-            {{- $changes := splitList " " $change.Custom.Issue }}
-            {{- range $issueNbr := $changes }}
-              {{- $changeLink := "[#nbr](https://github.com/dbt-labs/dbt-core/issues/nbr)" | replace "nbr" $issueNbr }}
-              {{- $IssueList = append $IssueList $changeLink  }}
-            {{- end -}}
-          {{- end }}
-          {{- /* check if this contributor has other changes associated with them already */}}
-          {{- if hasKey $contributorDict $author }}
-            {{- $contributionList := get $contributorDict $author }}
-            {{- $contributionList = concat $contributionList $IssueList  }}
-            {{- $contributorDict := set $contributorDict $author $contributionList }}
-          {{- else }}
-            {{- $contributionList := $IssueList }}
-            {{- $contributorDict := set $contributorDict $author $contributionList }}
-          {{- end }}
-        {{- end}}
-    {{- end}}
-  {{- end }}
-  {{- /* no indentation here for formatting so the final markdown doesn't have unneeded indentations */}}
-  {{- if $contributorDict}}
-  ### Contributors
-  {{- range $k,$v := $contributorDict }}
-  - [@{{$k}}](https://github.com/{{$k}}) ({{ range $index, $element := $v }}{{if $index}}, {{end}}{{$element}}{{end}})
-  {{- end }}
-  {{- end }}

.flake8

@@ -1,12 +0,0 @@
-[flake8]
-select =
-    E
-    W
-    F
-ignore =
-    W503 # makes Flake8 work like black
-    W504
-    E203 # makes Flake8 work like black
-    E741
-    E501 # long line checking is done in black
-exclude = test/

.git-blame-ignore-revs

@@ -1,2 +0,0 @@
-# Reformatting dbt-core via black, flake8, mypy, and assorted pre-commit hooks.
-43e3fc22c4eae4d3d901faba05e33c40f1f1dc5a

.gitattributes

@@ -1,6 +0,0 @@
-core/dbt/include/index.html binary
-tests/functional/artifacts/data/state/*/manifest.json binary
-core/dbt/docs/build/html/searchindex.js binary
-core/dbt/docs/build/html/index.html binary
-performance/runner/Cargo.lock binary
-core/dbt/events/types_pb2.py binary

.github/CODEOWNERS

@@ -1,60 +0,0 @@
-# This file contains the code owners for the dbt-core repo.
-# PRs will be automatically assigned for review to the associated
-# team(s) or person(s) that touches any files that are mapped to them.
-#
-# A statement takes precedence over the statements above it so more general
-# assignments are found at the top with specific assignments being lower in
-# the ordering (i.e. catch all assignment should be the first item)
-#
-# Consult GitHub documentation for formatting guidelines:
-# https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners#example-of-a-codeowners-file
-
-# As a default for areas with no assignment,
-# the core team as a whole will be assigned
-*       @dbt-labs/core-team
-
-### OSS Tooling Guild
-
-/.github/                       @dbt-labs/guild-oss-tooling
-.bumpversion.cfg                @dbt-labs/guild-oss-tooling
-
-.changie.yaml                   @dbt-labs/guild-oss-tooling
-
-pre-commit-config.yaml          @dbt-labs/guild-oss-tooling
-pytest.ini                      @dbt-labs/guild-oss-tooling
-tox.ini                         @dbt-labs/guild-oss-tooling
-
-pyproject.toml                  @dbt-labs/guild-oss-tooling
-requirements.txt                @dbt-labs/guild-oss-tooling
-dev_requirements.txt            @dbt-labs/guild-oss-tooling
-/core/setup.py                  @dbt-labs/guild-oss-tooling
-/core/MANIFEST.in               @dbt-labs/guild-oss-tooling
-
-### ADAPTERS
-
-# Adapter interface ("base" + "sql" adapter defaults, cache)
-/core/dbt/adapters              @dbt-labs/core-adapters
-
-# Global project (default macros + materializations), starter project
-/core/dbt/include               @dbt-labs/core-adapters
-
-# Postgres plugin
-/plugins/                       @dbt-labs/core-adapters
-/plugins/postgres/setup.py      @dbt-labs/core-adapters @dbt-labs/guild-oss-tooling
-
-# Functional tests for adapter plugins
-/tests/adapter                  @dbt-labs/core-adapters
-
-### TESTS
-
-# Overlapping ownership for vast majority of unit + functional tests
-
-# Perf regression testing framework
-# This excludes the test project files itself since those aren't specific
-# framework changes (excluded by not setting an owner next to it- no owner)
-/performance                    @nathaniel-may
-/performance/projects
-
-### ARTIFACTS
-
-/schemas/dbt                    @dbt-labs/cloud-artifacts

.github/ISSUE_TEMPLATE/beta-minor-version-release.md

@@ -0,0 +1,27 @@
+---
+name: Beta minor version release
+about: Creates a tracking checklist of items for a Beta minor version release
+title: "[Tracking] v#.##.#B# release "
+labels: 'release'
+assignees: ''
+
+---
+
+### Release Core
+- [ ] [Engineering] Follow [dbt-release workflow](https://www.notion.so/dbtlabs/Releasing-b97c5ea9a02949e79e81db3566bbc8ef#03ff37da697d4d8ba63d24fae1bfa817) 
+- [ ] [Engineering] Verify new release branch is created in the repo
+- [ ] [Product] Finalize migration guide (next.docs.getdbt.com)
+
+### Release Cloud
+- [ ] [Engineering] Create a platform issue to update dbt Cloud and verify it is completed. [Example issue](https://github.com/dbt-labs/dbt-cloud/issues/3481)
+- [ ] [Engineering] Determine if schemas have changed. If so, generate new schemas and push to schemas.getdbt.com
+
+### Announce
+- [ ] [Product] Announce in dbt Slack
+
+### Post-release
+- [ ] [Engineering] [Bump plugin versions](https://www.notion.so/dbtlabs/Releasing-b97c5ea9a02949e79e81db3566bbc8ef#f01854e8da3641179fbcbe505bdf515c) (dbt-spark + dbt-presto), add compatibility as needed
+   - [ ]  [Spark](https://github.com/dbt-labs/dbt-spark) 
+   - [ ]  [Presto](https://github.com/dbt-labs/dbt-presto)
+- [ ] [Engineering] Create a platform issue to update dbt-spark versions to dbt Cloud. [Example issue](https://github.com/dbt-labs/dbt-cloud/issues/3481)
+- [ ] [Engineering] Create an epic for the RC release

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -1,97 +0,0 @@
-name: 🐞 Bug
-description: Report a bug or an issue you've found with dbt
-title: "[Bug] <title>"
-labels: ["bug", "triage"]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Thanks for taking the time to fill out this bug report!
-  - type: checkboxes
-    attributes:
-      label: Is this a new bug in dbt-core?
-      description: >
-        In other words, is this an error, flaw, failure or fault in our software?
-
-        If this is a bug that broke existing functionality that used to work, please open a regression issue.
-        If this is a bug in an adapter plugin, please open an issue in the adapter's repository.
-        If this is a bug experienced while using dbt Cloud, please report to [support](mailto:support@getdbt.com).
-        If this is a request for help or troubleshooting code in your own dbt project, please join our [dbt Community Slack](https://www.getdbt.com/community/join-the-community/) or open a [Discussion question](https://github.com/dbt-labs/docs.getdbt.com/discussions).
-
-        Please search to see if an issue already exists for the bug you encountered.
-      options:
-        - label: I believe this is a new bug in dbt-core
-          required: true
-        - label: I have searched the existing issues, and I could not find an existing issue for this bug
-          required: true
-  - type: textarea
-    attributes:
-      label: Current Behavior
-      description: A concise description of what you're experiencing.
-    validations:
-      required: true
-  - type: textarea
-    attributes:
-      label: Expected Behavior
-      description: A concise description of what you expected to happen.
-    validations:
-      required: true
-  - type: textarea
-    attributes:
-      label: Steps To Reproduce
-      description: Steps to reproduce the behavior.
-      placeholder: |
-        1. In this environment...
-        2. With this config...
-        3. Run '...'
-        4. See error...
-    validations:
-      required: true
-  - type: textarea
-    id: logs
-    attributes:
-      label: Relevant log output
-      description: |
-        If applicable, log output to help explain your problem.
-      render: shell
-    validations:
-      required: false
-  - type: textarea
-    attributes:
-      label: Environment
-      description: |
-        examples:
-          - **OS**: Ubuntu 20.04
-          - **Python**: 3.9.12 (`python3 --version`)
-          - **dbt-core**: 1.1.1 (`dbt --version`)
-      value: |
-        - OS:
-        - Python:
-        - dbt:
-      render: markdown
-    validations:
-      required: false
-  - type: dropdown
-    id: database
-    attributes:
-      label: Which database adapter are you using with dbt?
-      description: If the bug is specific to the database or adapter, please open the issue in that adapter's repository instead
-      multiple: true
-      options:
-        - postgres
-        - redshift
-        - snowflake
-        - bigquery
-        - spark
-        - other (mention it in "Additional Context")
-    validations:
-      required: false
-  - type: textarea
-    attributes:
-      label: Additional Context
-      description: |
-        Links? References? Anything that will give us more context about the issue you are encountering!
-
-        Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.
-    validations:
-      required: false

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,41 @@
+---
+name: Bug report
+about: Report a bug or an issue you've found with dbt
+title: ''
+labels: bug, triage
+assignees: ''
+
+---
+
+### Describe the bug
+A clear and concise description of what the bug is. What command did you run? What happened?
+
+### Steps To Reproduce
+In as much detail as possible, please provide steps to reproduce the issue. Sample data that triggers the issue, example model code, etc is all very helpful here.
+
+### Expected behavior
+A clear and concise description of what you expected to happen.
+
+### Screenshots and log output
+If applicable, add screenshots or log output to help explain your problem.
+
+### System information
+**Which database are you using dbt with?**
+- [ ] postgres
+- [ ] redshift
+- [ ] bigquery
+- [ ] snowflake
+- [ ] other (specify: ____________)
+
+
+**The output of `dbt --version`:**
+```
+<output goes here>
+```
+
+**The operating system you're using:**
+
+**The output of `python --version`:**
+
+### Additional context
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/config.yml

@@ -1,23 +0,0 @@
-blank_issues_enabled: false
-contact_links:
-  - name: Ask the community for help
-    url: https://github.com/dbt-labs/docs.getdbt.com/discussions
-    about: Need help troubleshooting? Check out our guide on how to ask
-  - name: Contact dbt Cloud support
-    url: mailto:support@getdbt.com
-    about: Are you using dbt Cloud? Contact our support team for help!
-  - name: Participate in Discussions
-    url: https://github.com/dbt-labs/dbt-core/discussions
-    about: Do you have a Big Idea for dbt? Read open discussions, or start a new one
-  - name: Create an issue for dbt-redshift
-    url: https://github.com/dbt-labs/dbt-redshift/issues/new/choose
-    about: Report a bug or request a feature for dbt-redshift
-  - name: Create an issue for dbt-bigquery
-    url: https://github.com/dbt-labs/dbt-bigquery/issues/new/choose
-    about: Report a bug or request a feature for dbt-bigquery
-  - name: Create an issue for dbt-snowflake
-    url: https://github.com/dbt-labs/dbt-snowflake/issues/new/choose
-    about: Report a bug or request a feature for dbt-snowflake
-  - name: Create an issue for dbt-spark
-    url: https://github.com/dbt-labs/dbt-spark/issues/new/choose
-    about: Report a bug or request a feature for dbt-spark

.github/ISSUE_TEMPLATE/feature-request.yml

@@ -1,59 +0,0 @@
-name: ✨ Feature
-description: Propose a straightforward extension of dbt functionality
-title: "[Feature] <title>"
-labels: ["enhancement", "triage"]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Thanks for taking the time to fill out this feature request!
-  - type: checkboxes
-    attributes:
-      label: Is this your first time submitting a feature request?
-      description: >
-        We want to make sure that features are distinct and discoverable,
-        so that other members of the community can find them and offer their thoughts.
-
-        Issues are the right place to request straightforward extensions of existing dbt functionality.
-        For "big ideas" about future capabilities of dbt, we ask that you open a
-        [discussion](https://github.com/dbt-labs/dbt-core/discussions) in the "Ideas" category instead.
-      options:
-        - label: I have read the [expectations for open source contributors](https://docs.getdbt.com/docs/contributing/oss-expectations)
-          required: true
-        - label: I have searched the existing issues, and I could not find an existing issue for this feature
-          required: true
-        - label: I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion
-          required: true
-  - type: textarea
-    attributes:
-      label: Describe the feature
-      description: A clear and concise description of what you want to happen.
-    validations:
-      required: true
-  - type: textarea
-    attributes:
-      label: Describe alternatives you've considered
-      description: |
-        A clear and concise description of any alternative solutions or features you've considered.
-    validations:
-      required: false
-  - type: textarea
-    attributes:
-      label: Who will this benefit?
-      description: |
-        What kind of use case will this feature be useful for? Please be specific and provide examples, this will help us prioritize properly.
-    validations:
-      required: false
-  - type: input
-    attributes:
-      label: Are you interested in contributing this feature?
-      description: Let us know if you want to write some code, and how we can help.
-    validations:
-      required: false
-  - type: textarea
-    attributes:
-      label: Anything else?
-      description: |
-        Links? References? Anything that will give us more context about the feature you are suggesting!
-    validations:
-      required: false

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,23 @@
+---
+name: Feature request
+about: Suggest an idea for dbt
+title: ''
+labels: enhancement, triage
+assignees: ''
+
+---
+
+### Describe the feature
+A clear and concise description of what you want to happen.
+
+### Describe alternatives you've considered
+A clear and concise description of any alternative solutions or features you've considered.
+
+### Additional context
+Is this feature database-specific? Which database(s) is/are relevant? Please include any other relevant context here.
+
+### Who will this benefit?
+What kind of use case will this feature be useful for? Please be specific and provide examples, this will help us prioritize properly.
+
+### Are you interested in contributing this feature?
+Let us know if you want to write some code, and how we can help.

.github/ISSUE_TEMPLATE/final-minor-version-release.md

@@ -0,0 +1,28 @@
+---
+name: Final minor version release
+about: Creates a tracking checklist of items for a final minor version release
+title: "[Tracking] v#.##.# final release "
+labels: 'release'
+assignees: ''
+
+---
+
+### Release Core
+- [ ] [Engineering] Verify all necessary changes exist on the release branch
+- [ ] [Engineering] Follow [dbt-release workflow](https://www.notion.so/dbtlabs/Releasing-b97c5ea9a02949e79e81db3566bbc8ef#03ff37da697d4d8ba63d24fae1bfa817) 
+- [ ] [Product] Merge `next` into `current` for docs.getdbt.com
+
+### Release Cloud
+- [ ] [Engineering] Create a platform issue to update dbt Cloud and verify it is completed. [Example issue](https://github.com/dbt-labs/dbt-cloud/issues/3481)
+- [ ] [Engineering] Determine if schemas have changed. If so, generate new schemas and push to schemas.getdbt.com
+
+### Announce
+- [ ] [Product] Update discourse
+- [ ] [Product] Announce in dbt Slack
+
+### Post-release
+- [ ] [Engineering] [Bump plugin versions](https://www.notion.so/dbtlabs/Releasing-b97c5ea9a02949e79e81db3566bbc8ef#f01854e8da3641179fbcbe505bdf515c) (dbt-spark + dbt-presto), add compatibility as needed
+   - [ ]  [Spark](https://github.com/dbt-labs/dbt-spark) 
+   - [ ]  [Presto](https://github.com/dbt-labs/dbt-presto)
+- [ ] [Engineering] Create a platform issue to update dbt-spark versions to dbt Cloud. [Example issue](https://github.com/dbt-labs/dbt-cloud/issues/3481)
+- [ ] [Product] Release new version of dbt-utils with new dbt version compatibility. If there are breaking changes requiring a minor version, plan upgrades of other packages that depend on dbt-utils.

.github/ISSUE_TEMPLATE/implementation-ticket.yml

@@ -1,58 +0,0 @@
-name: 🛠️ Implementation
-description: This is an implementation ticket intended for use by the maintainers of dbt-core
-title: "[<project>] <title>"
-labels: ["user docs"]
-body:
-  - type: markdown
-    attributes:
-      value: This is an implementation ticket intended for use by the maintainers of dbt-core
-  - type: checkboxes
-    attributes:
-      label: Housekeeping
-      description: >
-        A couple friendly reminders:
-          1. Remove the `user docs` label if the scope of this work does not require changes to https://docs.getdbt.com/docs: no end-user interface (e.g. yml spec, CLI, error messages, etc) or functional changes
-          2. Link any blocking issues in the "Blocked on" field under the "Core devs & maintainers" project.
-      options:
-        - label: I am a maintainer of dbt-core
-          required: true
-  - type: textarea
-    attributes:
-      label: Short description
-      description: |
-        Describe the scope of the ticket, a high-level implementation approach and any tradeoffs to consider
-    validations:
-      required: true
-  - type: textarea
-    attributes:
-      label: Acceptance criteria
-      description: |
-        What is the definition of done for this ticket? Include any relevant edge cases and/or test cases
-    validations:
-      required: true
-  - type: textarea
-    attributes:
-      label: Impact to Other Teams
-      description: |
-        Will this change impact other teams?  Include details of the kinds of changes required (new tests, code changes, related tickets) and _add the relevant `Impact:[team]` label_.
-      placeholder: |
-        Example: This change impacts `dbt-redshift` because the tests will need to be modified.  The `Impact:[Adapter]` label has been added.
-    validations:
-      required: true
-  - type: textarea
-    attributes:
-      label: Will backports be required?
-      description: |
-        Will this change need to be backported to previous versions?  Add details, possible blockers to backporting and _add the relevant backport labels `backport 1.x.latest`_
-      placeholder: |
-        Example: Backport to 1.6.latest, 1.5.latest and 1.4.latest.  Since 1.4 isn't using click, the backport may be complicated. The `backport 1.6.latest`, `backport 1.5.latest` and `backport 1.4.latest` labels have been added.
-    validations:
-      required: true
-  - type: textarea
-    attributes:
-      label: Context
-      description: |
-        Provide the "why", motivation, and alternative approaches considered -- linking to previous refinement issues, spikes, Notion docs as appropriate
-          validations:
-    validations:
-      required: false

.github/ISSUE_TEMPLATE/rc-minor-version-release copy.md

@@ -0,0 +1,29 @@
+---
+name: RC minor version release
+about: Creates a tracking checklist of items for a RC minor version release
+title: "[Tracking] v#.##.#RC# release "
+labels: 'release'
+assignees: ''
+
+---
+
+### Release Core
+- [ ] [Engineering] Verify all necessary changes exist on the release branch
+- [ ] [Engineering] Follow [dbt-release workflow](https://www.notion.so/dbtlabs/Releasing-b97c5ea9a02949e79e81db3566bbc8ef#03ff37da697d4d8ba63d24fae1bfa817) 
+- [ ] [Product] Update migration guide (next.docs.getdbt.com)
+
+### Release Cloud
+- [ ] [Engineering] Create a platform issue to update dbt Cloud and verify it is completed. [Example issue](https://github.com/dbt-labs/dbt-cloud/issues/3481)
+- [ ] [Engineering] Determine if schemas have changed. If so, generate new schemas and push to schemas.getdbt.com
+
+### Announce
+- [ ] [Product] Publish discourse
+- [ ] [Product] Announce in dbt Slack
+
+### Post-release
+- [ ] [Engineering] [Bump plugin versions](https://www.notion.so/dbtlabs/Releasing-b97c5ea9a02949e79e81db3566bbc8ef#f01854e8da3641179fbcbe505bdf515c) (dbt-spark + dbt-presto), add compatibility as needed
+   - [ ]  [Spark](https://github.com/dbt-labs/dbt-spark) 
+   - [ ]  [Presto](https://github.com/dbt-labs/dbt-presto)
+- [ ] [Engineering] Create a platform issue to update dbt-spark versions to dbt Cloud. [Example issue](https://github.com/dbt-labs/dbt-cloud/issues/3481)
+- [ ] [Product] Release new version of dbt-utils with new dbt version compatibility. If there are breaking changes requiring a minor version, plan upgrades of other packages that depend on dbt-utils.
+- [ ] [Engineering] Create an epic for the final release

.github/ISSUE_TEMPLATE/regression-report.yml

@@ -1,93 +0,0 @@
-name: ☣️ Regression
-description: Report a regression you've observed in a newer version of dbt
-title: "[Regression] <title>"
-labels: ["bug", "regression", "triage"]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Thanks for taking the time to fill out this regression report!
-  - type: checkboxes
-    attributes:
-      label: Is this a regression in a recent version of dbt-core?
-      description: >
-        A regression is when documented functionality works as expected in an older version of dbt-core,
-        and no longer works after upgrading to a newer version of dbt-core
-      options:
-        - label: I believe this is a regression in dbt-core functionality
-          required: true
-        - label: I have searched the existing issues, and I could not find an existing issue for this regression
-          required: true
-  - type: textarea
-    attributes:
-      label: Current Behavior
-      description: A concise description of what you're experiencing.
-    validations:
-      required: true
-  - type: textarea
-    attributes:
-      label: Expected/Previous Behavior
-      description: A concise description of what you expected to happen.
-    validations:
-      required: true
-  - type: textarea
-    attributes:
-      label: Steps To Reproduce
-      description: Steps to reproduce the behavior.
-      placeholder: |
-        1. In this environment...
-        2. With this config...
-        3. Run '...'
-        4. See error...
-    validations:
-      required: true
-  - type: textarea
-    id: logs
-    attributes:
-      label: Relevant log output
-      description: |
-        If applicable, log output to help explain your problem.
-      render: shell
-    validations:
-      required: false
-  - type: textarea
-    attributes:
-      label: Environment
-      description: |
-        examples:
-          - **OS**: Ubuntu 20.04
-          - **Python**: 3.9.12 (`python3 --version`)
-          - **dbt-core (working version)**: 1.1.1 (`dbt --version`)
-          - **dbt-core (regression version)**: 1.2.0 (`dbt --version`)
-      value: |
-        - OS:
-        - Python:
-        - dbt (working version):
-        - dbt (regression version):
-      render: markdown
-    validations:
-      required: true
-  - type: dropdown
-    id: database
-    attributes:
-      label: Which database adapter are you using with dbt?
-      description: If the regression is specific to the database or adapter, please open the issue in that adapter's repository instead
-      multiple: true
-      options:
-        - postgres
-        - redshift
-        - snowflake
-        - bigquery
-        - spark
-        - other (mention it in "Additional Context")
-    validations:
-      required: false
-  - type: textarea
-    attributes:
-      label: Additional Context
-      description: |
-        Links? References? Anything that will give us more context about the issue you are encountering!
-
-        Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.
-    validations:
-      required: false

.github/_README.md

@@ -1,216 +0,0 @@
-<!-- GitHub will publish this readme on the main repo page if the name is `README.md` so we've added the leading underscore to prevent this -->
-<!-- Do not rename this file `README.md` -->
-<!-- See https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes -->
-
-## What are GitHub Actions?
-
-GitHub Actions are used for many different purposes.  We use them to run tests in CI, validate PRs are in an expected state, and automate processes.
-
-- [Overview of GitHub Actions](https://docs.github.com/en/actions/learn-github-actions/understanding-github-actions)
-- [What's a workflow?](https://docs.github.com/en/actions/using-workflows/about-workflows)
-- [GitHub Actions guides](https://docs.github.com/en/actions/guides)
-
-___
-
-## Where do actions and workflows live
-
-We try to maintain actions that are shared across repositories in a single place so that necesary changes can be made in a single place.
-
-[dbt-labs/actions](https://github.com/dbt-labs/actions/) is the central repository of actions and workflows we use across repositories.
-
-GitHub Actions also live locally within a repository.  The workflows can be found at `.github/workflows` from the root of the repository.  These should be specific to that code base.
-
-Note: We are actively moving actions into the central Action repository so there is currently some duplication across repositories.
-
-___
-
-## Basics of Using Actions
-
-### Viewing Output
-
-- View the detailed action output for your PR in the **Checks** tab of the PR.  This only shows the most recent run.  You can also view high level **Checks** output at the bottom on the PR.
-
-- View _all_ action output for a repository from the [**Actions**](https://github.com/dbt-labs/dbt-core/actions) tab.  Workflow results last 1 year.  Artifacts last 90 days, unless specified otherwise in individual workflows.
-
-  This view often shows what seem like duplicates of the same workflow.  This occurs when files are renamed but the workflow name has not changed.  These are in fact _not_ duplicates.
-
-  You can see the branch the workflow runs from in this view.  It is listed in the table between the workflow name and the time/duration of the run.  When blank, the workflow is running in the context of the  `main` branch.
-
-### How to view what workflow file is being referenced from a run
-
-- When viewing the output of a specific workflow run, click the 3 dots at the top right of the display.  There will be an option to `View workflow file`.
-
-### How to manually run a workflow
-
-- If a workflow has the `on: workflow_dispatch` trigger, it can be manually triggered
-- From the [**Actions**](https://github.com/dbt-labs/dbt-core/actions) tab, find the workflow you want to run, select it and fill in any inputs requied.  That's it!
-
-### How to re-run jobs
-
-- Some actions cannot be rerun in the GitHub UI.  Namely the snyk checks and the cla check.  Snyk checks are rerun by closing and reopening the PR.  You can retrigger the cla check by commenting on the PR with `@cla-bot check`
-
-___
-
-## General Standards
-
-### Permissions
-- By default, workflows have read permissions in the repository for the contents scope only when no permissions are explicitly set.
-- It is best practice to always define the permissions explicitly.  This will allow actions to continue to work when the default permissions on the repository are changed.  It also allows explicit grants of the least permissions possible.
-- There are a lot of permissions available.  [Read up on them](https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs) if you're unsure what to use.
-
-```yaml
-permissions:
-  contents: read
-  pull-requests: write
-```
-
-### Secrets
-- When to use a [Personal Access Token (PAT)](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token) vs the [GITHUB_TOKEN](https://docs.github.com/en/actions/security-guides/automatic-token-authentication) generated for the action?
-
-    The `GITHUB_TOKEN` is used by default.  In most cases it is sufficient for what you need.
-
-    If you expect the workflow to result in a commit to that should retrigger workflows, you will need to use a Personal Access Token for the bot to commit the file. When using the GITHUB_TOKEN, the resulting commit will not trigger another GitHub Actions Workflow run. This is due to limitations set by GitHub. See [the docs](https://docs.github.com/en/actions/security-guides/automatic-token-authentication#using-the-github_token-in-a-workflow) for a more detailed explanation.
-
-    For example, we must use a PAT in our workflow to commit a new changelog yaml file for bot PRs.  Once the file has been committed to the branch, it should retrigger the check to validate that a changelog exists on the PR.  Otherwise, it would stay in a failed state since the check would never retrigger.
-
-### Triggers
-You can configure your workflows to run when specific activity on GitHub happens, at a scheduled time, or when an event outside of GitHub occurs.  Read more details in the [GitHub docs](https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows).
-
-These triggers are under the `on` key of the workflow and more than one can be listed.
-
-```yaml
-on:
-  push:
-    branches:
-      - "main"
-      - "*.latest"
-      - "releases/*"
-  pull_request:
-    # catch when the PR is opened with the label or when the label is added
-    types: [opened, labeled]
-  workflow_dispatch:
-```
-
-Some triggers of note that we use:
-
-- `push` - Runs your workflow when you push a commit or tag.
-- `pull_request` - Runs your workflow when activity on a pull request in the workflow's repository occurs.  Takes in a list of activity types (opened, labeled, etc) if appropriate.
-- `pull_request_target` - Same as `pull_request` but runs in the context of the PR target branch.
-- `workflow_call` - used with reusable workflows.  Triggered by another workflow calling it.
-- `workflow_dispatch` - Gives the ability to manually trigger a workflow from the GitHub API, GitHub CLI, or GitHub browser interface.
-
-
-### Basic Formatting
-- Add a description of what your workflow does at the top in this format
-
-  ```
-  # **what?**
-  # Describe what the action does.
-
-  # **why?**
-  # Why does this action exist?
-
-  # **when?**
-  # How/when will it be triggered?
-  ```
-
-- Leave blank lines between steps and jobs
-
-  ```yaml
-  jobs:
-    dependency_changelog:
-      runs-on: ubuntu-latest
-
-      steps:
-      - name: Get File Name Timestamp
-        id: filename_time
-        uses: nanzm/get-time-action@v1.1
-        with:
-          format: 'YYYYMMDD-HHmmss'
-
-      - name: Get File Content Timestamp
-        id: file_content_time
-        uses: nanzm/get-time-action@v1.1
-        with:
-          format: 'YYYY-MM-DDTHH:mm:ss.000000-05:00'
-
-      - name: Generate Filepath
-        id: fp
-        run: |
-          FILEPATH=.changes/unreleased/Dependencies-${{ steps.filename_time.outputs.time }}.yaml
-          echo "FILEPATH=$FILEPATH" >> $GITHUB_OUTPUT
-  ```
-
-- Print out all variables you will reference as the first step of a job.  This allows for easier debugging.  The first job should log all inputs.  Subsequent jobs should reference outputs of other jobs, if present.
-
-  When possible, generate variables at the top of your workflow in a single place to reference later.  This is not always strictly possible since you may generate a value to be used later mid-workflow.
-
-  Be sure to use quotes around these logs so special characters are not interpreted.
-
-  ```yaml
-  job1:
-    - name: "[DEBUG] Print Variables"
-      run: |
-        echo "all variables defined as inputs"
-        echo "The last commit sha in the release: ${{ inputs.sha }}"
-        echo "The release version number:         ${{ inputs.version_number }}"
-        echo "The changelog_path:                 ${{ inputs.changelog_path }}"
-        echo "The build_script_path:              ${{ inputs.build_script_path }}"
-        echo "The s3_bucket_name:                 ${{ inputs.s3_bucket_name }}"
-        echo "The package_test_command:           ${{ inputs.package_test_command }}"
-
-    # collect all the variables that need to be used in subsequent jobs
-    - name: Set Variables
-      id: variables
-      run: |
-        echo "important_path='performance/runner/Cargo.toml'" >> $GITHUB_OUTPUT
-        echo "release_id=${{github.event.inputs.release_id}}" >> $GITHUB_OUTPUT
-        echo "open_prs=${{github.event.inputs.open_prs}}" >> $GITHUB_OUTPUT
-
-  job2:
-    needs: [job1]
-      - name: "[DEBUG] Print Variables"
-      run: |
-        echo "all variables defined in job1 > Set Variables > outputs"
-        echo "important_path: ${{ needs.job1.outputs.important_path }}"
-        echo "release_id:     ${{ needs.job1.outputs.release_id }}"
-        echo "open_prs:       ${{ needs.job1.outputs.open_prs }}"
-  ```
-
-- When it's not obvious what something does, add a comment!
-
-___
-
-## Tips
-
-### Context
-- The [GitHub CLI](https://cli.github.com/) is available in the default runners
-- Actions run in your context.  ie, using an action from the marketplace that uses the GITHUB_TOKEN uses the GITHUB_TOKEN generated by your workflow run.
-
-### Actions from the Marketplace
-- Don’t use external actions for things that can easily be accomplished manually.
-- Always read through what an external action does before using it!  Often an action in the GitHub Actions Marketplace can be replaced with a few lines in bash.  This is much more maintainable (and won’t change under us) and clear as to what’s actually happening.  It also prevents any
-- Pin actions _we don't control_ to tags.
-
-### Connecting to AWS
-- Authenticate with the aws managed workflow
-
-  ```yaml
-  - name: Configure AWS credentials from Test account
-    uses: aws-actions/configure-aws-credentials@v2
-    with:
-      aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
-      aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
-      aws-region: us-east-1
-  ```
-
-- Then access with the aws command that comes installed on the action runner machines
-
-  ```yaml
-  - name: Copy Artifacts from S3 via CLI
-    run: aws s3 cp ${{ env.s3_bucket }} . --recursive
-  ```
-
-### Testing
-
-- Depending on what your action does, you may be able to use [`act`](https://github.com/nektos/act) to test the action locally.  Some features of GitHub Actions do not work with `act`, among those are reusable workflows.  If you can't use `act`, you'll have to push your changes up before being able to test.  This can be slow.

.github/actions/latest-wrangler/Dockerfile

@@ -1,14 +0,0 @@
-FROM python:3-slim AS builder
-ADD . /app
-WORKDIR /app
-
-# We are installing a dependency here directly into our app source dir
-RUN pip install --target=/app requests packaging
-
-# A distroless container image with Python and some basics like SSL certificates
-# https://github.com/GoogleContainerTools/distroless
-FROM gcr.io/distroless/python3-debian10
-COPY --from=builder /app /app
-WORKDIR /app
-ENV PYTHONPATH /app
-CMD ["/app/main.py"]

.github/actions/latest-wrangler/README.md

@@ -1,50 +0,0 @@
-# Github package 'latest' tag wrangler for containers
-## Usage
-
-Plug in the necessary inputs to determine if the container being built should be tagged 'latest; at the package level, for example `dbt-redshift:latest`.
-
-## Inputs
-| Input | Description |
-| - | - |
-| `package` | Name of the GH package to check against |
-| `new_version` | Semver of new container |
-| `gh_token` | GH token with package read scope|
-| `halt_on_missing` | Return non-zero exit code if requested package does not exist. (defaults to false)|
-
-
-## Outputs
-| Output | Description |
-| - | - |
-| `latest` | Wether or not the new container should be tagged 'latest'|
-| `minor_latest` | Wether or not the new container should be tagged major.minor.latest |
-
-## Example workflow
-```yaml
-name: Ship it!
-on:
-  workflow_dispatch:
-    inputs:
-      package:
-       description: The package to publish
-       required: true
-      version_number:
-       description: The version number
-       required: true
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    steps:
-    - uses: actions/checkout@v3
-    - name: Wrangle latest tag
-      id: is_latest
-      uses: ./.github/actions/latest-wrangler
-      with:
-        package: ${{ github.event.inputs.package }}
-        new_version: ${{ github.event.inputs.new_version }}
-        gh_token: ${{ secrets.GITHUB_TOKEN }}
-    - name: Print the results
-      run: |
-        echo "Is it latest?  Survey says: ${{ steps.is_latest.outputs.latest }} !"
-        echo "Is it minor.latest?  Survey says: ${{ steps.is_latest.outputs.minor_latest }} !"
-```

.github/actions/latest-wrangler/action.yml

@@ -1,20 +0,0 @@
-name: "Github package 'latest' tag wrangler for containers"
-description: "Determines wether or not a given dbt container should be given a bare 'latest' tag (I.E. dbt-core:latest)"
-inputs:
-  package_name:
-    description: "Package to check (I.E. dbt-core, dbt-redshift, etc)"
-    required: true
-  new_version:
-    description: "Semver of the container being built (I.E. 1.0.4)"
-    required: true
-  gh_token:
-    description: "Auth token for github (must have view packages scope)"
-    required: true
-outputs:
-  latest:
-    description: "Wether or not built container should be tagged latest (bool)"
-  minor_latest:
-    description: "Wether or not built container should be tagged minor.latest (bool)"
-runs:
-  using: "docker"
-  image: "Dockerfile"