update to use Docs object

.bumpversion.cfg

@@ -1,19 +1,13 @@
 [bumpversion]
-current_version = 1.5.0b1
-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,9 @@ 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]

.changes/0.0.0.md

@@ -3,8 +3,6 @@
 For information on prior major and minor releases, see their changelogs:
 
 
-* [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)

.changes/1.5.0-b1.md

@@ -1,80 +0,0 @@
-## dbt-core 1.5.0-b1 - February 17, 2023
-
-### Features
-
-- Data type constraints are now native to SQL table materializations. Enforce columns are specific data types and not null depending on database functionality. ([#6079](https://github.com/dbt-labs/dbt-core/issues/6079))
-- Have dbt debug spit out structured json logs with flags enabled. ([#5353](https://github.com/dbt-labs/dbt-core/issues/5353))
-- add adapter_response to dbt test and freshness result ([#2964](https://github.com/dbt-labs/dbt-core/issues/2964))
-- Improve error message for packages missing `dbt_project.yml` ([#6663](https://github.com/dbt-labs/dbt-core/issues/6663))
-- Adjust makefile to have clearer instructions for CI env var changes. ([#6689](https://github.com/dbt-labs/dbt-core/issues/6689))
-- Stand-alone Python module for PostgresColumn ([#6772](https://github.com/dbt-labs/dbt-core/issues/6772))
-- Exposure owner requires one of name or email keys, and accepts additional arbitrary keys ([#6833](https://github.com/dbt-labs/dbt-core/issues/6833))
-- Parse 'group' resource ([#6921](https://github.com/dbt-labs/dbt-core/issues/6921))
-
-### Fixes
-
-- add merge_exclude_columns adapter tests ([#6699](https://github.com/dbt-labs/dbt-core/issues/6699))
-- Include adapter_response in NodeFinished run_result log event ([#6703](https://github.com/dbt-labs/dbt-core/issues/6703))
-- Sort cli vars before hashing for partial parsing ([#6710](https://github.com/dbt-labs/dbt-core/issues/6710))
-- [Regression] exposure_content referenced incorrectly ([#6738](https://github.com/dbt-labs/dbt-core/issues/6738))
-- Remove pin on packaging and stop using it for prerelease comparisons ([#6834](https://github.com/dbt-labs/dbt-core/issues/6834))
-- Readd depends_on.macros to SeedNode, to support seeds with hooks calling macros ([#6806](https://github.com/dbt-labs/dbt-core/issues/6806))
-- Fix regression of --quiet cli parameter behavior ([#6749](https://github.com/dbt-labs/dbt-core/issues/6749))
-- Ensure results from hooks contain nodes when processing them ([#6796](https://github.com/dbt-labs/dbt-core/issues/6796))
-- Always flush stdout after logging ([#6901](https://github.com/dbt-labs/dbt-core/issues/6901))
-- Reapply logging fixes which were accidentally reverted ([#6936](https://github.com/dbt-labs/dbt-core/issues/6936))
-- Set relation_name in test nodes at compile time ([#6930](https://github.com/dbt-labs/dbt-core/issues/6930))
-- Readd initialization events, --log-cache-events in new CLI ([#6933](https://github.com/dbt-labs/dbt-core/issues/6933))
-- Fix previous state tests and disabled exposures, metrics ([#6752](https://github.com/dbt-labs/dbt-core/issues/6752), [#6753](https://github.com/dbt-labs/dbt-core/issues/6753))
-- Make use of hashlib.md5() FIPS compliant ([#6900](https://github.com/dbt-labs/dbt-core/issues/6900))
-
-### Docs
-
-- update link to installation instructions ([dbt-docs/#None](https://github.com/dbt-labs/dbt-docs/issues/None))
-- Fix JSON path to overview docs ([dbt-docs/#366](https://github.com/dbt-labs/dbt-docs/issues/366))
-- Searchable column descriptions ([dbt-docs/#140](https://github.com/dbt-labs/dbt-docs/issues/140), [dbt-docs/#322](https://github.com/dbt-labs/dbt-docs/issues/322), [dbt-docs/#369](https://github.com/dbt-labs/dbt-docs/issues/369))
-
-### Under the Hood
-
-- [CT-921] dbt compile works in click ([#5545](https://github.com/dbt-labs/dbt-core/issues/5545))
-- Fix use of ConnectionReused logging event ([#6168](https://github.com/dbt-labs/dbt-core/issues/6168))
-- Port docs tests to pytest ([#6573](https://github.com/dbt-labs/dbt-core/issues/6573))
-- Update deprecated github action command ([#6153](https://github.com/dbt-labs/dbt-core/issues/6153))
-- dbt snapshot works in click ([#5554](https://github.com/dbt-labs/dbt-core/issues/5554))
-- dbt list working with click ([#5549](https://github.com/dbt-labs/dbt-core/issues/5549))
-- Add dbt run-operation to click CLI ([#5552](https://github.com/dbt-labs/dbt-core/issues/5552))
-- dbt build working with new click framework ([#5541](https://github.com/dbt-labs/dbt-core/issues/5541))
-- dbt docs generate works with new click framework ([#5543](https://github.com/dbt-labs/dbt-core/issues/5543))
-- Replaced the EmptyLine event with a more general Formatting event, and added a Note event. ([#6481](https://github.com/dbt-labs/dbt-core/issues/6481))
-- Small optimization on manifest parsing benefitting large DAGs ([#6697](https://github.com/dbt-labs/dbt-core/issues/6697))
-- Revised and simplified various structured logging events ([#6664](https://github.com/dbt-labs/dbt-core/issues/6664), [#6665](https://github.com/dbt-labs/dbt-core/issues/6665), [#6666](https://github.com/dbt-labs/dbt-core/issues/6666))
-- dbt init works with click ([#5548](https://github.com/dbt-labs/dbt-core/issues/5548))
-- [CT-920][CT-1900] Create Click CLI runner and use it to fix dbt docs commands ([#5544](https://github.com/dbt-labs/dbt-core/issues/5544), [#6722](https://github.com/dbt-labs/dbt-core/issues/6722))
-- Migrate debug task to click ([#5546](https://github.com/dbt-labs/dbt-core/issues/5546))
--  Optimized GraphQueue to remove graph analysis bottleneck in large dags. ([#6759](https://github.com/dbt-labs/dbt-core/issues/6759))
-- Implement --version for click cli ([#6757](https://github.com/dbt-labs/dbt-core/issues/6757))
-- [CT-1841] Convert custom target test to Pytest ([#6638](https://github.com/dbt-labs/dbt-core/issues/6638))
-- Remove BigQuery-specific btye abbreviations ([#6741](https://github.com/dbt-labs/dbt-core/issues/6741))
-- warn_error/warn_error_options mutual exclusivity in click ([#6579](https://github.com/dbt-labs/dbt-core/issues/6579))
-- Enables the new Click Cli on the commandline! 🚀 ([#6784](https://github.com/dbt-labs/dbt-core/issues/6784))
-- Lazily call --version ([#6812](https://github.com/dbt-labs/dbt-core/issues/6812))
-- Moving simple_seed to adapter zone to help adapter test conversions ([#CT-1959](https://github.com/dbt-labs/dbt-core/issues/CT-1959))
-- flags.THREADS defaults to None ([#6887](https://github.com/dbt-labs/dbt-core/issues/6887))
-- Fixing target type exposure error ([#6928](https://github.com/dbt-labs/dbt-core/issues/6928))
-- Test binary serialization of logging events ([#6852](https://github.com/dbt-labs/dbt-core/issues/6852))
-
-### Dependencies
-
-- Bump ubuntu from 22.04 to 23.04 ([#6865](https://github.com/dbt-labs/dbt-core/pull/6865))
-- Revert hoisting dbt.cli.main into the dbt.name namespace ([#](https://github.com/dbt-labs/dbt-core/pull/))
-
-### Contributors
-- [@aezomz](https://github.com/aezomz) ([#2964](https://github.com/dbt-labs/dbt-core/issues/2964))
-- [@boxysean](https://github.com/boxysean) ([#6697](https://github.com/dbt-labs/dbt-core/issues/6697))
-- [@callum-mcdata](https://github.com/callum-mcdata) ([#6928](https://github.com/dbt-labs/dbt-core/issues/6928))
-- [@dave-connors-3](https://github.com/dave-connors-3) ([#6699](https://github.com/dbt-labs/dbt-core/issues/6699))
-- [@davidbloss](https://github.com/davidbloss) ([#6153](https://github.com/dbt-labs/dbt-core/issues/6153))
-- [@halvorlu](https://github.com/halvorlu) ([#366](https://github.com/dbt-labs/dbt-core/issues/366))
-- [@nielspardon](https://github.com/nielspardon) ([#6900](https://github.com/dbt-labs/dbt-core/issues/6900))
-- [@ryancharris](https://github.com/ryancharris) ([#None](https://github.com/dbt-labs/dbt-core/issues/None))
-- [@sungchun12](https://github.com/sungchun12) ([#6079](https://github.com/dbt-labs/dbt-core/issues/6079))

.changes/1.5.0/Dependencies-20230206-000926.yaml

@@ -1,6 +0,0 @@
-kind: "Dependencies"
-body: "Bump ubuntu from 22.04 to 23.04"
-time: 2023-02-06T00:09:26.00000Z
-custom:
-  Author: dependabot[bot]
-  PR: 6865

.changes/1.5.0/Dependencies-20230215-091759.yaml

@@ -1,6 +0,0 @@
-kind: Dependencies
-body: Revert hoisting dbt.cli.main into the dbt.name namespace
-time: 2023-02-15T09:17:59.04148-08:00
-custom:
-  Author: aranke
-  PR: ''

.changes/1.5.0/Docs-20230207-123807.yaml

@@ -1,6 +0,0 @@
-kind: Docs
-body: update link to installation instructions
-time: 2023-02-07T12:38:07.336783-05:00
-custom:
-  Author: ryancharris
-  Issue: None

.changes/1.5.0/Docs-20230209-082901.yaml

@@ -1,6 +0,0 @@
-kind: Docs
-body: Fix JSON path to overview docs
-time: 2023-02-09T08:29:01.432616-07:00
-custom:
-  Author: halvorlu
-  Issue: "366"

.changes/1.5.0/Docs-20230209-212729.yaml

@@ -1,6 +0,0 @@
-kind: Docs
-body: Searchable column descriptions
-time: 2023-02-09T21:27:29.570243-07:00
-custom:
-  Author: dbeatty10
-  Issue: 140 322 369

.changes/1.5.0/Features-20221118-141120.yaml

@@ -1,8 +0,0 @@
-kind: Features
-body: Data type constraints are now native to SQL table materializations. Enforce
-  columns are specific data types and not null depending on database functionality.
-time: 2022-11-18T14:11:20.868062-08:00
-custom:
-  Author: sungchun12
-  Issue: "6079"
-  PR: "6271"

.changes/1.5.0/Features-20230107-003157.yaml

@@ -1,6 +0,0 @@
-kind: Features
-body: Have dbt debug spit out structured json logs with flags enabled.
-time: 2023-01-07T00:31:57.516063-08:00
-custom:
-  Author: versusfacit
-  Issue: "5353"

.changes/1.5.0/Features-20230118-233801.yaml

@@ -1,6 +0,0 @@
-kind: Features
-body: add adapter_response to dbt test and freshness result
-time: 2023-01-18T23:38:01.857342+08:00
-custom:
-  Author: aezomz
-  Issue: "2964"

.changes/1.5.0/Features-20230120-112921.yaml

@@ -1,6 +0,0 @@
-kind: Features
-body: Improve error message for packages missing `dbt_project.yml`
-time: 2023-01-20T11:29:21.509967-07:00
-custom:
-  Author: dbeatty10
-  Issue: "6663"

.changes/1.5.0/Features-20230126-154716.yaml

@@ -1,6 +0,0 @@
-kind: Features
-body: Adjust makefile to have clearer instructions for CI env var changes.
-time: 2023-01-26T15:47:16.887327-08:00
-custom:
-  Author: versusfacit
-  Issue: "6689"

.changes/1.5.0/Features-20230127-162812.yaml

@@ -1,6 +0,0 @@
-kind: Features
-body: Stand-alone Python module for PostgresColumn
-time: 2023-01-27T16:28:12.212427-08:00
-custom:
-  Author: nssalian
-  Issue: "6772"

.changes/1.5.0/Features-20230209-092059.yaml

@@ -1,7 +0,0 @@
-kind: Features
-body: Exposure owner requires one of name or email keys, and accepts additional arbitrary
-  keys
-time: 2023-02-09T09:20:59.300272-05:00
-custom:
-  Author: michelleark
-  Issue: "6833"

.changes/1.5.0/Features-20230209-093409.yaml

@@ -1,6 +0,0 @@
-kind: Features
-body: Parse 'group' resource
-time: 2023-02-09T09:34:09.547006-05:00
-custom:
-  Author: michelleark
-  Issue: "6921"

.changes/1.5.0/Fixes-20230123-132814.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: add merge_exclude_columns adapter tests
-time: 2023-01-23T13:28:14.808748-06:00
-custom:
-  Author: dave-connors-3
-  Issue: "6699"

.changes/1.5.0/Fixes-20230124-115837.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Include adapter_response in NodeFinished run_result log event
-time: 2023-01-24T11:58:37.74179-05:00
-custom:
-  Author: gshank
-  Issue: "6703"

.changes/1.5.0/Fixes-20230124-141943.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Sort cli vars before hashing for partial parsing
-time: 2023-01-24T14:19:43.333628-05:00
-custom:
-  Author: gshank
-  Issue: "6710"

.changes/1.5.0/Fixes-20230125-191739.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: '[Regression] exposure_content referenced incorrectly'
-time: 2023-01-25T19:17:39.942081-05:00
-custom:
-  Author: Mathyoub
-  Issue: "6738"

.changes/1.5.0/Fixes-20230201-154418.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Remove pin on packaging and stop using it for prerelease comparisons
-time: 2023-02-01T15:44:18.279158-05:00
-custom:
-  Author: gshank
-  Issue: "6834"

.changes/1.5.0/Fixes-20230203-135557.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Readd depends_on.macros to SeedNode, to support seeds with hooks calling macros
-time: 2023-02-03T13:55:57.853715+01:00
-custom:
-  Author: jtcohen6
-  Issue: "6806"

.changes/1.5.0/Fixes-20230207-143544.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Fix regression of --quiet cli parameter behavior
-time: 2023-02-07T14:35:44.160163-05:00
-custom:
-  Author: peterallenwebb
-  Issue: "6749"

.changes/1.5.0/Fixes-20230208-110551.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Ensure results from hooks contain nodes when processing them
-time: 2023-02-08T11:05:51.952494-06:00
-custom:
-  Author: emmyoop
-  Issue: "6796"

.changes/1.5.0/Fixes-20230208-154935.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Always flush stdout after logging
-time: 2023-02-08T15:49:35.175874-05:00
-custom:
-  Author: peterallenwebb
-  Issue: "6901"

.changes/1.5.0/Fixes-20230210-103028.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Reapply logging fixes which were accidentally reverted
-time: 2023-02-10T10:30:28.179997-05:00
-custom:
-  Author: peterallenwebb
-  Issue: "6936"

.changes/1.5.0/Fixes-20230210-194157.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Set relation_name in test nodes at compile time
-time: 2023-02-10T19:41:57.386766-05:00
-custom:
-  Author: gshank
-  Issue: "6930"

.changes/1.5.0/Fixes-20230213-130522.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Readd initialization events, --log-cache-events in new CLI
-time: 2023-02-13T13:05:22.989477+01:00
-custom:
-  Author: jtcohen6
-  Issue: "6933"

.changes/1.5.0/Fixes-20230213-170723.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Fix previous state tests and disabled exposures, metrics
-time: 2023-02-13T17:07:23.185679-05:00
-custom:
-  Author: gshank
-  Issue: 6752 6753

.changes/1.5.0/Fixes-20230215-104536.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Make use of hashlib.md5() FIPS compliant
-time: 2023-02-15T10:45:36.755797+01:00
-custom:
-  Author: nielspardon
-  Issue: "6900"

.changes/1.5.0/Under the Hood-20230111-145143.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: '[CT-921] dbt compile works in click'
-time: 2023-01-11T14:51:43.324107-08:00
-custom:
-  Author: aranke
-  Issue: "5545"

.changes/1.5.0/Under the Hood-20230113-132513.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Fix use of ConnectionReused logging event
-time: 2023-01-13T13:25:13.023168-05:00
-custom:
-  Author: gshank
-  Issue: "6168"

.changes/1.5.0/Under the Hood-20230113-150700.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Port docs tests to pytest
-time: 2023-01-13T15:07:00.477038-05:00
-custom:
-  Author: peterallenwebb
-  Issue: "6573"

.changes/1.5.0/Under the Hood-20230117-111737.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Update deprecated github action command
-time: 2023-01-17T11:17:37.046095-06:00
-custom:
-  Author: davidbloss
-  Issue: "6153"

.changes/1.5.0/Under the Hood-20230117-162505.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: dbt snapshot works in click
-time: 2023-01-17T16:25:05.973769-08:00
-custom:
-  Author: ChenyuLInx
-  Issue: "5554"

.changes/1.5.0/Under the Hood-20230117-213729.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: dbt list working with click
-time: 2023-01-17T21:37:29.91632-05:00
-custom:
-  Author: michelleark
-  Issue: "5549"

.changes/1.5.0/Under the Hood-20230119-105304.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Add dbt run-operation to click CLI
-time: 2023-01-19T10:53:04.154871+01:00
-custom:
-  Author: jtcohen6
-  Issue: "5552"

.changes/1.5.0/Under the Hood-20230119-205650.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: dbt build working with new click framework
-time: 2023-01-19T20:56:50.50549-05:00
-custom:
-  Author: michelleark
-  Issue: "5541"

.changes/1.5.0/Under the Hood-20230119-211040.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: dbt docs generate works with new click framework
-time: 2023-01-19T21:10:40.698851-05:00
-custom:
-  Author: michelleark
-  Issue: "5543"

.changes/1.5.0/Under the Hood-20230120-172254.yaml

@@ -1,7 +0,0 @@
-kind: Under the Hood
-body: Replaced the EmptyLine event with a more general Formatting event, and added
-  a Note event.
-time: 2023-01-20T17:22:54.45828-05:00
-custom:
-  Author: peterallenwebb
-  Issue: "6481"

.changes/1.5.0/Under the Hood-20230122-215235.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Small optimization on manifest parsing benefitting large DAGs
-time: 2023-01-22T21:52:35.549814+01:00
-custom:
-  Author: boxysean
-  Issue: "6697"

.changes/1.5.0/Under the Hood-20230124-153553.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Revised and simplified various structured logging events
-time: 2023-01-24T15:35:53.065356-05:00
-custom:
-  Author: peterallenwebb
-  Issue: 6664 6665 6666

.changes/1.5.0/Under the Hood-20230124-175110.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: dbt init works with click
-time: 2023-01-24T17:51:10.74065-05:00
-custom:
-  Author: michelleark
-  Issue: "5548"

.changes/1.5.0/Under the Hood-20230125-041136.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: '[CT-920][CT-1900] Create Click CLI runner and use it to fix dbt docs commands'
-time: 2023-01-25T04:11:36.57506-08:00
-custom:
-  Author: aranke
-  Issue: 5544 6722

.changes/1.5.0/Under the Hood-20230125-102606.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Migrate debug task to click
-time: 2023-01-25T10:26:06.735994-06:00
-custom:
-  Author: stu-k
-  Issue: "5546"

.changes/1.5.0/Under the Hood-20230126-135939.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: ' Optimized GraphQueue to remove graph analysis bottleneck in large dags.'
-time: 2023-01-26T13:59:39.518345-05:00
-custom:
-  Author: peterallenwebb
-  Issue: "6759"

.changes/1.5.0/Under the Hood-20230126-143102.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Implement --version for click cli
-time: 2023-01-26T14:31:02.740282-06:00
-custom:
-  Author: stu-k
-  Issue: "6757"

.changes/1.5.0/Under the Hood-20230126-164741.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: '[CT-1841] Convert custom target test to Pytest'
-time: 2023-01-26T16:47:41.198714-08:00
-custom:
-  Author: aranke
-  Issue: "6638"

.changes/1.5.0/Under the Hood-20230130-153306.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Remove BigQuery-specific btye abbreviations
-time: 2023-01-30T15:33:06.28965-07:00
-custom:
-  Author: dbeatty10
-  Issue: "6741"

.changes/1.5.0/Under the Hood-20230130-175752.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: "Enables the new Click Cli on the commandline! \U0001F680"
-time: 2023-01-30T17:57:52.65626-06:00
-custom:
-  Author: iknox-fa
-  Issue: "6784"

.changes/1.5.0/Under the Hood-20230130-180917.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: warn_error/warn_error_options mutual exclusivity in click
-time: 2023-01-30T18:09:17.240662-05:00
-custom:
-  Author: michelleark
-  Issue: "6579"

.changes/1.5.0/Under the Hood-20230131-141806.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Lazily call --version
-time: 2023-01-31T14:18:06.02312-06:00
-custom:
-  Author: stu-k
-  Issue: "6812"

.changes/1.5.0/Under the Hood-20230203-143551.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Moving simple_seed to adapter zone to help adapter test conversions
-time: 2023-02-03T14:35:51.481856-08:00
-custom:
-  Author: nssalian
-  Issue: CT-1959

.changes/1.5.0/Under the Hood-20230207-165111.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: flags.THREADS defaults to None
-time: 2023-02-07T16:51:11.011984-05:00
-custom:
-  Author: michelleark
-  Issue: "6887"

.changes/1.5.0/Under the Hood-20230210-084647.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Fixing target type exposure error
-time: 2023-02-10T08:46:47.72936-06:00
-custom:
-  Author: callum-mcdata
-  Issue: "6928"

.changes/1.5.0/Under the Hood-20230216-143252.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Test binary serialization of logging events
-time: 2023-02-16T14:32:52.524225-05:00
-custom:
-  Author: gshank
-  Issue: "6852"

.changes/unreleased/Dependency-20220927-000822.yaml

@@ -1,7 +0,0 @@
-kind: "Dependency"
-body: "Bump mypy from 0.971 to 0.981"
-time: 2022-09-27T00:08:22.00000Z
-custom:
-  Author: dependabot[bot]
-  Issue: 4904
-  PR: 5937

.changes/unreleased/Docs-20230113-094855.yaml

@@ -1,7 +0,0 @@
-kind: Docs
-body: Improve displayed message under "Arguments" section for argumentless macro
-time: 2023-01-13T09:48:55.574898-05:00
-custom:
-  Author: MartinGuindon
-  Issue: "358"
-  PR: "359"

.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"

.changes/unreleased/Features-20230124-135550.yaml

@@ -1,6 +0,0 @@
-kind: Features
-body: Make project version optional
-time: 2023-01-24T13:55:50.86071024-08:00
-custom:
-  Author: seub
-  Issue: "6603"

.changes/unreleased/Features-20230214-225134.yaml

@@ -1,6 +0,0 @@
-kind: Features
-body: parse 'group' config on groupable nodes
-time: 2023-02-14T22:51:34.936228-05:00
-custom:
-  Author: michelleark
-  Issue: "6823"

.changes/unreleased/Features-20230216-144534.yaml

@@ -1,6 +0,0 @@
-kind: Features
-body: Implemented new log cli parameters for finer-grained control.
-time: 2023-02-16T14:45:34.038453-05:00
-custom:
-  Author: peterallenwebb
-  Issue: "6639"

.changes/unreleased/Features-20230218-092816.yaml

@@ -1,6 +0,0 @@
-kind: Features
-body: Add access attribute to parsed nodes
-time: 2023-02-18T09:28:16.448175-05:00
-custom:
-  Author: gshank
-  Issue: "6824"

.changes/unreleased/Features-20230224-134533.yaml

@@ -1,6 +0,0 @@
-kind: Features
-body: Add ability to select by group resource
-time: 2023-02-24T13:45:33.974287-06:00
-custom:
-  Author: emmyoop
-  Issue: "6825"

.changes/unreleased/Features-20230224-182214.yaml

@@ -1,6 +0,0 @@
-kind: Features
-body: Disallow refing private model across groups
-time: 2023-02-24T18:22:14.965136-05:00
-custom:
-  Author: gshank
-  Issue: "6826"

.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"

.changes/unreleased/Fixes-20221030-102114.yaml

@@ -1,7 +0,0 @@
-kind: Fixes
-body: Remove trailing slashes from source paths (#6102)
-time: 2022-10-30T10:21:14.660221Z
-custom:
-  Author: jmg-duarte
-  Issue: "6102"
-  PR: "6179"

.changes/unreleased/Fixes-20230221-170630.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Fix compilation logic for ephemeral nodes
-time: 2023-02-21T17:06:30.218568-05:00
-custom:
-  Author: gshank
-  Issue: "6885"

.changes/unreleased/Fixes-20230224-001338.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Fix semver comparison logic by ensuring numeric values
-time: 2023-02-24T00:13:38.23242+01:00
-custom:
-  Author: jtcohen6
-  Issue: "7039"

.changes/unreleased/Under the Hood-20230217-105223.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Rename "constraint_enabled" to "contract"
-time: 2023-02-17T10:52:23.212474-05:00
-custom:
-  Author: gshank
-  Issue: "6748"

.changie.yaml

@@ -4,137 +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
-    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
-
+- 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 }}
-          {{- 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}}
+      {{- 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 }}

.flake8

@@ -9,4 +9,4 @@ ignore =
     E203 # makes Flake8 work like black
     E741
     E501 # long line checking is done in black
-exclude = test/
+exclude = test

.gitattributes

@@ -1,2 +0,0 @@
-core/dbt/include/index.html binary
-tests/functional/artifacts/data/state/*/manifest.json binary

.github/CODEOWNERS

@@ -16,57 +16,25 @@
 # Changes to GitHub configurations including Actions
 /.github/ @leahwicz
 
-### LANGUAGE
-
 # 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/events/               @dbt-labs/core-language  # structured logging
-/core/dbt/parser/               @dbt-labs/core-language
-
-# Language misc files
-/core/dbt/dataclass_schema.py   @dbt-labs/core-language
-/core/dbt/hooks.py              @dbt-labs/core-language
-/core/dbt/node_types.py         @dbt-labs/core-language
-/core/dbt/semver.py             @dbt-labs/core-language
-
-
-### EXECUTION
+/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/graph/                @dbt-labs/core-execution
-/core/dbt/task/                 @dbt-labs/core-execution
+/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
 
-# Execution misc files
-/core/dbt/compilation.py        @dbt-labs/core-execution
-/core/dbt/flags.py              @dbt-labs/core-execution
-/core/dbt/lib.py                @dbt-labs/core-execution
-/core/dbt/main.py               @dbt-labs/core-execution
-/core/dbt/profiler.py           @dbt-labs/core-execution
-/core/dbt/selected_resources.py @dbt-labs/core-execution
-/core/dbt/tracking.py           @dbt-labs/core-execution
-/core/dbt/version.py            @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
 
-
-### 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
-
-# Functional tests for adapter plugins
-/tests/adapter                  @dbt-labs/core-adapters
-
-### TESTS
-
-# Overlapping ownership for vast majority of unit + functional tests
+# 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

.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

.github/ISSUE_TEMPLATE/config.yml

@@ -1,14 +1,4 @@
-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
@@ -18,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

.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

.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@v1
-    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/main.py

@@ -28,12 +28,11 @@ if __name__ == "__main__":
     if package_request.status_code == 404:
         if halt_on_missing:
             sys.exit(1)
-        # everything is the latest if the package doesn't exist
-        github_output = os.environ.get("GITHUB_OUTPUT")
-        with open(github_output, "at", encoding="utf-8") as gh_output:
-            gh_output.write("latest=True")
-            gh_output.write("minor_latest=True")
-        sys.exit(0)
+        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
@@ -92,7 +91,5 @@ if __name__ == "__main__":
     latest = is_latest(pre_rel, new_version, current_latest)
     minor_latest = is_latest(pre_rel, new_version, current_minor_latest)
 
-    github_output = os.environ.get("GITHUB_OUTPUT")
-    with open(github_output, "at", encoding="utf-8") as gh_output:
-        gh_output.write(f"latest={latest}")
-        gh_output.write(f"minor_latest={minor_latest}")
+    print(f"::set-output name=latest::{latest}")
+    print(f"::set-output name=minor_latest::{minor_latest}")

.github/pull_request_template.md

@@ -20,4 +20,4 @@ resolves #
 - [ ] 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-a-changelog-entry)
+- [ ] I have run `changie new` to [create a changelog entry](https://github.com/dbt-labs/dbt-core/blob/main/CONTRIBUTING.md#Adding-CHANGELOG-Entry)

.github/workflows/bot-changelog.yml

@@ -1,61 +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"
-          - label: "snyk"
-            changie_kind: "Security"
-    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.0.1
-      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  PR: ${{ github.event.pull_request.number }}"

.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.')

.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 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
-
-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

.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 }}

.github/workflows/dependency-changelog.yml

@@ -0,0 +1,114 @@
+# **what?**
+# When dependabot create a PR, it always adds the `dependencies` label. This
+# action will add a corresponding changie yaml file to that PR when that label is added.
+# The file is created off a template:
+#
+# kind: Dependencies
+# body: <PR title>
+# time: <current timestamp>
+# custom:
+#   Author: dependabot
+#   Issue: 4904
+#   PR: <PR number>
+#
+# **why?**
+# Automate changelog generation for more visability with automated dependency updates via dependabot.
+
+# **when?**
+# Once a PR is created and it has been correctly labeled with `dependencies`.  The intended use
+# is for the PRs created by dependabot.  You can also manually trigger this by adding the
+# `dependencies` label at any time.
+
+name: Dependency Changelog
+
+on:
+  pull_request:
+    # catch when the PR is opened with the label or when the label is added
+    types: [opened, labeled]
+
+permissions:
+  contents: write
+  pull-requests: read
+
+jobs:
+  dependency_changelog:
+    if: "contains(github.event.pull_request.labels.*.name, 'dependencies')"
+    runs-on: ubuntu-latest
+
+    steps:
+    # timestamp changes the order the changelog entries are listed in the final Changelog.md file.  Precision is not
+    # important here.
+    # The timestamp on the filename and the timestamp in the contents of the file have different expected formats.
+    - 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'
+
+    # changie expects files to be named in a specific pattern.
+    - name: Generate Filepath
+      id: fp
+      run: |
+        FILEPATH=.changes/unreleased/Dependencies-${{ steps.filename_time.outputs.time }}.yaml
+        echo "::set-output name=FILEPATH::$FILEPATH"
+
+    - name: Check if changelog file exists already
+      # if there's already a changelog entry, don't add another one!
+      # 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: changelog_check
+      with:
+        token: ${{ secrets.GITHUB_TOKEN }}
+        filters: |
+          exists:
+            - added: '.changes/unreleased/**.yaml'
+
+    - name: Checkout Branch
+      if: steps.changelog_check.outputs.exists == 'false'
+      uses: actions/checkout@v2
+      with:
+        # specifying the ref avoids checking out the repository in a detached state
+        ref: ${{ github.event.pull_request.head.ref }}
+        # If this is not set to false, Git push is performed with github.token and not the token
+        # configured using the env: GITHUB_TOKEN in commit step
+        persist-credentials: false
+
+    - name: Create file from template
+      if: steps.changelog_check.outputs.exists == 'false'
+      run: |
+        echo kind: Dependencies > "${{ steps.fp.outputs.FILEPATH }}"
+        echo 'body: "${{ github.event.pull_request.title }}"' >> "${{ steps.fp.outputs.FILEPATH }}"
+        echo time: "${{ steps.file_content_time.outputs.time }}" >> "${{ steps.fp.outputs.FILEPATH }}"
+        echo custom: >> "${{ steps.fp.outputs.FILEPATH }}"
+        echo '  Author: ${{ github.event.pull_request.user.login }}' >> "${{ steps.fp.outputs.FILEPATH }}"
+        echo '  Issue: "4904"' >> "${{ steps.fp.outputs.FILEPATH }}"  # github.event.pull_request.issue for auto id?
+        echo '  PR: "${{ github.event.pull_request.number }}"' >> "${{ steps.fp.outputs.FILEPATH }}"
+
+    - name: Commit Changelog File
+      if: steps.changelog_check.outputs.exists == 'false'
+      uses: gr2m/create-or-update-pull-request-action@v1
+      env:
+        # 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: https://docs.github.com/en/actions/security-guides/automatic-token-authentication#using-the-github_token-in-a-workflow
+        # When you use the repository's GITHUB_TOKEN to perform tasks on behalf of the GitHub Actions
+        # app, events triggered by the GITHUB_TOKEN will not create a new workflow run. This prevents
+        # you from accidentally creating recursive workflow runs. To get around this, use a Personal
+        # Access Token to commit changes.
+        GITHUB_TOKEN: ${{ secrets.FISHTOWN_BOT_PAT }}
+      with:
+        branch: ${{ github.event.pull_request.head.ref }}
+        # author expected in the format "Lorem J. Ipsum <lorem@example.com>"
+        author: "Github Build Bot <buildbot@fishtownanalytics.com>"
+        commit-message: "Add automated changelog yaml from template"

.github/workflows/generate-cli-api-docs.yml

@@ -1,165 +0,0 @@
-# **what?**
-# On push, if anything in core/dbt/docs or core/dbt/cli has been
-# created or modified, regenerate the CLI API docs using sphinx.
-
-# **why?**
-# We watch for changes in core/dbt/cli because the CLI API docs rely on click
-# and all supporting flags/params to be generated. We watch for changes in
-# core/dbt/docs since any changes to sphinx configuration or any of the
-# .rst files there could result in a differently build final index.html file.
-
-# **when?**
-# Whenever a change has been pushed to a branch, and only if there is a diff
-# between the PR branch and main's core/dbt/cli and or core/dbt/docs dirs.
-
-# TODO: add bot comment to PR informing contributor that the docs have been committed
-# TODO: figure out why github action triggered pushes cause github to fail to report
-#       the status of jobs
-
-name: Generate CLI API docs
-
-on:
-  pull_request:
-
-permissions:
-  contents: write
-  pull-requests: write
-
-env:
-  CLI_DIR: ${{ github.workspace }}/core/dbt/cli
-  DOCS_DIR: ${{ github.workspace }}/core/dbt/docs
-  DOCS_BUILD_DIR: ${{ github.workspace }}/core/dbt/docs/build
-
-jobs:
-  check_gen:
-    name: check if generation needed
-    runs-on: ubuntu-latest
-    if: ${{ github.event.pull_request.head.repo.fork == false }}
-    outputs:
-      cli_dir_changed: ${{ steps.check_cli.outputs.cli_dir_changed }}
-      docs_dir_changed: ${{ steps.check_docs.outputs.docs_dir_changed }}
-
-    steps:
-    - name: "[DEBUG] print variables"
-      run: |
-        echo "env.CLI_DIR:        ${{ env.CLI_DIR }}"
-        echo "env.DOCS_BUILD_DIR: ${{ env.DOCS_BUILD_DIR }}"
-        echo "env.DOCS_DIR:       ${{ env.DOCS_DIR }}"
-
-    - name: git checkout
-      uses: actions/checkout@v3
-      with:
-        fetch-depth: 0
-        ref: ${{ github.head_ref }}
-
-    - name: set shas
-      id: set_shas
-      run: |
-        THIS_SHA=$(git rev-parse @)
-        LAST_SHA=$(git rev-parse @~1)
-
-        echo "this sha: $THIS_SHA"
-        echo "last sha: $LAST_SHA"
-
-        echo "this_sha=$THIS_SHA" >> $GITHUB_OUTPUT
-        echo "last_sha=$LAST_SHA" >> $GITHUB_OUTPUT
-
-    - name: check for changes in core/dbt/cli
-      id: check_cli
-      run: |
-        CLI_DIR_CHANGES=$(git diff \
-          ${{ steps.set_shas.outputs.last_sha }} \
-          ${{ steps.set_shas.outputs.this_sha }} \
-          -- ${{ env.CLI_DIR }})
-
-        if [ -n "$CLI_DIR_CHANGES" ]; then
-          echo "changes found"
-          echo $CLI_DIR_CHANGES
-          echo "cli_dir_changed=true" >> $GITHUB_OUTPUT
-          exit 0
-        fi
-        echo "cli_dir_changed=false" >> $GITHUB_OUTPUT
-        echo "no changes found"
-
-    - name: check for changes in core/dbt/docs
-      id: check_docs
-      if: steps.check_cli.outputs.cli_dir_changed == 'false'
-      run: |
-        DOCS_DIR_CHANGES=$(git diff --name-only \
-          ${{ steps.set_shas.outputs.last_sha }} \
-          ${{ steps.set_shas.outputs.this_sha }} \
-          -- ${{ env.DOCS_DIR }} ':!${{ env.DOCS_BUILD_DIR }}')
-
-        DOCS_BUILD_DIR_CHANGES=$(git diff --name-only \
-          ${{ steps.set_shas.outputs.last_sha }} \
-          ${{ steps.set_shas.outputs.this_sha }} \
-          -- ${{ env.DOCS_BUILD_DIR }})
-
-        if [ -n "$DOCS_DIR_CHANGES" ] && [ -z "$DOCS_BUILD_DIR_CHANGES" ]; then
-          echo "changes found"
-          echo $DOCS_DIR_CHANGES
-          echo "docs_dir_changed=true" >> $GITHUB_OUTPUT
-          exit 0
-        fi
-        echo "docs_dir_changed=false" >> $GITHUB_OUTPUT
-        echo "no changes found"
-
-  gen_docs:
-    name: generate docs
-    runs-on: ubuntu-latest
-    needs: [check_gen]
-    if: |
-      needs.check_gen.outputs.cli_dir_changed == 'true'
-      || needs.check_gen.outputs.docs_dir_changed == 'true'
-
-    steps:
-      - name: "[DEBUG] print variables"
-        run: |
-          echo "env.DOCS_DIR:    ${{ env.DOCS_DIR }}"
-          echo "github head_ref: ${{ github.head_ref }}"
-
-      - name: git checkout
-        uses: actions/checkout@v3
-        with:
-          ref: ${{ github.head_ref }}
-
-      - name: install python
-        uses: actions/setup-python@v4.3.0
-        with:
-          python-version: 3.8
-
-      - name: install dev requirements
-        run: |
-          python3 -m venv env
-          source env/bin/activate
-          python -m pip install --upgrade pip
-          pip install -r requirements.txt -r dev-requirements.txt
-
-      - name: generate docs
-        run: |
-          source env/bin/activate
-          cd ${{ env.DOCS_DIR }}
-
-          echo "cleaning existing docs"
-          make clean
-
-          echo "creating docs"
-          make html
-
-      - name: debug
-        run: |
-          echo ">>>>> status"
-          git status
-          echo ">>>>> remotes"
-          git remote -v
-          echo ">>>>> branch"
-          git branch -v
-          echo ">>>>> log"
-          git log --pretty=oneline | head -5
-
-      - name: commit docs
-        run: |
-          git config user.name 'Github Build Bot'
-          git config user.email 'buildbot@fishtownanalytics.com'
-          git commit -am "Add generated CLI API docs"
-          git push -u origin ${{ github.head_ref }}

.github/workflows/jira-transition.yml

@@ -15,9 +15,6 @@ on:
   issues:
     types: [closed, deleted, reopened]
 
-# no special access is needed
-permissions: read-all
-
 jobs:
   call-label-action:
     uses: dbt-labs/jira-actions/.github/workflows/jira-transition.yml@main

.github/workflows/main.yml

@@ -45,9 +45,7 @@ jobs:
         uses: actions/checkout@v2
 
       - name: Set up Python
-        uses: actions/setup-python@v4.3.0
-        with:
-          python-version: '3.8'
+        uses: actions/setup-python@v2
 
       - name: Install python dependencies
         run: |
@@ -73,7 +71,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        python-version: ["3.7", "3.8", "3.9", "3.10", "3.11"]
+        python-version: ["3.7", "3.8", "3.9", "3.10"]
 
     env:
       TOXENV: "unit"
@@ -84,7 +82,7 @@ jobs:
         uses: actions/checkout@v2
 
       - name: Set up Python ${{ matrix.python-version }}
-        uses: actions/setup-python@v4.3.0
+        uses: actions/setup-python@v2
         with:
           python-version: ${{ matrix.python-version }}
 
@@ -101,9 +99,7 @@ jobs:
       - name: Get current date
         if: always()
         id: date
-        run: |
-          CURRENT_DATE=$(date +'%Y-%m-%dT%H_%M_%S') # no colons allowed for artifacts
-          echo "date=$CURRENT_DATE" >> $GITHUB_OUTPUT
+        run: echo "::set-output name=date::$(date +'%Y-%m-%dT%H_%M_%S')" #no colons allowed for artifacts
 
       - uses: actions/upload-artifact@v2
         if: always()
@@ -120,8 +116,8 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        python-version: ["3.7", "3.8", "3.9", "3.10", "3.11"]
-        os: [ubuntu-20.04]
+        python-version: ["3.7", "3.8", "3.9", "3.10"]
+        os: [ubuntu-latest]
         include:
           - python-version: 3.8
             os: windows-latest
@@ -141,7 +137,7 @@ jobs:
         uses: actions/checkout@v2
 
       - name: Set up Python ${{ matrix.python-version }}
-        uses: actions/setup-python@v4.3.0
+        uses: actions/setup-python@v2
         with:
           python-version: ${{ matrix.python-version }}
 
@@ -170,9 +166,7 @@ jobs:
       - name: Get current date
         if: always()
         id: date
-        run: |
-          CURRENT_DATE=$(date +'%Y-%m-%dT%H_%M_%S') # no colons allowed for artifacts
-          echo "date=$CURRENT_DATE" >> $GITHUB_OUTPUT
+        run: echo "::set-output name=date::$(date +'%Y_%m_%dT%H_%M_%S')" #no colons allowed for artifacts
 
       - uses: actions/upload-artifact@v2
         if: always()
@@ -196,9 +190,9 @@ jobs:
         uses: actions/checkout@v2
 
       - name: Set up Python
-        uses: actions/setup-python@v4.3.0
+        uses: actions/setup-python@v2
         with:
-          python-version: '3.8'
+          python-version: 3.8
 
       - name: Install python dependencies
         run: |

.github/workflows/nightly-release.yml

@@ -1,109 +0,0 @@
-# **what?**
-# Nightly releases to GitHub and PyPI. This workflow produces the following outcome:
-# - generate and validate data for night release (commit SHA, version number, release branch);
-# - pass data to release workflow;
-# - night release will be pushed to GitHub as a draft release;
-# - night build will be pushed to test PyPI;
-#
-# **why?**
-# Ensure an automated and tested release process for nightly builds
-#
-# **when?**
-# This workflow runs on schedule or can be run manually on demand.
-
-name: Nightly Test Release to GitHub and PyPI
-
-on:
-  workflow_dispatch: # for manual triggering
-  schedule:
-    - cron: 0 9 * * *
-
-permissions:
-  contents: write # this is the permission that allows creating a new release
-
-defaults:
-  run:
-    shell: bash
-
-env:
-  RELEASE_BRANCH: "main"
-
-jobs:
-  aggregate-release-data:
-    runs-on: ubuntu-latest
-
-    outputs:
-      commit_sha: ${{ steps.resolve-commit-sha.outputs.release_commit }}
-      version_number: ${{ steps.nightly-release-version.outputs.number }}
-      release_branch: ${{ steps.release-branch.outputs.name }}
-
-    steps:
-      - name: "Checkout ${{ github.repository }} Branch ${{ env.RELEASE_BRANCH }}"
-        uses: actions/checkout@v3
-        with:
-          ref: ${{ env.RELEASE_BRANCH }}
-
-      - name: "Resolve Commit To Release"
-        id: resolve-commit-sha
-        run: |
-          commit_sha=$(git rev-parse HEAD)
-          echo "release_commit=$commit_sha" >> $GITHUB_OUTPUT
-
-      - name: "Get Current Version Number"
-        id: version-number-sources
-        run: |
-          current_version=`awk -F"current_version = " '{print $2}' .bumpversion.cfg | tr '\n' ' '`
-          echo "current_version=$current_version" >> $GITHUB_OUTPUT
-
-      - name: "Audit Version And Parse Into Parts"
-        id: semver
-        uses: dbt-labs/actions/parse-semver@v1.1.0
-        with:
-          version: ${{ steps.version-number-sources.outputs.current_version }}
-
-      - name: "Get Current Date"
-        id: current-date
-        run: echo "date=$(date +'%m%d%Y')" >> $GITHUB_OUTPUT
-
-      - name: "Generate Nightly Release Version Number"
-        id: nightly-release-version
-        run: |
-          number="${{ steps.semver.outputs.version }}.dev${{ steps.current-date.outputs.date }}"
-          echo "number=$number" >> $GITHUB_OUTPUT
-
-      - name: "Audit Nightly Release Version And Parse Into Parts"
-        uses: dbt-labs/actions/parse-semver@v1.1.0
-        with:
-          version: ${{ steps.nightly-release-version.outputs.number }}
-
-      - name: "Set Release Branch"
-        id: release-branch
-        run: |
-          echo "name=${{ env.RELEASE_BRANCH }}" >> $GITHUB_OUTPUT
-
-  log-outputs-aggregate-release-data:
-    runs-on: ubuntu-latest
-    needs: [aggregate-release-data]
-
-    steps:
-      - name: "[DEBUG] Log Outputs"
-        run: |
-          echo commit_sha    : ${{ needs.aggregate-release-data.outputs.commit_sha }}
-          echo version_number: ${{ needs.aggregate-release-data.outputs.version_number }}
-          echo release_branch: ${{ needs.aggregate-release-data.outputs.release_branch }}
-
-  release-github-pypi:
-    needs: [aggregate-release-data]
-
-    uses: ./.github/workflows/release.yml
-    with:
-      sha: ${{ needs.aggregate-release-data.outputs.commit_sha }}
-      target_branch: ${{ needs.aggregate-release-data.outputs.release_branch }}
-      version_number: ${{ needs.aggregate-release-data.outputs.version_number }}
-      build_script_path: "scripts/build-dist.sh"
-      env_setup_script_path: "scripts/env-setup.sh"
-      s3_bucket_name: "core-team-artifacts"
-      package_test_command: "dbt --version"
-      test_run: true
-      nightly_release: true
-    secrets: inherit

.github/workflows/release-branch-tests.yml

@@ -28,33 +28,7 @@ on:
 permissions: read-all
 
 jobs:
-  fetch-latest-branches:
-    runs-on: ubuntu-latest
-
-    outputs:
-      latest-branches: ${{ steps.get-latest-branches.outputs.repo-branches }}
-
-    steps:
-      - name: "Fetch dbt-core Latest Branches"
-        uses: dbt-labs/actions/fetch-repo-branches@v1.1.1
-        id: get-latest-branches
-        with:
-          repo_name: ${{ github.event.repository.name }}
-          organization: "dbt-labs"
-          pat: ${{ secrets.GITHUB_TOKEN }}
-          fetch_protected_branches_only: true
-          regex: "^1.[0-9]+.latest$"
-          perform_match_method: "match"
-          retries: 3
-
-      - name: "[ANNOTATION] ${{ github.event.repository.name }} - branches to test"
-        run: |
-          title="${{ github.event.repository.name }} - branches to test"
-          message="The workflow will run tests for the following branches of the ${{ github.event.repository.name }} repo: ${{ steps.get-latest-branches.outputs.repo-branches }}"
-          echo "::notice $title::$message"
-
   kick-off-ci:
-    needs: [fetch-latest-branches]
     name: Kick-off CI
     runs-on: ubuntu-latest
 
@@ -65,9 +39,7 @@ jobs:
       max-parallel: 1
       fail-fast: false
       matrix:
-        branch: ${{ fromJSON(needs.fetch-latest-branches.outputs.latest-branches) }}
-        include:
-          - branch: 'main'
+        branch: [1.0.latest, 1.1.latest, main]
 
     steps:
     - name: Call CI workflow for ${{ matrix.branch }} branch

.github/workflows/release-docker.yml

@@ -41,9 +41,9 @@ jobs:
         id: version
         run: |
           IFS="." read -r MAJOR MINOR PATCH <<< ${{ github.event.inputs.version_number }}
-          echo "major=$MAJOR" >> $GITHUB_OUTPUT
-          echo "minor=$MINOR" >> $GITHUB_OUTPUT
-          echo "patch=$PATCH" >> $GITHUB_OUTPUT
+          echo "::set-output name=major::$MAJOR"
+          echo "::set-output name=minor::$MINOR"
+          echo "::set-output name=patch::$PATCH"
 
       - name: Is pkg 'latest'
         id: latest
@@ -70,10 +70,8 @@ jobs:
       - name: Get docker build arg
         id: build_arg
         run: |
-          BUILD_ARG_NAME=$(echo ${{ github.event.inputs.package }} | sed 's/\-/_/g')
-          BUILD_ARG_VALUE=$(echo ${{ github.event.inputs.package }} | sed 's/postgres/core/g')
-          echo "build_arg_name=$BUILD_ARG_NAME" >> $GITHUB_OUTPUT
-          echo "build_arg_value=$BUILD_ARG_VALUE" >> $GITHUB_OUTPUT
+          echo "::set-output name=build_arg_name::"$(echo ${{ github.event.inputs.package }} | sed 's/\-/_/g')
+          echo "::set-output name=build_arg_value::"$(echo ${{ github.event.inputs.package }} | sed 's/postgres/core/g')
 
       - name: Log in to the GHCR
         uses: docker/login-action@v1

.github/workflows/release.yml

@@ -1,229 +1,199 @@
 # **what?**
-# Release workflow provides the following steps:
-# - checkout the given commit;
-# - validate version in sources and changelog file for given version;
-# - bump the version and generate a changelog if needed;
-# - merge all changes to the target branch if needed;
-# - run unit and integration tests against given commit;
-# - build and package that SHA;
-# - release it to GitHub and PyPI with that specific build;
-#
+# Take the given commit, run unit tests specifically on that sha, build and
+# package it, and then release to GitHub and PyPi with that specific build
+
 # **why?**
 # Ensure an automated and tested release process
-#
-# **when?**
-# This workflow can be run manually on demand or can be called by other workflows
 
-name: Release to GitHub and PyPI
+# **when?**
+# This will only run manually with a given sha and version
+
+name: Release to GitHub and PyPi
 
 on:
   workflow_dispatch:
     inputs:
       sha:
-        description: "The last commit sha in the release"
-        type: string
-        required: true
-      target_branch:
-        description: "The branch to release from"
-        type: string
-        required: true
+       description: 'The last commit sha in the release'
+       required: true
       version_number:
-        description: "The release version number (i.e. 1.0.0b1)"
-        type: string
-        required: true
-      build_script_path:
-        description: "Build script path"
-        type: string
-        default: "scripts/build-dist.sh"
-        required: true
-      env_setup_script_path:
-        description: "Environment setup script path"
-        type: string
-        default: "scripts/env-setup.sh"
-        required: false
-      s3_bucket_name:
-        description: "AWS S3 bucket name"
-        type: string
-        default: "core-team-artifacts"
-        required: true
-      package_test_command:
-        description: "Package test command"
-        type: string
-        default: "dbt --version"
-        required: true
-      test_run:
-        description: "Test run (Publish release as draft)"
-        type: boolean
-        default: true
-        required: false
-      nightly_release:
-        description: "Nightly release to dev environment"
-        type: boolean
-        default: false
-        required: false
-  workflow_call:
-    inputs:
-      sha:
-        description: "The last commit sha in the release"
-        type: string
-        required: true
-      target_branch:
-        description: "The branch to release from"
-        type: string
-        required: true
-      version_number:
-        description: "The release version number (i.e. 1.0.0b1)"
-        type: string
-        required: true
-      build_script_path:
-        description: "Build script path"
-        type: string
-        default: "scripts/build-dist.sh"
-        required: true
-      env_setup_script_path:
-        description: "Environment setup script path"
-        type: string
-        default: "scripts/env-setup.sh"
-        required: false
-      s3_bucket_name:
-        description: "AWS S3 bucket name"
-        type: string
-        default: "core-team-artifacts"
-        required: true
-      package_test_command:
-        description: "Package test command"
-        type: string
-        default: "dbt --version"
-        required: true
-      test_run:
-        description: "Test run (Publish release as draft)"
-        type: boolean
-        default: true
-        required: false
-      nightly_release:
-        description: "Nightly release to dev environment"
-        type: boolean
-        default: false
-        required: false
-
-permissions:
-  contents: write # this is the permission that allows creating a new release
+       description: 'The release version number (i.e. 1.0.0b1)'
+       required: true
 
 defaults:
   run:
     shell: bash
 
 jobs:
-  log-inputs:
-    name: Log Inputs
+  unit:
+    name: Unit test
+
     runs-on: ubuntu-latest
+
+    env:
+      TOXENV: "unit"
+
     steps:
-      - name: "[DEBUG] Print Variables"
+      - name: Check out the repository
+        uses: actions/checkout@v2
+        with:
+          persist-credentials: false
+          ref: ${{ github.event.inputs.sha }}
+
+      - name: Set up Python
+        uses: actions/setup-python@v2
+        with:
+          python-version: 3.8
+
+      - name: Install python dependencies
         run: |
-          echo The last commit sha in the release: ${{ inputs.sha }}
-          echo The branch to release from:         ${{ inputs.target_branch }}
-          echo The release version number:         ${{ inputs.version_number }}
-          echo Build script path:                  ${{ inputs.build_script_path }}
-          echo Environment setup script path:      ${{ inputs.env_setup_script_path }}
-          echo AWS S3 bucket name:                 ${{ inputs.s3_bucket_name }}
-          echo Package test command:               ${{ inputs.package_test_command }}
-          echo Test run:                           ${{ inputs.test_run }}
-          echo Nightly release:                    ${{ inputs.nightly_release }}
+          pip install --user --upgrade pip
+          pip install tox
+          pip --version
+          tox --version
 
-  bump-version-generate-changelog:
-    name: Bump package version, Generate changelog
+      - name: Run tox
+        run: tox
 
-    uses: dbt-labs/dbt-release/.github/workflows/release-prep.yml@main
-
-    with:
-      sha: ${{ inputs.sha }}
-      version_number: ${{ inputs.version_number }}
-      target_branch: ${{ inputs.target_branch }}
-      env_setup_script_path: ${{ inputs.env_setup_script_path }}
-      test_run: ${{ inputs.test_run }}
-      nightly_release: ${{ inputs.nightly_release }}
-
-    secrets: inherit
-
-  log-outputs-bump-version-generate-changelog:
-    name: "[Log output] Bump package version, Generate changelog"
-    if: ${{ !failure() && !cancelled() }}
-
-    needs: [bump-version-generate-changelog]
+  build:
+    name: build packages
 
     runs-on: ubuntu-latest
 
     steps:
-      - name: Print variables
+      - name: Check out the repository
+        uses: actions/checkout@v2
+        with:
+          persist-credentials: false
+          ref: ${{ github.event.inputs.sha }}
+
+      - name: Set up Python
+        uses: actions/setup-python@v2
+        with:
+          python-version: 3.8
+
+      - name: Install python dependencies
         run: |
-          echo Final SHA     : ${{ needs.bump-version-generate-changelog.outputs.final_sha }}
-          echo Changelog path: ${{ needs.bump-version-generate-changelog.outputs.changelog_path }}
+          pip install --user --upgrade pip
+          pip install --upgrade setuptools wheel twine check-wheel-contents
+          pip --version
 
-  build-test-package:
-    name: Build, Test, Package
-    if: ${{ !failure() && !cancelled() }}
-    needs: [bump-version-generate-changelog]
+      - name: Build distributions
+        run: ./scripts/build-dist.sh
 
-    uses: dbt-labs/dbt-release/.github/workflows/build.yml@main
+      - name: Show distributions
+        run: ls -lh dist/
 
-    with:
-      sha: ${{ needs.bump-version-generate-changelog.outputs.final_sha }}
-      version_number: ${{ inputs.version_number }}
-      changelog_path: ${{ needs.bump-version-generate-changelog.outputs.changelog_path }}
-      build_script_path: ${{ inputs.build_script_path }}
-      s3_bucket_name: ${{ inputs.s3_bucket_name }}
-      package_test_command: ${{ inputs.package_test_command }}
-      test_run: ${{ inputs.test_run }}
-      nightly_release: ${{ inputs.nightly_release }}
+      - name: Check distribution descriptions
+        run: |
+          twine check dist/*
 
-    secrets:
-      AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
-      AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
+      - name: Check wheel contents
+        run: |
+          check-wheel-contents dist/*.whl --ignore W007,W008
+
+      - uses: actions/upload-artifact@v2
+        with:
+          name: dist
+          path: |
+            dist/
+            !dist/dbt-${{github.event.inputs.version_number}}.tar.gz
+
+  test-build:
+    name: verify packages
+
+    needs: [build, unit]
+
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Set up Python
+        uses: actions/setup-python@v2
+        with:
+          python-version: 3.8
+
+      - name: Install python dependencies
+        run: |
+          pip install --user --upgrade pip
+          pip install --upgrade wheel
+          pip --version
+
+      - uses: actions/download-artifact@v2
+        with:
+          name: dist
+          path: dist/
+
+      - name: Show distributions
+        run: ls -lh dist/
+
+      - name: Install wheel distributions
+        run: |
+          find ./dist/*.whl -maxdepth 1 -type f | xargs pip install --force-reinstall --find-links=dist/
+
+      - name: Check wheel distributions
+        run: |
+          dbt --version
+
+      - name: Install source distributions
+        run: |
+          find ./dist/*.gz -maxdepth 1 -type f | xargs pip install --force-reinstall --find-links=dist/
+
+      - name: Check source distributions
+        run: |
+          dbt --version
 
   github-release:
     name: GitHub Release
-    if: ${{ !failure() && !cancelled() }}
 
-    needs: [bump-version-generate-changelog, build-test-package]
+    needs: test-build
 
-    uses: dbt-labs/dbt-release/.github/workflows/github-release.yml@main
+    runs-on: ubuntu-latest
 
-    with:
-      sha: ${{ needs.bump-version-generate-changelog.outputs.final_sha }}
-      version_number: ${{ inputs.version_number }}
-      changelog_path: ${{ needs.bump-version-generate-changelog.outputs.changelog_path }}
-      test_run: ${{ inputs.test_run }}
+    steps:
+      - uses: actions/download-artifact@v2
+        with:
+          name: dist
+          path: '.'
+
+      # Need to set an output variable because env variables can't be taken as input
+      # This is needed for the next step with releasing to GitHub
+      - name: Find release type
+        id: release_type
+        env:
+          IS_PRERELEASE: ${{ contains(github.event.inputs.version_number, 'rc') ||  contains(github.event.inputs.version_number, 'b') }}
+        run: |
+          echo ::set-output name=isPrerelease::$IS_PRERELEASE
+
+      - name: Creating GitHub Release
+        uses: softprops/action-gh-release@v1
+        with:
+          name: dbt-core v${{github.event.inputs.version_number}}
+          tag_name: v${{github.event.inputs.version_number}}
+          prerelease: ${{ steps.release_type.outputs.isPrerelease }}
+          target_commitish: ${{github.event.inputs.sha}}
+          body: |
+            [Release notes](https://github.com/dbt-labs/dbt-core/blob/main/CHANGELOG.md)
+          files: |
+            dbt_postgres-${{github.event.inputs.version_number}}-py3-none-any.whl
+            dbt_core-${{github.event.inputs.version_number}}-py3-none-any.whl
+            dbt-postgres-${{github.event.inputs.version_number}}.tar.gz
+            dbt-core-${{github.event.inputs.version_number}}.tar.gz
 
   pypi-release:
-    name: PyPI Release
+    name: Pypi release
 
-    needs: [github-release]
+    runs-on: ubuntu-latest
 
-    uses: dbt-labs/dbt-release/.github/workflows/pypi-release.yml@main
+    needs: github-release
 
-    with:
-      version_number: ${{ inputs.version_number }}
-      test_run: ${{ inputs.test_run }}
+    environment: PypiProd
+    steps:
+      - uses: actions/download-artifact@v2
+        with:
+          name: dist
+          path: 'dist'
 
-    secrets:
-      PYPI_API_TOKEN: ${{ secrets.PYPI_API_TOKEN }}
-      TEST_PYPI_API_TOKEN: ${{ secrets.TEST_PYPI_API_TOKEN }}
-
-  slack-notification:
-    name: Slack Notification
-    if: ${{ failure() && (!inputs.test_run || inputs.nightly_release) }}
-
-    needs:
-      [
-        bump-version-generate-changelog,
-        build-test-package,
-        github-release,
-        pypi-release,
-      ]
-
-    uses: dbt-labs/dbt-release/.github/workflows/slack-post-notification.yml@main
-    with:
-      status: "failure"
-
-    secrets:
-      SLACK_WEBHOOK_URL: ${{ secrets.SLACK_DEV_CORE_ALERTS }}
+      - name: Publish distribution to PyPI
+        uses: pypa/gh-action-pypi-publish@v1.4.2
+        with:
+          password: ${{ secrets.PYPI_API_TOKEN }}

.github/workflows/schema-check.yml

@@ -21,9 +21,6 @@ on:
       - "*.latest"
       - "releases/*"
 
-# no special access is needed
-permissions: read-all
-
 env:
   LATEST_SCHEMA_PATH: ${{ github.workspace }}/new_schemas
   SCHEMA_DIFF_ARTIFACT: ${{ github.workspace }}//schema_schanges.txt

.github/workflows/stale.yml

@@ -3,10 +3,15 @@ on:
   schedule:
     - cron: "30 1 * * *"
 
-permissions:
-  issues: write
-  pull-requests: write
-
 jobs:
   stale:
-    uses: dbt-labs/actions/.github/workflows/stale-bot-matrix.yml@main
+    runs-on: ubuntu-latest
+    steps:
+      # pinned at v4 (https://github.com/actions/stale/releases/tag/v4.0.0)
+      - uses: actions/stale@cdf15f641adb27a71842045a94023bef6945e3aa
+        with:
+          stale-issue-message: "This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please remove the stale label or comment on the issue, or it will be closed in 7 days."
+          stale-pr-message: "This PR has been marked as Stale because it has been open for 180 days with no activity. If you would like the PR to remain open, please remove the stale label or comment on the PR, or it will be closed in 7 days."
+          close-issue-message: "Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest; add a comment to notify the maintainers."
+          # mark issues/PRs stale when they haven't seen activity in 180 days
+          days-before-stale: 180

.github/workflows/structured-logging-schema-check.yml

@@ -22,7 +22,7 @@ jobs:
   # run the performance measurements on the current or default branch
   test-schema:
     name: Test Log Schema
-    runs-on: ubuntu-20.04
+    runs-on: ubuntu-latest
     env:
       # turns warnings into errors
       RUSTFLAGS: "-D warnings"
@@ -30,8 +30,6 @@ jobs:
       LOG_DIR: "/home/runner/work/dbt-core/dbt-core/logs"
       # tells integration tests to output into json format
       DBT_LOG_FORMAT: "json"
-      # tell eventmgr to convert logging events into bytes
-      DBT_TEST_BINARY_SERIALIZATION: "true"
       # Additional test users
       DBT_TEST_USER_1: dbt_test_user_1
       DBT_TEST_USER_2: dbt_test_user_2
@@ -48,6 +46,12 @@ jobs:
         with:
           python-version: "3.8"
 
+      - uses: actions-rs/toolchain@v1
+        with:
+          profile: minimal
+          toolchain: stable
+          override: true
+
       - name: Install python dependencies
         run: |
           pip install --user --upgrade pip
@@ -65,3 +69,10 @@ jobs:
       # we actually care if these pass, because the normal test run doesn't usually include many json log outputs
       - name: Run integration tests
         run: tox -e integration -- -nauto
+
+      # apply our schema tests to every log event from the previous step
+      # skips any output that isn't valid json
+      - uses: actions-rs/cargo@v1
+        with:
+          command: run
+          args: --manifest-path test/interop/log_parsing/Cargo.toml

.github/workflows/version-bump.yml

@@ -1,15 +1,18 @@
 # **what?**
-# This workflow will take the new version number to bump to. With that
+# This workflow will take a version number and a dry run flag. With that
 # it will run versionbump to update the version number everywhere in the
-# code base and then run changie to create the corresponding changelog.
-# A PR will be created with the changes that can be reviewed before committing.
+# code base and then generate an update Docker requirements file. If this
+# is a dry run, a draft PR will open with the changes. If this isn't a dry
+# run, the changes will be committed to the branch this is run on.
 
 # **why?**
 # This is to aid in releasing dbt and making sure we have updated
-# the version in all places and generated the changelog.
+# the versions and Docker requirements in all places.
 
 # **when?**
-# This is triggered manually
+# This is triggered either manually OR
+# from the repository_dispatch event "version-bump" which is sent from
+# the dbt-release repo Action
 
 name: Version Bump
 
@@ -17,12 +20,92 @@ on:
   workflow_dispatch:
     inputs:
       version_number:
-       description: 'The version number to bump to (ex. 1.2.0, 1.3.0b1)'
+       description: 'The version number to bump to'
        required: true
+      is_dry_run:
+       description: 'Creates a draft PR to allow testing instead of committing to a branch'
+       required: true
+       default: 'true'
+  repository_dispatch:
+    types: [version-bump]
 
 jobs:
-  version_bump_and_changie:
-    uses: dbt-labs/actions/.github/workflows/version-bump.yml@main
-    with:
-      version_number: ${{ inputs.version_number }}
-    secrets: inherit  # ok since what we are calling is internally maintained
+  bump:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out the repository
+        uses: actions/checkout@v2
+
+      - name: Set version and dry run values
+        id: variables
+        env:
+          VERSION_NUMBER: "${{ github.event.client_payload.version_number == '' && github.event.inputs.version_number || github.event.client_payload.version_number }}"
+          IS_DRY_RUN: "${{ github.event.client_payload.is_dry_run == '' && github.event.inputs.is_dry_run || github.event.client_payload.is_dry_run }}"
+        run: |
+          echo Repository dispatch event version: ${{ github.event.client_payload.version_number }}
+          echo Repository dispatch event dry run: ${{ github.event.client_payload.is_dry_run }}
+          echo Workflow dispatch event version: ${{ github.event.inputs.version_number }}
+          echo Workflow dispatch event dry run: ${{ github.event.inputs.is_dry_run }}
+          echo ::set-output name=VERSION_NUMBER::$VERSION_NUMBER
+          echo ::set-output name=IS_DRY_RUN::$IS_DRY_RUN
+
+      - uses: actions/setup-python@v2
+        with:
+          python-version: "3.8"
+
+      - name: Install python dependencies
+        run: |
+          python3 -m venv env
+          source env/bin/activate
+          pip install --upgrade pip
+
+      - name: Create PR branch
+        if: ${{ steps.variables.outputs.IS_DRY_RUN == 'true' }}
+        run: |
+          git checkout -b bumping-version/${{steps.variables.outputs.VERSION_NUMBER}}_$GITHUB_RUN_ID
+          git push origin bumping-version/${{steps.variables.outputs.VERSION_NUMBER}}_$GITHUB_RUN_ID
+          git branch --set-upstream-to=origin/bumping-version/${{steps.variables.outputs.VERSION_NUMBER}}_$GITHUB_RUN_ID bumping-version/${{steps.variables.outputs.VERSION_NUMBER}}_$GITHUB_RUN_ID
+
+      # - name: Generate Docker requirements
+      #  run: |
+      #    source env/bin/activate
+      #    pip install -r requirements.txt
+      #    pip freeze -l > docker/requirements/requirements.txt
+      #    git status
+
+      - name: Bump version
+        run: |
+          source env/bin/activate
+          pip install -r dev-requirements.txt
+          env/bin/bumpversion --allow-dirty --new-version ${{steps.variables.outputs.VERSION_NUMBER}} major
+          git status
+
+      - name: Commit version bump directly
+        uses: EndBug/add-and-commit@v7
+        if: ${{ steps.variables.outputs.IS_DRY_RUN == 'false' }}
+        with:
+          author_name: 'Github Build Bot'
+          author_email: 'buildbot@fishtownanalytics.com'
+          message: 'Bumping version to ${{steps.variables.outputs.VERSION_NUMBER}}'
+
+      - name: Commit version bump to branch
+        uses: EndBug/add-and-commit@v7
+        if: ${{ steps.variables.outputs.IS_DRY_RUN == 'true' }}
+        with:
+          author_name: 'Github Build Bot'
+          author_email: 'buildbot@fishtownanalytics.com'
+          message: 'Bumping version to ${{steps.variables.outputs.VERSION_NUMBER}}'
+          branch: 'bumping-version/${{steps.variables.outputs.VERSION_NUMBER}}_${{GITHUB.RUN_ID}}'
+          push: 'origin origin/bumping-version/${{steps.variables.outputs.VERSION_NUMBER}}_${{GITHUB.RUN_ID}}'
+
+      - name: Create Pull Request
+        uses: peter-evans/create-pull-request@v3
+        if: ${{ steps.variables.outputs.IS_DRY_RUN == 'true' }}
+        with:
+          author: 'Github Build Bot <buildbot@fishtownanalytics.com>'
+          draft: true
+          base: ${{github.ref}}
+          title: 'Bumping version to ${{steps.variables.outputs.VERSION_NUMBER}}'
+          branch: 'bumping-version/${{steps.variables.outputs.VERSION_NUMBER}}_${{GITHUB.RUN_ID}}'
+          labels: |
+            Skip Changelog

.gitignore

@@ -11,7 +11,6 @@ __pycache__/
 env*/
 dbt_env/
 build/
-!core/dbt/docs/build
 develop-eggs/
 dist/
 downloads/
@@ -25,8 +24,7 @@ var/
 *.egg-info/
 .installed.cfg
 *.egg
-.mypy_cache/
-.dmypy.json
+*.mypy_cache/
 logs/
 
 # PyInstaller
@@ -51,7 +49,6 @@ coverage.xml
 *,cover
 .hypothesis/
 test.env
-makefile.test.env
 *.pytest_cache/
 
 
@@ -98,7 +95,3 @@ venv/
 
 # vscode
 .vscode/
-*.code-workspace
-
-# poetry
-poetry.lock

.pre-commit-config.yaml

@@ -2,11 +2,11 @@
 # Eventually the hooks described here will be run as tests before merging each PR.
 
 # TODO: remove global exclusion of tests when testing overhaul is complete
-exclude: ^(test/|core/dbt/docs/build/)
+exclude: ^test/
 
 # Force all unspecified python hooks to run python 3.8
 default_language_version:
-  python: python3
+  python: python3.8
 
 repos:
 - repo: https://github.com/pre-commit/pre-commit-hooks
@@ -24,13 +24,18 @@ repos:
   rev: 22.3.0
   hooks:
   - id: black
+    args:
+    - "--line-length=99"
+    - "--target-version=py38"
   - id: black
     alias: black-check
     stages: [manual]
     args:
+    - "--line-length=99"
+    - "--target-version=py38"
     - "--check"
     - "--diff"
-- repo: https://github.com/pycqa/flake8
+- repo: https://gitlab.com/pycqa/flake8
   rev: 4.0.1
   hooks:
   - id: flake8

CHANGELOG.md

@@ -5,95 +5,12 @@
 - "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)
 
-## dbt-core 1.5.0-b1 - February 17, 2023
-
-### Features
-
-- Data type constraints are now native to SQL table materializations. Enforce columns are specific data types and not null depending on database functionality. ([#6079](https://github.com/dbt-labs/dbt-core/issues/6079))
-- Have dbt debug spit out structured json logs with flags enabled. ([#5353](https://github.com/dbt-labs/dbt-core/issues/5353))
-- add adapter_response to dbt test and freshness result ([#2964](https://github.com/dbt-labs/dbt-core/issues/2964))
-- Improve error message for packages missing `dbt_project.yml` ([#6663](https://github.com/dbt-labs/dbt-core/issues/6663))
-- Adjust makefile to have clearer instructions for CI env var changes. ([#6689](https://github.com/dbt-labs/dbt-core/issues/6689))
-- Stand-alone Python module for PostgresColumn ([#6772](https://github.com/dbt-labs/dbt-core/issues/6772))
-- Exposure owner requires one of name or email keys, and accepts additional arbitrary keys ([#6833](https://github.com/dbt-labs/dbt-core/issues/6833))
-- Parse 'group' resource ([#6921](https://github.com/dbt-labs/dbt-core/issues/6921))
-
-### Fixes
-
-- add merge_exclude_columns adapter tests ([#6699](https://github.com/dbt-labs/dbt-core/issues/6699))
-- Include adapter_response in NodeFinished run_result log event ([#6703](https://github.com/dbt-labs/dbt-core/issues/6703))
-- Sort cli vars before hashing for partial parsing ([#6710](https://github.com/dbt-labs/dbt-core/issues/6710))
-- [Regression] exposure_content referenced incorrectly ([#6738](https://github.com/dbt-labs/dbt-core/issues/6738))
-- Remove pin on packaging and stop using it for prerelease comparisons ([#6834](https://github.com/dbt-labs/dbt-core/issues/6834))
-- Readd depends_on.macros to SeedNode, to support seeds with hooks calling macros ([#6806](https://github.com/dbt-labs/dbt-core/issues/6806))
-- Fix regression of --quiet cli parameter behavior ([#6749](https://github.com/dbt-labs/dbt-core/issues/6749))
-- Ensure results from hooks contain nodes when processing them ([#6796](https://github.com/dbt-labs/dbt-core/issues/6796))
-- Always flush stdout after logging ([#6901](https://github.com/dbt-labs/dbt-core/issues/6901))
-- Reapply logging fixes which were accidentally reverted ([#6936](https://github.com/dbt-labs/dbt-core/issues/6936))
-- Set relation_name in test nodes at compile time ([#6930](https://github.com/dbt-labs/dbt-core/issues/6930))
-- Readd initialization events, --log-cache-events in new CLI ([#6933](https://github.com/dbt-labs/dbt-core/issues/6933))
-- Fix previous state tests and disabled exposures, metrics ([#6752](https://github.com/dbt-labs/dbt-core/issues/6752), [#6753](https://github.com/dbt-labs/dbt-core/issues/6753))
-- Make use of hashlib.md5() FIPS compliant ([#6900](https://github.com/dbt-labs/dbt-core/issues/6900))
-
-### Docs
-
-- update link to installation instructions ([dbt-docs/#None](https://github.com/dbt-labs/dbt-docs/issues/None))
-- Fix JSON path to overview docs ([dbt-docs/#366](https://github.com/dbt-labs/dbt-docs/issues/366))
-- Searchable column descriptions ([dbt-docs/#140](https://github.com/dbt-labs/dbt-docs/issues/140), [dbt-docs/#322](https://github.com/dbt-labs/dbt-docs/issues/322), [dbt-docs/#369](https://github.com/dbt-labs/dbt-docs/issues/369))
-
-### Under the Hood
-
-- [CT-921] dbt compile works in click ([#5545](https://github.com/dbt-labs/dbt-core/issues/5545))
-- Fix use of ConnectionReused logging event ([#6168](https://github.com/dbt-labs/dbt-core/issues/6168))
-- Port docs tests to pytest ([#6573](https://github.com/dbt-labs/dbt-core/issues/6573))
-- Update deprecated github action command ([#6153](https://github.com/dbt-labs/dbt-core/issues/6153))
-- dbt snapshot works in click ([#5554](https://github.com/dbt-labs/dbt-core/issues/5554))
-- dbt list working with click ([#5549](https://github.com/dbt-labs/dbt-core/issues/5549))
-- Add dbt run-operation to click CLI ([#5552](https://github.com/dbt-labs/dbt-core/issues/5552))
-- dbt build working with new click framework ([#5541](https://github.com/dbt-labs/dbt-core/issues/5541))
-- dbt docs generate works with new click framework ([#5543](https://github.com/dbt-labs/dbt-core/issues/5543))
-- Replaced the EmptyLine event with a more general Formatting event, and added a Note event. ([#6481](https://github.com/dbt-labs/dbt-core/issues/6481))
-- Small optimization on manifest parsing benefitting large DAGs ([#6697](https://github.com/dbt-labs/dbt-core/issues/6697))
-- Revised and simplified various structured logging events ([#6664](https://github.com/dbt-labs/dbt-core/issues/6664), [#6665](https://github.com/dbt-labs/dbt-core/issues/6665), [#6666](https://github.com/dbt-labs/dbt-core/issues/6666))
-- dbt init works with click ([#5548](https://github.com/dbt-labs/dbt-core/issues/5548))
-- [CT-920][CT-1900] Create Click CLI runner and use it to fix dbt docs commands ([#5544](https://github.com/dbt-labs/dbt-core/issues/5544), [#6722](https://github.com/dbt-labs/dbt-core/issues/6722))
-- Migrate debug task to click ([#5546](https://github.com/dbt-labs/dbt-core/issues/5546))
--  Optimized GraphQueue to remove graph analysis bottleneck in large dags. ([#6759](https://github.com/dbt-labs/dbt-core/issues/6759))
-- Implement --version for click cli ([#6757](https://github.com/dbt-labs/dbt-core/issues/6757))
-- [CT-1841] Convert custom target test to Pytest ([#6638](https://github.com/dbt-labs/dbt-core/issues/6638))
-- Remove BigQuery-specific btye abbreviations ([#6741](https://github.com/dbt-labs/dbt-core/issues/6741))
-- warn_error/warn_error_options mutual exclusivity in click ([#6579](https://github.com/dbt-labs/dbt-core/issues/6579))
-- Enables the new Click Cli on the commandline! 🚀 ([#6784](https://github.com/dbt-labs/dbt-core/issues/6784))
-- Lazily call --version ([#6812](https://github.com/dbt-labs/dbt-core/issues/6812))
-- Moving simple_seed to adapter zone to help adapter test conversions ([#CT-1959](https://github.com/dbt-labs/dbt-core/issues/CT-1959))
-- flags.THREADS defaults to None ([#6887](https://github.com/dbt-labs/dbt-core/issues/6887))
-- Fixing target type exposure error ([#6928](https://github.com/dbt-labs/dbt-core/issues/6928))
-- Test binary serialization of logging events ([#6852](https://github.com/dbt-labs/dbt-core/issues/6852))
-
-### Dependencies
-
-- Bump ubuntu from 22.04 to 23.04 ([#6865](https://github.com/dbt-labs/dbt-core/pull/6865))
-- Revert hoisting dbt.cli.main into the dbt.name namespace ([#](https://github.com/dbt-labs/dbt-core/pull/))
-
-### Contributors
-- [@aezomz](https://github.com/aezomz) ([#2964](https://github.com/dbt-labs/dbt-core/issues/2964))
-- [@boxysean](https://github.com/boxysean) ([#6697](https://github.com/dbt-labs/dbt-core/issues/6697))
-- [@callum-mcdata](https://github.com/callum-mcdata) ([#6928](https://github.com/dbt-labs/dbt-core/issues/6928))
-- [@dave-connors-3](https://github.com/dave-connors-3) ([#6699](https://github.com/dbt-labs/dbt-core/issues/6699))
-- [@davidbloss](https://github.com/davidbloss) ([#6153](https://github.com/dbt-labs/dbt-core/issues/6153))
-- [@halvorlu](https://github.com/halvorlu) ([#366](https://github.com/dbt-labs/dbt-core/issues/366))
-- [@nielspardon](https://github.com/nielspardon) ([#6900](https://github.com/dbt-labs/dbt-core/issues/6900))
-- [@ryancharris](https://github.com/ryancharris) ([#None](https://github.com/dbt-labs/dbt-core/issues/None))
-- [@sungchun12](https://github.com/sungchun12) ([#6079](https://github.com/dbt-labs/dbt-core/issues/6079))
-
 
 ## Previous Releases
 
 For information on prior major and minor releases, see their changelogs:
 
 
-* [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)