update to use Docs object

Make docs a dataclass instead of a Dict
Merge branch 'feature/custom-node-colors-dbt_project' of github.com:dbt-labs/dbt-core into feature/custom-node-colors-dbt_project
2025-12-19 19:11:27 +00:00 · 2022-07-27 13:34:23 -05:00 · 2022-07-26 19:38:22 +02:00 · 2022-07-20 12:51:29 +02:00 · 2022-07-20 12:44:01 +02:00 · 2022-07-20 12:43:09 +02:00
1662 changed files with 65593 additions and 169318 deletions
--- a/.bumpversion.cfg
+++ b/.bumpversion.cfg
@@ -1,19 +1,13 @@
 [bumpversion]
-current_version = 1.9.0a1
-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 = 1.3.0a1
+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}
+	{major}.{minor}.{patch}{prekind}{pre}
 	{major}.{minor}.{patch}
 commit = False
 tag = False
@@ -27,11 +21,19 @@ values =
 	rc
 	final

-[bumpversion:part:num]
+[bumpversion:part:pre]
 first_value = 1

-[bumpversion:part:nightly]
-
 [bumpversion:file:core/setup.py]

 [bumpversion:file:core/dbt/version.py]
+
+[bumpversion:file:plugins/postgres/setup.py]
+
+[bumpversion:file:plugins/postgres/dbt/adapters/postgres/__version__.py]
+
+[bumpversion:file:docker/Dockerfile]
+
+[bumpversion:file:tests/adapter/setup.py]
+
+[bumpversion:file:tests/adapter/dbt/tests/adapter/__version__.py]
--- a/.changes/0.0.0.md
+++ b/.changes/0.0.0.md
@@ -3,11 +3,6 @@
 For information on prior major and minor releases, see their changelogs:


-* [1.7](https://github.com/dbt-labs/dbt-core/blob/1.7.latest/CHANGELOG.md)
-* [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)
--- a/.changes/header.tpl.md
+++ b/.changes/header.tpl.md
@@ -1,6 +1,6 @@
 # dbt Core Changelog

- This file provides a full account of all changes to `dbt-core`
+- 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)
--- a/Changes-20231206-192442.yaml
+++ b/Changes-20231206-192442.yaml
@@ -1,6 +0,0 @@
-kind: Breaking Changes
-body: Fix changing the current working directory when using dpt deps, clean and init.
-time: 2023-12-06T19:24:42.575372+09:00
-custom:
-  Author: rariyama
-  Issue: "8997"
--- a/.changes/unreleased/Dependencies-20240509-093717.yaml
+++ b/.changes/unreleased/Dependencies-20240509-093717.yaml
@@ -1,6 +0,0 @@
-kind: Dependencies
-body: Remove logbook dependency
-time: 2024-05-09T09:37:17.745129-05:00
-custom:
-  Author: emmyoop
-  Issue: "8027"
--- a/.changes/unreleased/Dependencies-20240820-131909.yaml
+++ b/.changes/unreleased/Dependencies-20240820-131909.yaml
@@ -1,7 +0,0 @@
-kind: Dependencies
-body: Increase supported version range for dbt-semantic-interfaces. Needed to support
-  custom calendar features.
-time: 2024-08-20T13:19:09.015225-07:00
-custom:
-  Author: courtneyholcomb
-  Issue: "9265"
--- a/.changes/unreleased/Docs-20240311-140344.yaml
+++ b/.changes/unreleased/Docs-20240311-140344.yaml
@@ -1,6 +0,0 @@
-kind: Docs
-body: Enable display of unit tests
-time: 2024-03-11T14:03:44.490834-04:00
-custom:
-  Author: gshank
-  Issue: "501"
--- a/.changes/unreleased/Docs-20240501-021050.yaml
+++ b/.changes/unreleased/Docs-20240501-021050.yaml
@@ -1,6 +0,0 @@
-kind: Docs
-body: Unit tests not rendering
-time: 2024-05-01T02:10:50.987412+02:00
-custom:
-  Author: aranke
-  Issue: "506"
--- a/.changes/unreleased/Docs-20240516-223036.yaml
+++ b/.changes/unreleased/Docs-20240516-223036.yaml
@@ -1,6 +0,0 @@
-kind: Docs
-body: Add support for Saved Query node
-time: 2024-05-16T22:30:36.206492-07:00
-custom:
-  Author: ChenyuLInx
-  Issue: "486"
--- a/.changes/unreleased/Docs-20240613-151048.yaml
+++ b/.changes/unreleased/Docs-20240613-151048.yaml
@@ -1,6 +0,0 @@
-kind: Docs
-body: Fix npm security vulnerabilities as of June 2024
-time: 2024-06-13T15:10:48.301989+01:00
-custom:
-    Author: aranke
-    Issue: "513"
--- a/.changes/unreleased/Features-20220715-035555.yaml
+++ b/.changes/unreleased/Features-20220715-035555.yaml
@@ -0,0 +1,8 @@
+kind: Features
+body: Add reusable function for retrying adapter connections. Utilize said function
+  to add retries for Postgres (and Redshift).
+time: 2022-07-15T03:55:55.270637265+02:00
+custom:
+  Author: tomasfarias
+  Issue: "5022"
+  PR: "5432"
--- a/.changes/unreleased/Features-20240506-175642.yaml
+++ b/.changes/unreleased/Features-20240506-175642.yaml
@@ -1,6 +0,0 @@
-kind: Features
-body: serialize inferred primary key
-time: 2024-05-06T17:56:42.757673-05:00
-custom:
-  Author: dave-connors-3
-  Issue: "9824"
--- a/.changes/unreleased/Features-20240507-162717.yaml
+++ b/.changes/unreleased/Features-20240507-162717.yaml
@@ -1,6 +0,0 @@
-kind: Features
-body: 'Add unit_test: selection method'
-time: 2024-05-07T16:27:17.047585-04:00
-custom:
-  Author: michelleark
-  Issue: "10053"
--- a/.changes/unreleased/Features-20240522-000309.yaml
+++ b/.changes/unreleased/Features-20240522-000309.yaml
@@ -1,7 +0,0 @@
-kind: Features
-body: Maximally parallelize dbt clone
-  in clone command"
-time: 2024-05-22T00:03:09.765977-04:00
-custom:
-  Author: michelleark
-  Issue: "7914"
--- a/.changes/unreleased/Features-20240527-124405.yaml
+++ b/.changes/unreleased/Features-20240527-124405.yaml
@@ -1,6 +0,0 @@
-kind: Features
-body: Add --host flag to dbt docs serve, defaulting to '127.0.0.1'
-time: 2024-05-27T12:44:05.040843-04:00
-custom:
-  Author: michelleark
-  Issue: "10229"
--- a/.changes/unreleased/Features-20240531-150816.yaml
+++ b/.changes/unreleased/Features-20240531-150816.yaml
@@ -1,6 +0,0 @@
-kind: Features
-body: Update data_test to accept arbitrary config options
-time: 2024-05-31T15:08:16.431966-05:00
-custom:
-    Author: McKnight-42
-    Issue: "10197"
--- a/.changes/unreleased/Features-20240606-112334.yaml
+++ b/.changes/unreleased/Features-20240606-112334.yaml
@@ -1,6 +0,0 @@
-kind: Features
-body: add pre_model and post_model hook calls to data and unit tests to be able to provide extra config options
-time: 2024-06-06T11:23:34.758675-05:00
-custom:
-    Author: McKnight-42
-    Issue: "10198"
--- a/.changes/unreleased/Features-20240617-103948.yaml
+++ b/.changes/unreleased/Features-20240617-103948.yaml
@@ -1,6 +0,0 @@
-kind: Features
-body: add --empty value to jinja context as flags.EMPTY
-time: 2024-06-17T10:39:48.275801-04:00
-custom:
-  Author: michelleark
-  Issue: "10317"
--- a/.changes/unreleased/Features-20240621-141635.yaml
+++ b/.changes/unreleased/Features-20240621-141635.yaml
@@ -1,6 +0,0 @@
-kind: Features
-body: Warning message for snapshot timestamp data types
-time: 2024-06-21T14:16:35.717637-04:00
-custom:
-  Author: gshank
-  Issue: "10234"
--- a/.changes/unreleased/Features-20240625-095107.yaml
+++ b/.changes/unreleased/Features-20240625-095107.yaml
@@ -1,6 +0,0 @@
-kind: Features
-body: Support cumulative_type_params & sub-daily granularities in semantic manifest.
-time: 2024-06-25T09:51:07.983248-07:00
-custom:
-  Author: courtneyholcomb
-  Issue: "10360"
--- a/.changes/unreleased/Features-20240627-162953.yaml
+++ b/.changes/unreleased/Features-20240627-162953.yaml
@@ -1,6 +0,0 @@
-kind: Features
-body: Add time_granularity to metric spec.
-time: 2024-06-27T16:29:53.500917-07:00
-custom:
-  Author: courtneyholcomb
-  Issue: "10376"
--- a/.changes/unreleased/Features-20240712-214546.yaml
+++ b/.changes/unreleased/Features-20240712-214546.yaml
@@ -1,6 +0,0 @@
-kind: Features
-body: Support standard schema/database fields for snapshots
-time: 2024-07-12T21:45:46.06011-04:00
-custom:
-  Author: gshank
-  Issue: "10301"
--- a/.changes/unreleased/Features-20240719-161841.yaml
+++ b/.changes/unreleased/Features-20240719-161841.yaml
@@ -1,6 +0,0 @@
-kind: Features
-body: Support ref and source in foreign key constraint expressions, bump dbt-common minimum to 1.6
-time: 2024-07-19T16:18:41.434278-04:00
-custom:
-  Author: michelleark
-  Issue: "8062"
--- a/.changes/unreleased/Features-20240722-202238.yaml
+++ b/.changes/unreleased/Features-20240722-202238.yaml
@@ -1,6 +0,0 @@
-kind: Features
-body: Support new semantic layer time spine configs to enable sub-daily granularity.
-time: 2024-07-22T20:22:38.258249-07:00
-custom:
-  Author: courtneyholcomb
-  Issue: "10475"
--- a/.changes/unreleased/Features-20240829-135320.yaml
+++ b/.changes/unreleased/Features-20240829-135320.yaml
@@ -1,6 +0,0 @@
-kind: Features
-body: Add support for behavior flags
-time: 2024-08-29T13:53:20.16122-04:00
-custom:
-  Author: mikealfare
-  Issue: "10618"
--- a/.changes/unreleased/Fixes-20220715-231148.yaml
+++ b/.changes/unreleased/Fixes-20220715-231148.yaml
@@ -0,0 +1,7 @@
+kind: Fixes
+body: Rename try to strict for more intuitiveness
+time: 2022-07-15T23:11:48.327928+12:00
+custom:
+  Author: jeremyyeo
+  Issue: "5475"
+  PR: "5477"
--- a/.changes/unreleased/Fixes-20230601-204157.yaml
+++ b/.changes/unreleased/Fixes-20230601-204157.yaml
@@ -1,6 +0,0 @@
-kind: Fixes
-body: Remove unused check_new method
-time: 2023-06-01T20:41:57.556342+02:00
-custom:
-  Author: kevinneville
-  Issue: "7586"
--- a/.changes/unreleased/Fixes-20240113-073615.yaml
+++ b/.changes/unreleased/Fixes-20240113-073615.yaml
@@ -1,6 +0,0 @@
-kind: Fixes
-body: Convert "Skipping model due to fail_fast" message to DEBUG level
-time: 2024-01-13T07:36:15.836294-00:00
-custom:
-  Author: scottgigante,nevdelap
-  Issue: "8774"
--- a/.changes/unreleased/Fixes-20240508-151127.yaml
+++ b/.changes/unreleased/Fixes-20240508-151127.yaml
@@ -1,7 +0,0 @@
-kind: Fixes
-body: 'Restore previous behavior for --favor-state: only favor defer_relation if not
-  selected in current command"'
-time: 2024-05-08T15:11:27.510912+02:00
-custom:
-  Author: jtcohen6
-  Issue: "10107"
--- a/.changes/unreleased/Fixes-20240509-091411.yaml
+++ b/.changes/unreleased/Fixes-20240509-091411.yaml
@@ -1,6 +0,0 @@
-kind: Fixes
-body: Unit test fixture (csv) returns null for empty value
-time: 2024-05-09T09:14:11.772709-04:00
-custom:
-  Author: michelleark
-  Issue: "9881"
--- a/.changes/unreleased/Fixes-20240516-153913.yaml
+++ b/.changes/unreleased/Fixes-20240516-153913.yaml
@@ -1,7 +0,0 @@
-kind: Fixes
-body: Fix json format log and --quiet for ls and jinja print by converting print call
-  to fire events
-time: 2024-05-16T15:39:13.896723-07:00
-custom:
-  Author: ChenyuLInx
-  Issue: "8756"
--- a/.changes/unreleased/Fixes-20240516-223510.yaml
+++ b/.changes/unreleased/Fixes-20240516-223510.yaml
@@ -1,6 +0,0 @@
-kind: Fixes
-body: Add resource type to saved_query
-time: 2024-05-16T22:35:10.287514-07:00
-custom:
-  Author: ChenyuLInx
-  Issue: "10168"
--- a/.changes/unreleased/Fixes-20240522-182855.yaml
+++ b/.changes/unreleased/Fixes-20240522-182855.yaml
@@ -1,7 +0,0 @@
-kind: Fixes
-body: 'Fix: Order-insensitive unit test equality assertion for expected/actual with
-  multiple nulls'
-time: 2024-05-22T18:28:55.91733-04:00
-custom:
-  Author: michelleark
-  Issue: "10167"
--- a/.changes/unreleased/Fixes-20240523-204251.yaml
+++ b/.changes/unreleased/Fixes-20240523-204251.yaml
@@ -1,6 +0,0 @@
-kind: Fixes
-body: Renaming or removing a contracted model should raise a BreakingChange warning/error
-time: 2024-05-23T20:42:51.033946-04:00
-custom:
-  Author: michelleark
-  Issue: "10116"
--- a/.changes/unreleased/Fixes-20240524-131135.yaml
+++ b/.changes/unreleased/Fixes-20240524-131135.yaml
@@ -1,6 +0,0 @@
-kind: Fixes
-body: prefer disabled project nodes to external node
-time: 2024-05-24T13:11:35.440443-04:00
-custom:
-  Author: michelleark
-  Issue: "10224"
--- a/.changes/unreleased/Fixes-20240605-111652.yaml
+++ b/.changes/unreleased/Fixes-20240605-111652.yaml
@@ -1,6 +0,0 @@
-kind: Fixes
-body: Fix issues with selectors and inline nodes
-time: 2024-06-05T11:16:52.187667-04:00
-custom:
-  Author: gshank
-  Issue: 8943 9269
--- a/.changes/unreleased/Fixes-20240607-134648.yaml
+++ b/.changes/unreleased/Fixes-20240607-134648.yaml
@@ -1,6 +0,0 @@
-kind: Fixes
-body: Fix snapshot config to work in yaml files
-time: 2024-06-07T13:46:48.383215-04:00
-custom:
-  Author: gshank
-  Issue: "4000"
--- a/.changes/unreleased/Fixes-20240610-132130.yaml
+++ b/.changes/unreleased/Fixes-20240610-132130.yaml
@@ -1,6 +0,0 @@
-kind: Fixes
-body: Improve handling of error when loading schema file list
-time: 2024-06-10T13:21:30.963371-04:00
-custom:
-  Author: gshank
-  Issue: "10284"
--- a/.changes/unreleased/Fixes-20240610-200522.yaml
+++ b/.changes/unreleased/Fixes-20240610-200522.yaml
@@ -1,6 +0,0 @@
-kind: Fixes
-body: Use model alias for the CTE identifier generated during ephemeral materialization
-time: 2024-06-10T20:05:22.510814008Z
-custom:
-    Author: jeancochrane
-    Issue: "5273"
--- a/.changes/unreleased/Fixes-20240612-124256.yaml
+++ b/.changes/unreleased/Fixes-20240612-124256.yaml
@@ -1,6 +0,0 @@
-kind: Fixes
-body: Saved Query node fail during skip
-time: 2024-06-12T12:42:56.329073-07:00
-custom:
-  Author: ChenyuLInx
-  Issue: "10029"
--- a/.changes/unreleased/Fixes-20240612-152139.yaml
+++ b/.changes/unreleased/Fixes-20240612-152139.yaml
@@ -1,6 +0,0 @@
-kind: Fixes
-body: Implement state:modified for saved queries
-time: 2024-06-12T15:21:39.851426-04:00
-custom:
-  Author: gshank
-  Issue: "10294"
--- a/.changes/unreleased/Fixes-20240613-183117.yaml
+++ b/.changes/unreleased/Fixes-20240613-183117.yaml
@@ -1,6 +0,0 @@
-kind: Fixes
-body: DOn't warn on `unit_test` config paths that are properly used
-time: 2024-06-13T18:31:17.486497-07:00
-custom:
-  Author: QMalcolm
-  Issue: "10311"
--- a/.changes/unreleased/Fixes-20240624-171729.yaml
+++ b/.changes/unreleased/Fixes-20240624-171729.yaml
@@ -1,6 +0,0 @@
-kind: Fixes
-body: Fix setting `silence` of `warn_error_options` via `dbt_project.yaml` flags
-time: 2024-06-24T17:17:29.464865-07:00
-custom:
-  Author: QMalcolm
-  Issue: "10160"
--- a/.changes/unreleased/Fixes-20240625-171737.yaml
+++ b/.changes/unreleased/Fixes-20240625-171737.yaml
@@ -1,7 +0,0 @@
-kind: Fixes
-body: Attempt to provide test fixture tables with all values to set types correctly
-  for comparisong with source tables
-time: 2024-06-25T17:17:37.514619-07:00
-custom:
-  Author: versusfacit
-  Issue: "10365"
--- a/.changes/unreleased/Fixes-20240627-154448.yaml
+++ b/.changes/unreleased/Fixes-20240627-154448.yaml
@@ -1,6 +0,0 @@
-kind: Fixes
-body: Limit data_tests deprecation to root_project
-time: 2024-06-27T15:44:48.579869-04:00
-custom:
-  Author: gshank
-  Issue: "9835"
--- a/.changes/unreleased/Fixes-20240709-172440.yaml
+++ b/.changes/unreleased/Fixes-20240709-172440.yaml
@@ -1,6 +0,0 @@
-kind: Fixes
-body: CLI flags should take precedence over env var flags
-time: 2024-07-09T17:24:40.918977-04:00
-custom:
-  Author: gshank
-  Issue: "10304"
--- a/.changes/unreleased/Fixes-20240714-100254.yaml
+++ b/.changes/unreleased/Fixes-20240714-100254.yaml
@@ -1,6 +0,0 @@
-kind: Fixes
-body: Fix typing for artifact schemas
-time: 2024-07-14T10:02:54.452099+09:00
-custom:
-    Author: nakamichiworks
-    Issue: "10442"
--- a/.changes/unreleased/Fixes-20240716-133703.yaml
+++ b/.changes/unreleased/Fixes-20240716-133703.yaml
@@ -1,6 +0,0 @@
-kind: Fixes
-body: Fix over deletion of generated_metrics in partial parsing
-time: 2024-07-16T13:37:03.49651-04:00
-custom:
-  Author: gshank
-  Issue: "10450"
--- a/.changes/unreleased/Fixes-20240716-171427.yaml
+++ b/.changes/unreleased/Fixes-20240716-171427.yaml
@@ -1,6 +0,0 @@
-kind: Fixes
-body: Fix error constructing warn_error_options
-time: 2024-07-16T17:14:27.837171-04:00
-custom:
-  Author: gshank
-  Issue: "10452"
--- a/.changes/unreleased/Fixes-20240728-221421.yaml
+++ b/.changes/unreleased/Fixes-20240728-221421.yaml
@@ -1,6 +0,0 @@
-kind: Fixes
-body: Do not update varchar column definitions if a contract exists
-time: 2024-07-28T22:14:21.67712-04:00
-custom:
-  Author: gshank
-  Issue: "10362"
--- a/.changes/unreleased/Fixes-20240731-095152.yaml
+++ b/.changes/unreleased/Fixes-20240731-095152.yaml
@@ -1,6 +0,0 @@
-kind: Fixes
-body: fix all_constraints access, disabled node parsing of non-uniquely named resources
-time: 2024-07-31T09:51:52.751135-04:00
-custom:
-  Author: michelleark gshank
-  Issue: "10509"
--- a/.changes/unreleased/Fixes-20240806-172110.yaml
+++ b/.changes/unreleased/Fixes-20240806-172110.yaml
@@ -1,6 +0,0 @@
-kind: Fixes
-body: Propagate measure label when using create_metrics
-time: 2024-08-06T17:21:10.265494-07:00
-custom:
-    Author: aliceliu
-    Issue: "10536"
--- a/.changes/unreleased/Fixes-20240806-194843.yaml
+++ b/.changes/unreleased/Fixes-20240806-194843.yaml
@@ -1,6 +0,0 @@
-kind: Fixes
-body: respect --quiet and --warn-error-options for flag deprecations
-time: 2024-08-06T19:48:43.399453-04:00
-custom:
-  Author: michelleark
-  Issue: "10105"
--- a/.changes/unreleased/Fixes-20240813-154235.yaml
+++ b/.changes/unreleased/Fixes-20240813-154235.yaml
@@ -1,6 +0,0 @@
-kind: Fixes
-body: Fix state:modified check for exports
-time: 2024-08-13T15:42:35.471685-07:00
-custom:
-    Author: aliceliu
-    Issue: "10138"
--- a/.changes/unreleased/Fixes-20240816-140807.yaml
+++ b/.changes/unreleased/Fixes-20240816-140807.yaml
@@ -1,6 +0,0 @@
-kind: Fixes
-body: Filter out empty nodes after graph selection to support consistent selection of nodes that depend on upstream public models
-time: 2024-08-16T14:08:07.426235-07:00
-custom:
-  Author: jtcohen6
-  Issue: "8987"
--- a/.changes/unreleased/Fixes-20240824-210903.yaml
+++ b/.changes/unreleased/Fixes-20240824-210903.yaml
@@ -1,6 +0,0 @@
-kind: Fixes
-body: Late render pre- and post-hooks configs in properties / schema YAML files
-time: 2024-08-24T21:09:03.252733-06:00
-custom:
-  Author: dbeatty10
-  Issue: "10603"
--- a/.changes/unreleased/Fixes-20240829-105701.yaml
+++ b/.changes/unreleased/Fixes-20240829-105701.yaml
@@ -1,7 +0,0 @@
-kind: Fixes
-body: Allow the use of env_var function in certain macros in which it was previously
-  unavailable.
-time: 2024-08-29T10:57:01.160613-04:00
-custom:
-  Author: peterallenwebb
-  Issue: "10609"
--- a/.changes/unreleased/Fixes-20240905-180248.yaml
+++ b/.changes/unreleased/Fixes-20240905-180248.yaml
@@ -1,6 +0,0 @@
-kind: Fixes
-body: 'Remove deprecation for tests: to data_tests: change'
-time: 2024-09-05T18:02:48.086421-04:00
-custom:
-  Author: gshank
-  Issue: "10564"
--- a/.changes/unreleased/Security-20240522-094540.yaml
+++ b/.changes/unreleased/Security-20240522-094540.yaml
@@ -1,6 +0,0 @@
-kind: Security
-body: Explicitly bind to localhost in docs serve
-time: 2024-05-22T09:45:40.748185-04:00
-custom:
-  Author: ChenyuLInx michelleark
-  Issue: "10209"
--- a/Hood-20240502-154430.yaml
+++ b/Hood-20240502-154430.yaml
@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Clear error message for Private package in dbt-core
-time: 2024-05-02T15:44:30.713097-07:00
-custom:
-  Author: ChenyuLInx
-  Issue: "10083"
--- a/Hood-20240506-145511.yaml
+++ b/Hood-20240506-145511.yaml
@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Enable use of context in serialization
-time: 2024-05-06T14:55:11.1812-04:00
-custom:
-  Author: gshank
-  Issue: "10093"
--- a/Hood-20240519-155946.yaml
+++ b/Hood-20240519-155946.yaml
@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Make RSS high water mark measurement more accurate on Linux
-time: 2024-05-19T15:59:46.700842315-04:00
-custom:
-    Author: peterallenwebb
-    Issue: "10177"
--- a/Hood-20240529-102814.yaml
+++ b/Hood-20240529-102814.yaml
@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Enable record filtering by type.
-time: 2024-05-29T10:28:14.547624-05:00
-custom:
-  Author: emmyoop
-  Issue: "10240"
--- a/Hood-20240618-140652.yaml
+++ b/Hood-20240618-140652.yaml
@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Remove IntermediateSnapshotNode
-time: 2024-06-18T14:06:52.618602-04:00
-custom:
-  Author: gshank
-  Issue: "10326"
--- a/Hood-20240701-131750.yaml
+++ b/Hood-20240701-131750.yaml
@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Additional logging for skipped ephemeral models
-time: 2024-07-01T13:17:50.827788-04:00
-custom:
-  Author: gshank
-  Issue: "10389"
--- a/Hood-20240716-184859.yaml
+++ b/Hood-20240716-184859.yaml
@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: bump black to 24.3.0
-time: 2024-07-16T18:48:59.651834-04:00
-custom:
-  Author: michelleark
-  Issue: "10454"
--- a/Hood-20240716-205703.yaml
+++ b/Hood-20240716-205703.yaml
@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: generate protos with protoc version 5.26.1
-time: 2024-07-16T20:57:03.332448-04:00
-custom:
-  Author: michelleark
-  Issue: "10457"
--- a/Hood-20240806-155406.yaml
+++ b/Hood-20240806-155406.yaml
@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Move from minimal-snowplow-tracker fork back to snowplow-tracker
-time: 2024-08-06T15:54:06.422444-04:00
-custom:
-  Author: peterallenwebb
-  Issue: "8409"
--- a/Hood-20240807-155652.yaml
+++ b/Hood-20240807-155652.yaml
@@ -1,7 +0,0 @@
-kind: Under the Hood
-body: Add group info to RunResultError, RunResultFailure, RunResultWarning log lines
-time: 2024-08-07T15:56:52.171199-05:00
-custom:
-  Author: aranke
-  Issue: ""
-  JiraID: "364"
--- a/Hood-20240809-130234.yaml
+++ b/Hood-20240809-130234.yaml
@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Improve speed of tree traversal when finding children, increasing build speed for some selectors
-time: 2024-08-09T13:02:34.759905-07:00
-custom:
-    Author: ttusing
-    Issue: "10434"
--- a/Hood-20240821-095516.yaml
+++ b/Hood-20240821-095516.yaml
@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Add test for sources tables with quotes
-time: 2024-08-21T09:55:16.038101-04:00
-custom:
-  Author: gshank
-  Issue: "10582"
--- a/Hood-20240827-105014.yaml
+++ b/Hood-20240827-105014.yaml
@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Additional type hints for `core/dbt/version.py`
-time: 2024-08-27T10:50:14.047859-05:00
-custom:
-  Author: QMalcolm
-  Issue: "10612"
--- a/Hood-20240827-113123.yaml
+++ b/Hood-20240827-113123.yaml
@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Fix typing issues in core/dbt/contracts/sql.py
-time: 2024-08-27T11:31:23.749912-05:00
-custom:
-  Author: QMalcolm
-  Issue: "10614"
--- a/Hood-20240827-114810.yaml
+++ b/Hood-20240827-114810.yaml
@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Fix type errors in `dbt/core/task/clean.py`
-time: 2024-08-27T11:48:10.438173-05:00
-custom:
-  Author: QMalcolm
-  Issue: "10616"
--- a/.changie.yaml
+++ b/.changie.yaml
@@ -4,93 +4,58 @@ 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}})
-
+changeFormat: '- {{.Body}} ([#{{.Custom.Issue}}](https://github.com/dbt-labs/dbt-core/issues/{{.Custom.Issue}}), [#{{.Custom.PR}}](https://github.com/dbt-labs/dbt-core/pull/{{.Custom.PR}}))'
 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
-  - label: Security
-
-newlines:
-  afterChangelogHeader: 1
-  afterKind: 1
-  afterChangelogVersion: 1
-  beforeKind: 1
-  endOfVersion: 1
-
+- label: Breaking Changes
+- label: Features
+- label: Fixes
+- label: Docs
+- label: Under the Hood
+- label: Dependencies
+- label: Security
 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
-
+  label: GitHub Issue Number
+  type: int
+  minLength: 4
+- key: PR
+  label: GitHub Pull Request Number
+  type: int
+  minLength: 4
 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 }}
+  {{- /* any names added to this list should be all lowercase for later matching purposes */}}
+  {{- $core_team := list "emmyoop" "nathaniel-may" "gshank" "leahwicz" "chenyulinx" "stu-k" "iknox-fa" "versusfacit" "mcknight-42" "jtcohen6" "dependabot" }}
  {{- range $change := .Changes }}
    {{- $authorList := splitList " " $change.Custom.Author }}
-    {{- /* loop through all authors for a single changelog */}}
+    {{- /* loop through all authors for a PR */}}
    {{- 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 }}
-          {{- $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 }}
-          {{- /* 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}}
+      {{- if not (has $authorLower $core_team)}}
+        {{- $pr := $change.Custom.PR }}
+        {{- /* check if this contributor has other PRs associated with them already */}}
+        {{- if hasKey $contributorDict $author }}
+          {{- $prList := get $contributorDict $author }}
+          {{- $prList = append $prList $pr  }}
+          {{- $contributorDict := set $contributorDict $author $prList }}
+        {{- else }}
+          {{- $prList := list $change.Custom.PR }}
+          {{- $contributorDict := set $contributorDict $author $prList }}
+        {{- 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}})
+  - [@{{$k}}](https://github.com/{{$k}}) ({{ range $index, $element := $v }}{{if $index}}, {{end}}[#{{$element}}](https://github.com/dbt-labs/dbt-core/pull/{{$element}}){{end}})
  {{- end }}
  {{- end }}
--- a/.flake8
+++ b/.flake8
@@ -7,9 +7,6 @@ ignore =
    W503 # makes Flake8 work like black
    W504
    E203 # makes Flake8 work like black
-    E704 # makes Flake8 work like black
    E741
    E501 # long line checking is done in black
-exclude = test/
-per-file-ignores =
-    */__init__.py: F401
+exclude = test
--- a/.gitattributes
+++ b/.gitattributes
@@ -1,6 +0,0 @@
-core/dbt/task/docs/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
--- a/.github/CODEOWNERS
+++ b/.github/CODEOWNERS
@@ -11,8 +11,33 @@

 # As a default for areas with no assignment,
 # the core team as a whole will be assigned
-*       @dbt-labs/core-team
+*       @dbt-labs/core

-### ARTIFACTS
+# Changes to GitHub configurations including Actions
+/.github/ @leahwicz

-/schemas/dbt                    @dbt-labs/cloud-artifacts
+# Language core modules
+/core/dbt/config/     @dbt-labs/core-language
+/core/dbt/context/    @dbt-labs/core-language
+/core/dbt/contracts/  @dbt-labs/core-language
+/core/dbt/deps/       @dbt-labs/core-language
+/core/dbt/parser/     @dbt-labs/core-language
+
+# Execution core modules
+/core/dbt/events/     @dbt-labs/core-execution @dbt-labs/core-language # eventually remove language but they have knowledge here now
+/core/dbt/graph/      @dbt-labs/core-execution
+/core/dbt/task/       @dbt-labs/core-execution
+
+# Adapter interface, scaffold, Postgres plugin
+/core/dbt/adapters    @dbt-labs/core-adapters
+/core/scripts/create_adapter_plugin.py    @dbt-labs/core-adapters
+/plugins/             @dbt-labs/core-adapters
+
+# Global project: default macros, including generic tests + materializations
+/core/dbt/include/global_project    @dbt-labs/core-execution @dbt-labs/core-adapters
+
+# 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
--- a/.github/ISSUE_TEMPLATE/bug-report.yml
+++ b/.github/ISSUE_TEMPLATE/bug-report.yml
@@ -9,33 +9,23 @@ body:
        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.
+      label: Is there an existing issue for this?
+      description: 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
+        - label: I have searched the existing issues
          required: true
  - type: textarea
    attributes:
      label: Current Behavior
      description: A concise description of what you're experiencing.
    validations:
-      required: true
+      required: false
  - type: textarea
    attributes:
      label: Expected Behavior
      description: A concise description of what you expected to happen.
    validations:
-      required: true
+      required: false
  - type: textarea
    attributes:
      label: Steps To Reproduce
@@ -46,7 +36,7 @@ body:
        3. Run '...'
        4. See error...
    validations:
-      required: true
+      required: false
  - type: textarea
    id: logs
    attributes:
@@ -62,8 +52,8 @@ body:
      description: |
        examples:
          - **OS**: Ubuntu 20.04
-          - **Python**: 3.9.12 (`python3 --version`)
-          - **dbt-core**: 1.1.1 (`dbt --version`)
+          - **Python**: 3.7.2 (`python --version`)
+          - **dbt**: 0.21.0 (`dbt --version`)
      value: |
        - OS:
        - Python:
@@ -74,15 +64,13 @@ body:
  - 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
+      label: What database are you using dbt with?
      multiple: true
      options:
        - postgres
        - redshift
        - snowflake
        - bigquery
-        - spark
        - other (mention it in "Additional Context")
    validations:
      required: false
--- a/.github/ISSUE_TEMPLATE/code-docs.yml
+++ b/.github/ISSUE_TEMPLATE/code-docs.yml
@@ -1,18 +0,0 @@
-name: 📄 Code docs
-description: Report an issue for markdown files within this repo, such as README, ARCHITECTURE, etc.
-title: "[Code docs] <title>"
-labels: ["triage"]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Thanks for taking the time to fill out this code docs issue!
-  - type: textarea
-    attributes:
-      label: Please describe the issue and your proposals.
-      description: |
-        Links? References? Anything that will give us more context about the issue you are encountering!
-
-        Tip: You can attach images by clicking this area to highlight it and then dragging files in.
-    validations:
-      required: false
--- a/.github/ISSUE_TEMPLATE/config.yml
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -1,17 +1,4 @@
-blank_issues_enabled: false
 contact_links:
-  - name: Documentation
-    url: https://github.com/dbt-labs/docs.getdbt.com/issues/new/choose
-    about: Problems and issues with dbt product documentation hosted on docs.getdbt.com. Issues for markdown files within this repo, such as README, should be opened using the "Code docs" template.
-  - 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
@@ -21,6 +8,9 @@ contact_links:
  - 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
+  - name: Ask a question or get support
+    url: https://docs.getdbt.com/docs/guides/getting-help
+    about: Ask a question or request support
+  - name: Questions on Stack Overflow
+    url: https://stackoverflow.com/questions/tagged/dbt
+    about: Look at questions/answers at Stack Overflow
--- a/.github/ISSUE_TEMPLATE/feature-request.yml
+++ b/.github/ISSUE_TEMPLATE/feature-request.yml
@@ -1,5 +1,5 @@
 name: ✨ Feature
-description: Propose a straightforward extension of dbt functionality
+description: Suggest an idea for dbt
 title: "[Feature] <title>"
 labels: ["enhancement", "triage"]
 body:
@@ -9,24 +9,18 @@ body:
        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.
+      label: Is there an existing feature request for this?
+      description: Please search to see if an issue already exists for the feature you would like.
+      options:
+        - label: I have searched the existing issues
+          required: true
+      label: Is this your first time opening an issue?
      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
+      label: Describe the Feature
      description: A clear and concise description of what you want to happen.
    validations:
      required: true
--- a/.github/ISSUE_TEMPLATE/implementation-ticket.yml
+++ b/.github/ISSUE_TEMPLATE/implementation-ticket.yml
@@ -1,67 +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: Suggested Tests
-      description: |
-        Provide scenarios to test.  Link to existing similar tests if appropriate.
-      placeholder: |
-         1. Test with no version specified in the schema file and use selection logic on a versioned model for a specific version.  Expect pass.
-         2. Test with a version specified in the schema file that is no valid.  Expect ParsingError.
-    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 and documentation as appropriate
-    validations:
-      required: false
--- a/.github/ISSUE_TEMPLATE/regression-report.yml
+++ b/.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
--- a/.github/_README.md
+++ b/.github/_README.md
@@ -1,217 +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
-
- From the UI you can rerun from failure
- 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.
--- a/.github/actions/latest-wrangler/README.md
+++ b/.github/actions/latest-wrangler/README.md
@@ -35,7 +35,7 @@ jobs:
  build:
    runs-on: ubuntu-latest
    steps:
-    - uses: actions/checkout@v3
+    - uses: actions/checkout@v1
    - name: Wrangle latest tag
      id: is_latest
      uses: ./.github/actions/latest-wrangler
--- a/.github/actions/latest-wrangler/action.yml
+++ b/.github/actions/latest-wrangler/action.yml
@@ -1,21 +1,20 @@
-name: "GitHub package `latest` tag wrangler for containers"
-description: "Determines if the published image should include `latest` tags"
-
+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 being published (i.e. `dbt-core`, `dbt-redshift`, etc.)"
+    description: "Package to check (I.E. dbt-core, dbt-redshift, etc)"
    required: true
  new_version:
-    description: "SemVer of the package being published (i.e. 1.7.2, 1.8.0a1, etc.)"
+    description: "Semver of the container being built (I.E. 1.0.4)"
    required: true
-  github_token:
-    description: "Auth token for GitHub (must have view packages scope)"
+  gh_token:
+    description: "Auth token for github (must have view packages scope)"
    required: true
-
 outputs:
-  tags:
-    description: "A list of tags to associate with this version"
-
+  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"
--- a/.github/actions/latest-wrangler/examples/example_workflow.yml
+++ b/.github/actions/latest-wrangler/examples/example_workflow.yml
@@ -13,7 +13,7 @@ jobs:
  build:
    runs-on: ubuntu-latest
    steps:
-    - uses: actions/checkout@v3
+    - uses: actions/checkout@v1
    - name: Wrangle latest tag
      id: is_latest
      uses: ./.github/actions/latest-wrangler
--- a/.github/actions/latest-wrangler/main.py
+++ b/.github/actions/latest-wrangler/main.py
@@ -1,71 +1,95 @@
 import os
-from packaging.version import Version, parse
-import requests
 import sys
-from typing import List
-
-
-def main():
-    package_name: str = os.environ["INPUT_PACKAGE_NAME"]
-    new_version: Version = parse(os.environ["INPUT_NEW_VERSION"])
-    github_token: str = os.environ["INPUT_GITHUB_TOKEN"]
-
-    response = _package_metadata(package_name, github_token)
-    published_versions = _published_versions(response)
-    new_version_tags = _new_version_tags(new_version, published_versions)
-    _register_tags(new_version_tags, package_name)
-
-
-def _package_metadata(package_name: str, github_token: str) -> requests.Response:
-    url = f"https://api.github.com/orgs/dbt-labs/packages/container/{package_name}/versions"
-    return requests.get(url, auth=("", github_token))
-
-
-def _published_versions(response: requests.Response) -> List[Version]:
-    package_metadata = response.json()
-    return [
-        parse(tag)
-        for version in package_metadata
-        for tag in version["metadata"]["container"]["tags"]
-        if "latest" not in tag
-    ]
-
-
-def _new_version_tags(new_version: Version, published_versions: List[Version]) -> List[str]:
-    # the package version is always a tag
-    tags = [str(new_version)]
-
-    # pre-releases don't get tagged with `latest`
-    if new_version.is_prerelease:
-        return tags
-
-    if new_version > max(published_versions):
-        tags.append("latest")
-
-    published_patches = [
-        version
-        for version in published_versions
-        if version.major == new_version.major and version.minor == new_version.minor
-    ]
-    if new_version > max(published_patches):
-        tags.append(f"{new_version.major}.{new_version.minor}.latest")
-
-    return tags
-
-
-def _register_tags(tags: List[str], package_name: str) -> None:
-    fully_qualified_tags = ",".join([f"ghcr.io/dbt-labs/{package_name}:{tag}" for tag in tags])
-    github_output = os.environ.get("GITHUB_OUTPUT")
-    with open(github_output, "at", encoding="utf-8") as gh_output:
-        gh_output.write(f"fully_qualified_tags={fully_qualified_tags}")
-
-
-def _validate_response(response: requests.Response) -> None:
-    message = response["message"]
-    if response.status_code != 200:
-        print(f"Call to GitHub API failed: {response.status_code} - {message}")
-        sys.exit(1)
-
+import requests
+from distutils.util import strtobool
+from typing import Union
+from packaging.version import parse, Version

 if __name__ == "__main__":
-    main()
+
+    # get inputs
+    package = os.environ["INPUT_PACKAGE"]
+    new_version = parse(os.environ["INPUT_NEW_VERSION"])
+    gh_token = os.environ["INPUT_GH_TOKEN"]
+    halt_on_missing = strtobool(os.environ.get("INPUT_HALT_ON_MISSING", "False"))
+
+    # get package metadata from github
+    package_request = requests.get(
+        f"https://api.github.com/orgs/dbt-labs/packages/container/{package}/versions",
+        auth=("", gh_token),
+    )
+    package_meta = package_request.json()
+
+    # Log info if we don't get a 200
+    if package_request.status_code != 200:
+        print(f"Call to GH API failed: {package_request.status_code} {package_meta['message']}")
+
+    # Make an early exit if there is no matching package in github
+    if package_request.status_code == 404:
+        if halt_on_missing:
+            sys.exit(1)
+        else:
+            # everything is the latest if the package doesn't exist
+            print(f"::set-output name=latest::{True}")
+            print(f"::set-output name=minor_latest::{True}")
+            sys.exit(0)
+
+    # TODO: verify package meta is "correct"
+    # https://github.com/dbt-labs/dbt-core/issues/4640
+
+    # map versions and tags
+    version_tag_map = {
+        version["id"]: version["metadata"]["container"]["tags"] for version in package_meta
+    }
+
+    # is pre-release
+    pre_rel = True if any(x in str(new_version) for x in ["a", "b", "rc"]) else False
+
+    # semver of current latest
+    for version, tags in version_tag_map.items():
+        if "latest" in tags:
+            # N.B. This seems counterintuitive, but we expect any version tagged
+            # 'latest' to have exactly three associated tags:
+            # latest, major.minor.latest, and major.minor.patch.
+            # Subtracting everything that contains the string 'latest' gets us
+            # the major.minor.patch which is what's needed for comparison.
+            current_latest = parse([tag for tag in tags if "latest" not in tag][0])
+        else:
+            current_latest = False
+
+    # semver of current_minor_latest
+    for version, tags in version_tag_map.items():
+        if f"{new_version.major}.{new_version.minor}.latest" in tags:
+            # Similar to above, only now we expect exactly two tags:
+            # major.minor.patch and major.minor.latest
+            current_minor_latest = parse([tag for tag in tags if "latest" not in tag][0])
+        else:
+            current_minor_latest = False
+
+    def is_latest(
+        pre_rel: bool, new_version: Version, remote_latest: Union[bool, Version]
+    ) -> bool:
+        """Determine if a given contaier should be tagged 'latest' based on:
+         - it's pre-release status
+         - it's version
+         - the version of a previously identified container tagged 'latest'
+
+        :param pre_rel: Wether or not the version of the new container is a pre-release
+        :param new_version: The version of the new container
+        :param remote_latest: The version of the previously identified container that's
+            already tagged latest or False
+        """
+        # is a pre-release = not latest
+        if pre_rel:
+            return False
+        # + no latest tag found = is latest
+        if not remote_latest:
+            return True
+        # + if remote version is lower than current = is latest, else not latest
+        return True if remote_latest <= new_version else False
+
+    latest = is_latest(pre_rel, new_version, current_latest)
+    minor_latest = is_latest(pre_rel, new_version, current_minor_latest)
+
+    print(f"::set-output name=latest::{latest}")
+    print(f"::set-output name=minor_latest::{minor_latest}")
--- a/.github/actions/setup-postgres-macos/action.yml
+++ b/.github/actions/setup-postgres-macos/action.yml
@@ -5,6 +5,7 @@ runs:
  steps:
    - shell: bash
      run: |
+        brew services start postgresql
        echo "Check PostgreSQL service is running"
        i=10
        COMMAND='pg_isready'
--- a/.github/actions/setup-postgres-windows/action.yml
+++ b/.github/actions/setup-postgres-windows/action.yml
@@ -2,8 +2,6 @@ name: "Set up postgres (windows)"
 description: "Set up postgres service on windows vm for dbt integration tests"
 runs:
  using: "composite"
-  env:
-    PQ_LIB_DIR: 'C:\Program Files\PostgreSQL\16\lib'
  steps:
    - shell: pwsh
      run: |
--- a/.github/dependabot.yml
+++ b/.github/dependabot.yml
@@ -11,6 +11,11 @@ updates:
    schedule:
      interval: "daily"
    rebase-strategy: "disabled"
+  - package-ecosystem: "pip"
+    directory: "/plugins/postgres"
+    schedule:
+      interval: "daily"
+    rebase-strategy: "disabled"

  # docker dependencies
  - package-ecosystem: "docker"
@@ -23,10 +28,3 @@ updates:
    schedule:
      interval: "weekly"
    rebase-strategy: "disabled"
-
-  # github dependencies
-  - package-ecosystem: "github-actions"
-    directory: "/"
-    schedule:
-      interval: "weekly"
-    rebase-strategy: "disabled"
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -1,33 +1,23 @@
-Resolves #
+resolves #

 <!---
-  Include the number of the issue addressed by this PR above, if applicable.
+  Include the number of the issue addressed by this PR above if applicable.
  PRs for code changes without an associated issue *will not be merged*.
  See CONTRIBUTING.md for more information.
-
-  Add the `user docs` label to this PR if it will need docs changes.  An 
-  issue will get opened in docs.getdbt.com upon successful merge of this PR.
 -->

-### Problem
+### Description

 <!---
-  Describe the problem this PR is solving. What is the application state
-  before this PR is merged?
-->
-
-### Solution
-
-<!---
-  Describe the way this PR solves the above problem. Add as much detail as you
-  can to help reviewers understand your changes. Include any alternatives and
-  tradeoffs you considered.
+  Describe the Pull Request here. Add any references and info to help reviewers
+  understand your changes. Include any tradeoffs you considered.
 -->

 ### Checklist

- [ ] I have read [the contributing guide](https://github.com/dbt-labs/dbt-core/blob/main/CONTRIBUTING.md) and understand what's expected of me.
- [ ] I have run this code in development, and it appears to resolve the stated issue.
- [ ] This PR includes tests, or tests are not required or relevant for this PR.
- [ ] This PR has no interface changes (e.g., macros, CLI, logs, JSON artifacts, config files, adapter interface, etc.) or this PR has already received feedback and approval from Product or DX.
- [ ] This PR includes [type annotations](https://docs.python.org/3/library/typing.html) for new and modified functions.
+- [ ] I have read [the contributing guide](https://github.com/dbt-labs/dbt-core/blob/main/CONTRIBUTING.md) and understand what's expected of me
+- [ ] I have signed the [CLA](https://docs.getdbt.com/docs/contributor-license-agreements)
+- [ ] I have run this code in development and it appears to resolve the stated issue
+- [ ] This PR includes tests, or tests are not required/relevant for this PR
+- [ ] I have [opened an issue to add/update docs](https://github.com/dbt-labs/docs.getdbt.com/issues/new/choose), or docs changes are not required/relevant for this PR
+- [ ] I have run `changie new` to [create a changelog entry](https://github.com/dbt-labs/dbt-core/blob/main/CONTRIBUTING.md#Adding-CHANGELOG-Entry)
--- a/.github/workflows/backport.yml
+++ b/.github/workflows/backport.yml
@@ -35,6 +35,6 @@ jobs:
      github.event.pull_request.merged
      && contains(github.event.label.name, 'backport')
    steps:
-      - uses: tibdex/backport@v2.0.4
+      - uses: tibdex/backport@v2.0.2
        with:
          github_token: ${{ secrets.GITHUB_TOKEN }}
--- a/.github/workflows/bot-changelog.yml
+++ b/.github/workflows/bot-changelog.yml
@@ -1,59 +0,0 @@
-# **what?**
-# When bots create a PR, this action will add a corresponding changie yaml file to that
-# PR when a specific label is added.
-#
-# The file is created off a template:
-#
-# kind: <per action matrix>
-# body: <PR title>
-# time: <current timestamp>
-# custom:
-#   Author: <PR User Login (generally the bot)>
-#   Issue: 4904
-#   PR: <PR number>
-#
-# **why?**
-# Automate changelog generation for more visability with automated bot PRs.
-#
-# **when?**
-# Once a PR is created, label should be added to PR before or after creation. You can also
-#  manually trigger this by adding the appropriate label at any time.
-#
-# **how to add another bot?**
-# Add the label and changie kind to the include matrix.  That's it!
-#
-
-name: Bot Changelog
-
-on:
-  pull_request:
-    # catch when the PR is opened with the label or when the label is added
-    types: [labeled]
-
-permissions:
-  contents: write
-  pull-requests: read
-
-jobs:
-  generate_changelog:
-    strategy:
-      matrix:
-        include:
-          - label: "dependencies"
-            changie_kind: "Dependencies"
-    runs-on: ubuntu-latest
-
-    steps:
-
-    - name: Create and commit changelog on bot PR
-      if: ${{ contains(github.event.pull_request.labels.*.name, matrix.label) }}
-      id: bot_changelog
-      uses: emmyoop/changie_bot@v1.1.0
-      with:
-        GITHUB_TOKEN: ${{ secrets.FISHTOWN_BOT_PAT }}
-        commit_author_name: "Github Build Bot"
-        commit_author_email: "<buildbot@fishtownanalytics.com>"
-        commit_message: "Add automated changelog yaml from template for bot PR"
-        changie_kind: ${{ matrix.changie_kind }}
-        label: ${{ matrix.label }}
-        custom_changelog_string: "custom:\n  Author: ${{ github.event.pull_request.user.login }}\n  Issue: ${{ github.event.pull_request.number }}"
--- a/.github/workflows/changelog-check.yml
+++ b/.github/workflows/changelog-check.yml
@@ -0,0 +1,78 @@
+# **what?**
+# Checks that a file has been committed under the /.changes directory
+# as a new CHANGELOG entry.  Cannot check for a specific filename as
+# it is dynamically generated by change type and timestamp.
+# This workflow should not require any secrets since it runs for PRs
+# from forked repos.
+# By default, secrets are not passed to workflows running from
+# a forked repo.
+
+# **why?**
+# Ensure code change gets reflected in the CHANGELOG.
+
+# **when?**
+# This will run for all PRs going into main and *.latest.  It will
+# run when they are opened, reopened, when any label is added or removed
+# and when new code is pushed to the branch.  The action will then get
+# skipped if the 'Skip Changelog' label is present is any of the labels.
+
+name: Check Changelog Entry
+
+on:
+  pull_request:
+    types: [opened, reopened, labeled, unlabeled, synchronize]
+  workflow_dispatch:
+
+defaults:
+  run:
+    shell: bash
+
+permissions:
+  contents: read
+  pull-requests: write
+
+env:
+  changelog_comment: 'Thank you for your pull request! We could not find a changelog entry for this change. 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).'
+
+jobs:
+  changelog:
+    name: changelog
+    if: "!contains(github.event.pull_request.labels.*.name, 'Skip Changelog')"
+
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Check if changelog file was added
+        # https://github.com/marketplace/actions/paths-changes-filter
+        # For each filter, it sets output variable named by the filter to the text:
+        #  'true' - if any of changed files matches any of filter rules
+        #  'false' - if none of changed files matches any of filter rules
+        # also, returns:
+        #  `changes` - JSON array with names of all filters matching any of the changed files
+        uses: dorny/paths-filter@v2
+        id: filter
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          filters: |
+            changelog:
+              - added: '.changes/unreleased/**.yaml'
+      - name: Check if comment already exists
+        uses: peter-evans/find-comment@v1
+        id: changelog_comment
+        with:
+          issue-number: ${{ github.event.pull_request.number }}
+          comment-author: 'github-actions[bot]'
+          body-includes: ${{ env.changelog_comment }}
+      - name: Create PR comment if changelog entry is missing, required, and does not exist
+        if: |
+          steps.filter.outputs.changelog == 'false' &&
+          steps.changelog_comment.outputs.comment-body == ''
+        uses: peter-evans/create-or-update-comment@v1
+        with:
+          issue-number: ${{ github.event.pull_request.number }}
+          body: ${{ env.changelog_comment }}
+      - name: Fail job if changelog entry is missing and required
+        if: steps.filter.outputs.changelog == 'false'
+        uses: actions/github-script@v6
+        with:
+          script: core.setFailed('Changelog entry required to merge.')
--- a/.github/workflows/changelog-existence.yml
+++ b/.github/workflows/changelog-existence.yml
@@ -1,40 +0,0 @@
-# **what?**
-# Checks that a file has been committed under the /.changes directory
-# as a new CHANGELOG entry.  Cannot check for a specific filename as
-# it is dynamically generated by change type and timestamp.
-# This workflow runs on pull_request_target because it requires
-# secrets to post comments.
-
-# **why?**
-# Ensure code change gets reflected in the CHANGELOG.
-
-# **when?**
-# This will run for all PRs going into main and *.latest.  It will
-# run when they are opened, reopened, when any label is added or removed
-# and when new code is pushed to the branch.  The action will then get
-# skipped if the 'Skip Changelog' label is present is any of the labels.
-
-name: Check Changelog Entry
-
-on:
-  pull_request_target:
-    types: [opened, reopened, labeled, unlabeled, synchronize]
-    paths-ignore: ['.changes/**', '.github/**', 'tests/**', '**.md', '**.yml']
-
-  workflow_dispatch:
-
-defaults:
-  run:
-    shell: bash
-
-permissions:
-  contents: read
-  pull-requests: write
-
-jobs:
-  changelog:
-    uses: dbt-labs/actions/.github/workflows/changelog-existence.yml@main
-    with:
-      changelog_comment: 'Thank you for your pull request! We could not find a changelog entry for this change. 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).'
-      skip_label: 'Skip Changelog'
-    secrets: inherit
--- a/.github/workflows/check-artifact-changes.yml
+++ b/.github/workflows/check-artifact-changes.yml
@@ -1,41 +0,0 @@
-name: Check Artifact Changes
-
-on:
-  pull_request:
-    types: [ opened, reopened, labeled, unlabeled, synchronize ]
-    paths-ignore: [ '.changes/**', '.github/**', 'tests/**', '**.md', '**.yml' ]
-
-  workflow_dispatch:
-
-jobs:
-  check-artifact-changes:
-    runs-on: ubuntu-latest
-    if: ${{ !contains(github.event.pull_request.labels.*.name, 'artifact_minor_upgrade') }}
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-
-      - name: Check for changes in core/dbt/artifacts
-        # https://github.com/marketplace/actions/paths-changes-filter
-        uses: dorny/paths-filter@v3
-        id: check_artifact_changes
-        with:
-          filters: |
-            artifacts_changed:
-              - 'core/dbt/artifacts/**'
-          list-files: shell
-
-      - name: Fail CI if artifacts have changed
-        if: steps.check_artifact_changes.outputs.artifacts_changed == 'true'
-        run: |
-          echo "CI failure: Artifact changes checked in core/dbt/artifacts directory."
-          echo "Files changed: ${{ steps.check_artifact_changes.outputs.artifacts_changed_files }}"
-          echo "To bypass this check, confirm that the change is not breaking (https://github.com/dbt-labs/dbt-core/blob/main/core/dbt/artifacts/README.md#breaking-changes) and add the 'artifact_minor_upgrade' label to the PR. Modifications and additions to all fields require updates to https://github.com/dbt-labs/dbt-jsonschema."
-          exit 1
-
-      - name: CI check passed
-        if: steps.check_artifact_changes.outputs.artifacts_changed == 'false'
-        run: |
-          echo "No prohibited artifact changes found in core/dbt/artifacts. CI check passed."
--- a/.github/workflows/community-label.yml
+++ b/.github/workflows/community-label.yml
@@ -1,39 +0,0 @@
-# **what?**
-# Label a PR with a `community` label when a PR is opened by a user outside core/adapters
-
-# **why?**
-# To streamline triage and ensure that community contributions are recognized and prioritized
-
-# **when?**
-# When a PR is opened, not in draft or moved from draft to ready for review
-
-
-name: Label community PRs
-
-on:
-  # have to use pull_request_target since community PRs come from forks
-  pull_request_target:
-    types: [opened, ready_for_review]
-
-defaults:
-  run:
-    shell: bash
-
-permissions:
-    pull-requests: write # labels PRs
-    contents: read # reads team membership
-
-jobs:
-  open_issues:
-    # If this PR already has the community label, no need to relabel it
-    # If this PR is opened and not draft, determine if it needs to be labeled
-    # if the PR is converted out of draft, determine if it needs to be labeled
-    if: |
-      (!contains(github.event.pull_request.labels.*.name, 'community') &&
-      (github.event.action == 'opened' && github.event.pull_request.draft == false ) ||
-       github.event.action == 'ready_for_review' )
-    uses: dbt-labs/actions/.github/workflows/label-community.yml@main
-    with:
-        github_team: 'core-group'
-        label: 'community'
-    secrets: inherit
--- a/.github/workflows/cut-release-branch.yml
+++ b/.github/workflows/cut-release-branch.yml
@@ -1,41 +0,0 @@
-# **what?**
-# Cuts a new `*.latest` branch
-# Also cleans up all files in `.changes/unreleased` and `.changes/previous verion on
-# `main` and bumps `main` to the input version.
-
-# **why?**
-# Generally reduces the workload of engineers and reduces error.  Allow automation.
-
-# **when?**
-# This will run when called manually.
-
-name: Cut new release branch
-
-on:
-  workflow_dispatch:
-    inputs:
-      version_to_bump_main:
-        description: 'The alpha version main should bump to (ex. 1.6.0a1)'
-        required: true
-      new_branch_name:
-        description: 'The full name of the new branch (ex. 1.5.latest)'
-        required: true
-
-defaults:
-  run:
-    shell: bash
-
-permissions:
-  contents: write
-
-jobs:
-  cut_branch:
-    name: "Cut branch and clean up main for dbt-core"
-    uses: dbt-labs/actions/.github/workflows/cut-release-branch.yml@main
-    with:
-      version_to_bump_main: ${{ inputs.version_to_bump_main }}
-      new_branch_name: ${{ inputs.new_branch_name }}
-      PR_title: "Cleanup main after cutting new ${{ inputs.new_branch_name }} branch"
-      PR_body: "All adapter PRs will fail CI until the dbt-core PR has been merged due to release version conflicts."
-    secrets:
-      FISHTOWN_BOT_PAT: ${{ secrets.FISHTOWN_BOT_PAT }}
--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
Emily Rockman	734b6429c7	update to use Docs object	2022-07-27 13:34:23 -05:00
Benoit Perigaud	a75b2c0a90	Make docs a dataclass instead of a Dict	2022-07-26 19:38:22 +02:00
Benoit Perigaud	6b6ae22434	Merge branch 'feature/custom-node-colors-dbt_project' of github.com:dbt-labs/dbt-core into feature/custom-node-colors-dbt_project	2022-07-20 12:51:29 +02:00
Benoit Perigaud	287f443ec9	Make docs a Dict to avoid parsing errors	2022-07-20 12:44:01 +02:00
Benoit Perigaud	aea2c4a29b	Add node_color to Docs	2022-07-20 12:43:09 +02:00
Benoit Perigaud	21ffe31270	Handle when docs is both under docs and config.docs	2022-07-20 12:42:25 +02:00
Sung Won Chung	70c9074625	Merge branch 'main' of https://github.com/dbt-labs/dbt into feature/custom-node-colors-dbt_project	2022-07-19 14:27:18 -05:00
Benoit Perigaud	9fca33cb29	Add docs config and input validation	2022-06-21 09:10:15 +02:00
Benoit Perigaud	6360247d39	Remove node_color from the original docs config	2022-06-21 09:09:35 +02:00
Matt Winkler	f0fbb0e551	add Optional node_color config in Docs dataclass	2022-06-07 09:17:15 -06:00