Bumping version to 1.7.1 and generate changelog

* wip

* add tests

* changelog

* nits

* pr feedback

* nits

(cherry picked from commit 01d481bc8d)

Co-authored-by: Chenyu Li <chenyu.li@dbtlabs.com>

.bumpversion.cfg

@@ -0,0 +1,47 @@
+[bumpversion]
+current_version = 1.7.1
+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
+	)?
+	( # 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}
+commit = False
+tag = False
+
+[bumpversion:part:prekind]
+first_value = a
+optional_value = final
+values =
+	a
+	b
+	rc
+	final
+
+[bumpversion:part:num]
+first_value = 1
+
+[bumpversion:part:nightly]
+
+[bumpversion:file:core/setup.py]
+
+[bumpversion:file:core/dbt/version.py]
+
+[bumpversion:file:plugins/postgres/setup.py]
+
+[bumpversion:file:plugins/postgres/dbt/adapters/postgres/__version__.py]
+
+[bumpversion:file:docker/Dockerfile]
+
+[bumpversion:file:tests/adapter/setup.py]
+
+[bumpversion:file:tests/adapter/dbt/tests/adapter/__version__.py]

.changes/0.0.0.md

@@ -3,10 +3,6 @@
 For information on prior major and minor releases, see their changelogs:
 
 
-* [1.10](https://github.com/dbt-labs/dbt-core/blob/1.10.latest/CHANGELOG.md)
-* [1.9](https://github.com/dbt-labs/dbt-core/blob/1.9.latest/CHANGELOG.md)
-* [1.8](https://github.com/dbt-labs/dbt-core/blob/1.8.latest/CHANGELOG.md)
-* [1.7](https://github.com/dbt-labs/dbt-core/blob/1.7.latest/CHANGELOG.md)
 * [1.6](https://github.com/dbt-labs/dbt-core/blob/1.6.latest/CHANGELOG.md)
 * [1.5](https://github.com/dbt-labs/dbt-core/blob/1.5.latest/CHANGELOG.md)
 * [1.4](https://github.com/dbt-labs/dbt-core/blob/1.4.latest/CHANGELOG.md)

.changes/1.7.0.md

@@ -0,0 +1,157 @@
+## dbt-core 1.7.0 - November 02, 2023
+
+### Breaking Changes
+
+- Removed the FirstRunResultError and AfterFirstRunResultError event types, using the existing RunResultError in their place. ([#7963](https://github.com/dbt-labs/dbt-core/issues/7963))
+
+### Features
+
+- add log file of installed packages via dbt deps ([#6643](https://github.com/dbt-labs/dbt-core/issues/6643))
+- Enable re-population of metadata vars post-environment change during programmatic invocation ([#8010](https://github.com/dbt-labs/dbt-core/issues/8010))
+- Added support to configure a delimiter for a seed file, defaults to comma ([#3990](https://github.com/dbt-labs/dbt-core/issues/3990))
+- Allow specification of `create_metric: true` on measures ([#8125](https://github.com/dbt-labs/dbt-core/issues/8125))
+- Add node attributes related to compilation to run_results.json ([#7519](https://github.com/dbt-labs/dbt-core/issues/7519))
+- Add --no-inject-ephemeral-ctes flag for `compile` command, for usage by linting. ([#8480](https://github.com/dbt-labs/dbt-core/issues/8480))
+- Support configuration of semantic models with the addition of enable/disable and group enablement. ([#7968](https://github.com/dbt-labs/dbt-core/issues/7968))
+- Accept a `dbt-cloud` config in dbt_project.yml ([#8438](https://github.com/dbt-labs/dbt-core/issues/8438))
+- Support atomic replace in the global replace macro ([#8539](https://github.com/dbt-labs/dbt-core/issues/8539))
+- Use translate_type on data_type in model.columns in templates by default, remove no op `TYPE_LABELS` ([#8007](https://github.com/dbt-labs/dbt-core/issues/8007))
+- Add an option to generate static documentation ([#8614](https://github.com/dbt-labs/dbt-core/issues/8614))
+- Allow setting "access" as a config in addition to as a property ([#8383](https://github.com/dbt-labs/dbt-core/issues/8383))
+- Loosen typing requirement on renameable/replaceable relations to Iterable to allow adapters more flexibility in registering relation types, include docstrings as suggestions ([#8647](https://github.com/dbt-labs/dbt-core/issues/8647))
+- Add support for optional label in semantic_models, measures, dimensions and entities. ([#8595](https://github.com/dbt-labs/dbt-core/issues/8595), [#8755](https://github.com/dbt-labs/dbt-core/issues/8755))
+- Allow adapters to include package logs in dbt standard logging  ([#7859](https://github.com/dbt-labs/dbt-core/issues/7859))
+- Support storing test failures as views ([#6914](https://github.com/dbt-labs/dbt-core/issues/6914))
+- resolve packages with same git repo and unique subdirectory ([#5374](https://github.com/dbt-labs/dbt-core/issues/5374))
+- Add new ResourceReport event to record memory/cpu/io metrics ([#8342](https://github.com/dbt-labs/dbt-core/issues/8342))
+- Adding `date_spine` macro (and supporting macros) from dbt-utils to dbt-core ([#8172](https://github.com/dbt-labs/dbt-core/issues/8172))
+- Support `fill_nulls_with` and `join_to_timespine` for metric nodes ([#8593](https://github.com/dbt-labs/dbt-core/issues/8593), [#8755](https://github.com/dbt-labs/dbt-core/issues/8755))
+- Raise a warning when a contracted model has a numeric field without scale defined ([#8183](https://github.com/dbt-labs/dbt-core/issues/8183))
+- Added support for retrieving partial catalog information from a schema ([#8521](https://github.com/dbt-labs/dbt-core/issues/8521))
+- Add meta attribute to SemanticModels config ([#8511](https://github.com/dbt-labs/dbt-core/issues/8511))
+- Selectors with docs generate limits catalog generation ([#6014](https://github.com/dbt-labs/dbt-core/issues/6014))
+- Allow freshness to be determined via DBMS metadata for supported adapters ([#8704](https://github.com/dbt-labs/dbt-core/issues/8704))
+- Add support semantic layer SavedQuery node type ([#8594](https://github.com/dbt-labs/dbt-core/issues/8594))
+- Add exports to SavedQuery spec ([#8892](https://github.com/dbt-labs/dbt-core/issues/8892))
+
+### Fixes
+
+- Copy dir during `dbt deps` if symlink fails ([#7428](https://github.com/dbt-labs/dbt-core/issues/7428), [#8223](https://github.com/dbt-labs/dbt-core/issues/8223))
+- If --profile specified with dbt-init, create the project with the specified profile ([#6154](https://github.com/dbt-labs/dbt-core/issues/6154))
+- Fixed double-underline ([#5301](https://github.com/dbt-labs/dbt-core/issues/5301))
+- Copy target_schema from config into snapshot node ([#6745](https://github.com/dbt-labs/dbt-core/issues/6745))
+- Enable converting deprecation warnings to errors ([#8130](https://github.com/dbt-labs/dbt-core/issues/8130))
+- Add status to Parse Inline Error ([#8173](https://github.com/dbt-labs/dbt-core/issues/8173))
+- Ensure `warn_error_options` get serialized in `invocation_args_dict` ([#7694](https://github.com/dbt-labs/dbt-core/issues/7694))
+- Stop detecting materialization macros based on macro name ([#6231](https://github.com/dbt-labs/dbt-core/issues/6231))
+- Update `dbt deps` download retry logic to handle `EOFError` exceptions ([#6653](https://github.com/dbt-labs/dbt-core/issues/6653))
+- Improve handling of CTE injection with ephemeral models ([#8213](https://github.com/dbt-labs/dbt-core/issues/8213))
+- Fix unbound local variable error in `checked_agg_time_dimension_for_measure` ([#8230](https://github.com/dbt-labs/dbt-core/issues/8230))
+- Ensure runtime errors are raised for graph runnable tasks (compile, show, run, etc) ([#8166](https://github.com/dbt-labs/dbt-core/issues/8166))
+- Fix retry not working with log-file-max-bytes ([#8297](https://github.com/dbt-labs/dbt-core/issues/8297))
+- Add explicit support for integers for the show command ([#8153](https://github.com/dbt-labs/dbt-core/issues/8153))
+- Detect changes to model access, version, or latest_version in state:modified ([#8189](https://github.com/dbt-labs/dbt-core/issues/8189))
+- Add connection status into list of statuses for dbt debug ([#8350](https://github.com/dbt-labs/dbt-core/issues/8350))
+- fix fqn-selection for external versioned models ([#8374](https://github.com/dbt-labs/dbt-core/issues/8374))
+- Fix: DbtInternalError after model that previously ref'd external model is deleted ([#8375](https://github.com/dbt-labs/dbt-core/issues/8375))
+- Fix using list command with path selector and project-dir ([#8385](https://github.com/dbt-labs/dbt-core/issues/8385))
+- Remedy performance regression by only writing run_results.json once. ([#8360](https://github.com/dbt-labs/dbt-core/issues/8360))
+- Add support for swapping materialized views with tables/views and vice versa ([#8449](https://github.com/dbt-labs/dbt-core/issues/8449))
+- Turn breaking changes to contracted models into warnings for unversioned models ([#8384](https://github.com/dbt-labs/dbt-core/issues/8384), [#8282](https://github.com/dbt-labs/dbt-core/issues/8282))
+- Ensure parsing does not break when `window_groupings` is not specified for `non_additive_dimension` ([#8453](https://github.com/dbt-labs/dbt-core/issues/8453))
+- fix ambiguous reference error for tests and versions when model name is duplicated across packages ([#8327](https://github.com/dbt-labs/dbt-core/issues/8327), [#8493](https://github.com/dbt-labs/dbt-core/issues/8493))
+- Fix "Internal Error: Expected node <unique-id> not found in manifest" when depends_on set on ModelNodeArgs ([#8506](https://github.com/dbt-labs/dbt-core/issues/8506))
+- Fix snapshot success message ([#7583](https://github.com/dbt-labs/dbt-core/issues/7583))
+- Parse the correct schema version from manifest ([#8544](https://github.com/dbt-labs/dbt-core/issues/8544))
+- make version comparison insensitive to order ([#8571](https://github.com/dbt-labs/dbt-core/issues/8571))
+- Update metric helper functions to work with new semantic layer metrics ([#8134](https://github.com/dbt-labs/dbt-core/issues/8134))
+- Disallow cleaning paths outside current working directory ([#8318](https://github.com/dbt-labs/dbt-core/issues/8318))
+- Warn when --state == --target ([#8160](https://github.com/dbt-labs/dbt-core/issues/8160))
+- update dbt show to include limit in DWH query  ([#8496,](https://github.com/dbt-labs/dbt-core/issues/8496,), [#8417](https://github.com/dbt-labs/dbt-core/issues/8417))
+- Support quoted parameter list for MultiOption CLI options. ([#8598](https://github.com/dbt-labs/dbt-core/issues/8598))
+- Support global flags passed in after subcommands ([#6497](https://github.com/dbt-labs/dbt-core/issues/6497))
+- Lower bound of `8.0.2` for `click` ([#8683](https://github.com/dbt-labs/dbt-core/issues/8683))
+- Fixes test type edges filter ([#8692](https://github.com/dbt-labs/dbt-core/issues/8692))
+- semantic models in graph selection ([#8589](https://github.com/dbt-labs/dbt-core/issues/8589))
+- Support doc blocks in nested semantic model YAML ([#8509](https://github.com/dbt-labs/dbt-core/issues/8509))
+- avoid double-rendering sql_header in dbt show ([#8739](https://github.com/dbt-labs/dbt-core/issues/8739))
+- Fix tag selection for projects with semantic models ([#8749](https://github.com/dbt-labs/dbt-core/issues/8749))
+- Foreign key constraint on incremental model results in Database Error ([#8022](https://github.com/dbt-labs/dbt-core/issues/8022))
+- Support docs blocks on versioned model column descriptions ([#8540](https://github.com/dbt-labs/dbt-core/issues/8540))
+- Enable seeds to be handled from stored manifest data ([#6875](https://github.com/dbt-labs/dbt-core/issues/6875))
+- Override path-like args in dbt retry ([#8682](https://github.com/dbt-labs/dbt-core/issues/8682))
+- Group updates on unmodified nodes are handled gracefully for state:modified ([#8371](https://github.com/dbt-labs/dbt-core/issues/8371))
+- Partial parsing fix for adding groups and updating models at the same time ([#8697](https://github.com/dbt-labs/dbt-core/issues/8697))
+- Fix partial parsing not working for semantic model change ([#8859](https://github.com/dbt-labs/dbt-core/issues/8859))
+- Rework get_catalog implementation to retain previous adapter interface semantics ([#8846](https://github.com/dbt-labs/dbt-core/issues/8846))
+- Add back contract enforcement for temporary tables on postgres ([#8857](https://github.com/dbt-labs/dbt-core/issues/8857))
+- Add version to fqn when version==0 ([#8836](https://github.com/dbt-labs/dbt-core/issues/8836))
+- Fix cased comparison in catalog-retrieval function. ([#8939](https://github.com/dbt-labs/dbt-core/issues/8939))
+- Catalog queries now assign the correct type to materialized views ([#8864](https://github.com/dbt-labs/dbt-core/issues/8864))
+- Make relation filtering None-tolerant for maximal flexibility across adapters. ([#8974](https://github.com/dbt-labs/dbt-core/issues/8974))
+
+### Docs
+
+- Corrected spelling of "Partiton" ([dbt-docs/#8100](https://github.com/dbt-labs/dbt-docs/issues/8100))
+- Remove static SQL codeblock for metrics ([dbt-docs/#436](https://github.com/dbt-labs/dbt-docs/issues/436))
+- fixed comment util.py ([dbt-docs/#None](https://github.com/dbt-labs/dbt-docs/issues/None))
+- Fix newline escapes and improve formatting in docker README ([dbt-docs/#8211](https://github.com/dbt-labs/dbt-docs/issues/8211))
+- Display contract and column constraints on the model page ([dbt-docs/#433](https://github.com/dbt-labs/dbt-docs/issues/433))
+- Display semantic model details in docs ([dbt-docs/#431](https://github.com/dbt-labs/dbt-docs/issues/431))
+
+### Under the Hood
+
+- Switch from hologram to mashumaro jsonschema ([#8426](https://github.com/dbt-labs/dbt-core/issues/8426))
+- Refactor flaky test pp_versioned_models ([#7781](https://github.com/dbt-labs/dbt-core/issues/7781))
+- format exception from dbtPlugin.initialize ([#8152](https://github.com/dbt-labs/dbt-core/issues/8152))
+- A way to control maxBytes for a single dbt.log file ([#8199](https://github.com/dbt-labs/dbt-core/issues/8199))
+- Ref expressions with version can now be processed by the latest version of the high-performance dbt-extractor library. ([#7688](https://github.com/dbt-labs/dbt-core/issues/7688))
+- Bump manifest schema version to v11, freeze manifest v10 ([#8333](https://github.com/dbt-labs/dbt-core/issues/8333))
+- add tracking for plugin.get_nodes calls ([#8344](https://github.com/dbt-labs/dbt-core/issues/8344))
+- add internal flag: --no-partial-parse-file-diff to inform whether to compute a file diff during partial parsing ([#8363](https://github.com/dbt-labs/dbt-core/issues/8363))
+- Add return values to a number of functions for mypy ([#8389](https://github.com/dbt-labs/dbt-core/issues/8389))
+- Fix mypy warnings for ManifestLoader.load() ([#8401](https://github.com/dbt-labs/dbt-core/issues/8401))
+- Use python version 3.10.7 in Docker image. ([#8444](https://github.com/dbt-labs/dbt-core/issues/8444))
+- Re-organize jinja macros: relation-specific in /macros/adapters/relations/<relation>, relation agnostic in /macros/relations ([#8449](https://github.com/dbt-labs/dbt-core/issues/8449))
+- Update typing to meet mypy standards ([#8396](https://github.com/dbt-labs/dbt-core/issues/8396))
+- Mypy errors - adapters/factory.py ([#8387](https://github.com/dbt-labs/dbt-core/issues/8387))
+- Added more type annotations. ([#8537](https://github.com/dbt-labs/dbt-core/issues/8537))
+- Audit potential circular dependencies ([#8349](https://github.com/dbt-labs/dbt-core/issues/8349))
+- Add functional test for advanced ref override ([#8566](https://github.com/dbt-labs/dbt-core/issues/8566))
+- Add typing to __init__ in base.py ([#8398](https://github.com/dbt-labs/dbt-core/issues/8398))
+- Fix untyped functions in task/runnable.py (mypy warning) ([#8402](https://github.com/dbt-labs/dbt-core/issues/8402))
+- add a test for ephemeral cte injection ([#8225](https://github.com/dbt-labs/dbt-core/issues/8225))
+- Fix test_numeric_values to look for more specific strings ([#8470](https://github.com/dbt-labs/dbt-core/issues/8470))
+- Pin types-requests<2.31.0 in `dev-requirements.txt` ([#8789](https://github.com/dbt-labs/dbt-core/issues/8789))
+- Add warning_tag to UnversionedBreakingChange ([#8827](https://github.com/dbt-labs/dbt-core/issues/8827))
+- Update v10 manifest schema to match 1.6 for testing schema compatibility ([#8835](https://github.com/dbt-labs/dbt-core/issues/8835))
+- Add a no-op runner for Saved Qeury ([#8893](https://github.com/dbt-labs/dbt-core/issues/8893))
+
+### Dependencies
+
+- Bump mypy from 1.3.0 to 1.4.0 ([#7912](https://github.com/dbt-labs/dbt-core/pull/7912))
+- Bump mypy from 1.4.0 to 1.4.1 ([#8219](https://github.com/dbt-labs/dbt-core/pull/8219))
+- Update pin for click<9 ([#8232](https://github.com/dbt-labs/dbt-core/pull/8232))
+- Add upper bound to sqlparse pin of <0.5 ([#8236](https://github.com/dbt-labs/dbt-core/pull/8236))
+- Support dbt-semantic-interfaces 0.2.0 ([#8250](https://github.com/dbt-labs/dbt-core/pull/8250))
+- Bump docker/build-push-action from 4 to 5 ([#8783](https://github.com/dbt-labs/dbt-core/pull/8783))
+- Upgrade dbt-semantic-interfaces dep to 0.3.0 ([#8819](https://github.com/dbt-labs/dbt-core/pull/8819))
+- Begin using DSI 0.4.x ([#8892](https://github.com/dbt-labs/dbt-core/pull/8892))
+
+### Contributors
+- [@anjutiwari](https://github.com/anjutiwari) ([#7428](https://github.com/dbt-labs/dbt-core/issues/7428), [#8223](https://github.com/dbt-labs/dbt-core/issues/8223))
+- [@benmosher](https://github.com/benmosher) ([#8480](https://github.com/dbt-labs/dbt-core/issues/8480))
+- [@d-kaneshiro](https://github.com/d-kaneshiro) ([#None](https://github.com/dbt-labs/dbt-core/issues/None))
+- [@dave-connors-3](https://github.com/dave-connors-3) ([#8153](https://github.com/dbt-labs/dbt-core/issues/8153), [#8589](https://github.com/dbt-labs/dbt-core/issues/8589))
+- [@dylan-murray](https://github.com/dylan-murray) ([#8683](https://github.com/dbt-labs/dbt-core/issues/8683))
+- [@ezraerb](https://github.com/ezraerb) ([#6154](https://github.com/dbt-labs/dbt-core/issues/6154))
+- [@gem7318](https://github.com/gem7318) ([#8010](https://github.com/dbt-labs/dbt-core/issues/8010))
+- [@jamezrin](https://github.com/jamezrin) ([#8211](https://github.com/dbt-labs/dbt-core/issues/8211))
+- [@jusbaldw](https://github.com/jusbaldw) ([#6643](https://github.com/dbt-labs/dbt-core/issues/6643))
+- [@lllong33](https://github.com/lllong33) ([#5301](https://github.com/dbt-labs/dbt-core/issues/5301))
+- [@marcodamore](https://github.com/marcodamore) ([#436](https://github.com/dbt-labs/dbt-core/issues/436))
+- [@mescanne](https://github.com/mescanne) ([#8614](https://github.com/dbt-labs/dbt-core/issues/8614))
+- [@pgoslatara](https://github.com/pgoslatara) ([#8100](https://github.com/dbt-labs/dbt-core/issues/8100))
+- [@philippeboyd](https://github.com/philippeboyd) ([#5374](https://github.com/dbt-labs/dbt-core/issues/5374))
+- [@ramonvermeulen](https://github.com/ramonvermeulen) ([#3990](https://github.com/dbt-labs/dbt-core/issues/3990))
+- [@renanleme](https://github.com/renanleme) ([#8692](https://github.com/dbt-labs/dbt-core/issues/8692))

.changes/1.7.1.md

@@ -0,0 +1,8 @@
+## dbt-core 1.7.1 - November 07, 2023
+
+### Fixes
+
+- Fix compilation exception running empty seed file and support new Integer agate data_type ([#8895](https://github.com/dbt-labs/dbt-core/issues/8895))
+- Update run_results.json from previous versions of dbt to support deferral and rerun from failure ([#9010](https://github.com/dbt-labs/dbt-core/issues/9010))
+- Use MANIFEST.in to recursively include all jinja templates; fixes issue where some templates were not included in the distribution ([#9016](https://github.com/dbt-labs/dbt-core/issues/9016))
+- Fix git repository with subdirectory for Deps ([#9000](https://github.com/dbt-labs/dbt-core/issues/9000))

.changes/header.tpl.md

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

.changes/unreleased/Dependencies-20251118-155354.yaml

@@ -1,6 +0,0 @@
-kind: Dependencies
-body: Use EventCatcher from dbt-common instead of maintaining a local copy
-time: 2025-11-18T15:53:54.284561+05:30
-custom:
-    Author: 3loka
-    Issue: "12124"

.changes/unreleased/Features-20251006-140352.yaml

@@ -1,6 +0,0 @@
-kind: Features
-body: Support partial parsing for function nodes
-time: 2025-10-06T14:03:52.258104-05:00
-custom:
-  Author: QMalcolm
-  Issue: "12072"

.changes/unreleased/Features-20251117-141053.yaml

@@ -1,6 +0,0 @@
-kind: Features
-body: Allow for defining funciton arguments with default values
-time: 2025-11-17T14:10:53.860178-06:00
-custom:
-  Author: QMalcolm
-  Issue: "12044"

.changes/unreleased/Features-20251201-165209.yaml

@@ -1,6 +0,0 @@
-kind: Features
-body: Raise jsonschema-based deprecation warnings by default
-time: 2025-12-01T16:52:09.354436-05:00
-custom:
-    Author: michelleark
-    Issue: 12240

.changes/unreleased/Features-20251203-122926.yaml

@@ -1,6 +0,0 @@
-kind: Features
-body: ':bug: :snowman: Disable unit tests whose model is disabled'
-time: 2025-12-03T12:29:26.209248-05:00
-custom:
-    Author: michelleark
-    Issue: "10540"

.changes/unreleased/Features-20251210-202001.yaml

@@ -1,6 +0,0 @@
-kind: Features
-body: Implement config.meta_get and config.meta_require
-time: 2025-12-10T20:20:01.354288-05:00
-custom:
-    Author: gshank
-    Issue: "12012"

.changes/unreleased/Fixes-20250922-151726.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Address Click 8.2+ deprecation warning
-time: 2025-09-22T15:17:26.983151-06:00
-custom:
-    Author: edgarrmondragon
-    Issue: "12038"

.changes/unreleased/Fixes-20251117-140649.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Include macros in unit test parsing
-time: 2025-11-17T14:06:49.518566-05:00
-custom:
-    Author: michelleark nathanskone
-    Issue: "10157"

.changes/unreleased/Fixes-20251117-185025.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Allow dbt deps to run when vars lack defaults in dbt_project.yml
-time: 2025-11-17T18:50:25.759091+05:30
-custom:
-    Author: 3loka
-    Issue: "8913"

.changes/unreleased/Fixes-20251118-171106.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Restore DuplicateResourceNameError for intra-project node name duplication, behind behavior flag `require_unique_project_resource_names`
-time: 2025-11-18T17:11:06.454784-05:00
-custom:
-    Author: michelleark
-    Issue: "12152"

.changes/unreleased/Fixes-20251119-195034.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Allow the usage of `function` with `--exclude-resource-type` flag
-time: 2025-11-19T19:50:34.703236-06:00
-custom:
-  Author: QMalcolm
-  Issue: "12143"

.changes/unreleased/Fixes-20251124-155629.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Fix bug where schemas of functions weren't guaranteed to exist
-time: 2025-11-24T15:56:29.467004-06:00
-custom:
-  Author: QMalcolm
-  Issue: "12142"

.changes/unreleased/Fixes-20251124-155756.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Fix generation of deprecations summary
-time: 2025-11-24T15:57:56.544123-08:00
-custom:
-    Author: asiunov
-    Issue: "12146"

.changes/unreleased/Fixes-20251124-170855.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: ':bug: :snowman: Correctly reference foreign key references when --defer and --state provided'
-time: 2025-11-24T17:08:55.387946-05:00
-custom:
-    Author: michellark
-    Issue: "11885"

.changes/unreleased/Fixes-20251125-120246.yaml

@@ -1,7 +0,0 @@
-kind: Fixes
-body: ':bug: :snowman: Add exception when using --state and referring to a removed
-  test'
-time: 2025-11-25T12:02:46.635026-05:00
-custom:
-  Author: emmyoop
-  Issue: "10630"

.changes/unreleased/Fixes-20251125-122020.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: ':bug: :snowman: Stop emitting `NoNodesForSelectionCriteria` three times during `build` command'
-time: 2025-11-25T12:20:20.132379-06:00
-custom:
-  Author: QMalcolm
-  Issue: "11627"

.changes/unreleased/Fixes-20251127-141308.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: ":bug: :snowman: Fix long Python stack traces appearing when package dependencies have incompatible version requirements"
-time: 2025-11-27T14:13:08.082542-05:00
-custom:
-  Author: emmyoop
-  Issue: "12049"

.changes/unreleased/Fixes-20251127-145929.yaml

@@ -1,7 +0,0 @@
-kind: Fixes
-body: ':bug: :snowman: Fixed issue where changing data type size/precision/scale (e.g.,
-  varchar(3) to varchar(10)) incorrectly triggered a breaking change error fo'
-time: 2025-11-27T14:59:29.256274-05:00
-custom:
-  Author: emmyoop
-  Issue: "11186"

.changes/unreleased/Fixes-20251127-170124.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: ':bug: :snowman: Support unit testing models that depend on sources with the same name'
-time: 2025-11-27T17:01:24.193516-05:00
-custom:
-    Author: michelleark
-    Issue: 11975 10433

.changes/unreleased/Fixes-20251128-102129.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Fix bug in partial parsing when updating a model with a schema file that is referenced by a singular test
-time: 2025-11-28T10:21:29.911147Z
-custom:
-    Author: mattogburke
-    Issue: "12223"

.changes/unreleased/Fixes-20251128-122838.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: ':bug: :snowman: Avoid retrying successful run-operation commands'
-time: 2025-11-28T12:28:38.546261-05:00
-custom:
-    Author: michelleark
-    Issue: "11850"

.changes/unreleased/Fixes-20251128-161937.yaml

@@ -1,7 +0,0 @@
-kind: Fixes
-body: ':bug: :snowman: Fix `dbt deps --add-package` crash when packages.yml contains `warn-unpinned:
-  false`'
-time: 2025-11-28T16:19:37.608722-05:00
-custom:
-  Author: emmyoop
-  Issue: "9104"

.changes/unreleased/Fixes-20251128-163144.yaml

@@ -1,7 +0,0 @@
-kind: Fixes
-body: ':bug: :snowman: Improve `dbt deps --add-package` duplicate detection with better
-  cross-source matching and word boundaries'
-time: 2025-11-28T16:31:44.344099-05:00
-custom:
-  Author: emmyoop
-  Issue: "12239"

.changes/unreleased/Fixes-20251202-133705.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: ':bug: :snowman: Fix false positive deprecation warning of pre/post-hook SQL configs'
-time: 2025-12-02T13:37:05.012112-05:00
-custom:
-    Author: michelleark
-    Issue: "12244"

.changes/unreleased/Fixes-20251209-175031.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Ensure recent deprecation warnings include event name in message
-time: 2025-12-09T17:50:31.334618-06:00
-custom:
-  Author: QMalcolm
-  Issue: "12264"

.changes/unreleased/Fixes-20251210-143935.yaml

@@ -1,6 +0,0 @@
-kind: Fixes
-body: Improve error message clarity when detecting nodes with space in name
-time: 2025-12-10T14:39:35.107841-08:00
-custom:
-    Author: michelleark
-    Issue: "11835"

.changes/unreleased/Under the Hood-20251119-110110.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Update jsonschemas for schema.yml and dbt_project.yml deprecations
-time: 2025-11-19T11:01:10.616676-05:00
-custom:
-    Author: michelleark
-    Issue: "12180"

.changes/unreleased/Under the Hood-20251121-140515.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Replace setuptools and tox with hatch for build, test, and environment management.
-time: 2025-11-21T14:05:15.838252-05:00
-custom:
-  Author: emmyoop
-  Issue: "12151"

.changes/unreleased/Under the Hood-20251209-131857.yaml

@@ -1,6 +0,0 @@
-kind: Under the Hood
-body: Add add_catalog_integration call even if we have a pre-existing manifest
-time: 2025-12-09T13:18:57.043254-08:00
-custom:
-  Author: colin-rogers-dbt
-  Issue: "12262"

.changie.yaml

@@ -31,7 +31,43 @@ kinds:
       - {{.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
@@ -41,33 +77,47 @@ newlines:
   endOfVersion: 1
 
 custom:
-  - key: Author
-    label: GitHub Username(s) (separated by a single space if multiple)
-    type: string
-    minLength: 3
-  - key: Issue
-    label: GitHub Issue Number (separated by a single space if multiple)
-    type: string
-    minLength: 1
+- key: Author
+  label: GitHub Username(s) (separated by a single space if multiple)
+  type: string
+  minLength: 3
+- key: Issue
+  label: GitHub Issue Number (separated by a single space if multiple)
+  type: string
+  minLength: 1
 
 footerFormat: |
   {{- $contributorDict := dict }}
-  {{- /* ensure we always skip snyk and dependabot */}}
-  {{- $bots := list "dependabot[bot]" "snyk-bot"}}
+  {{- /* ensure all names in this list are all lowercase for later matching purposes */}}
+  {{- $core_team := splitList " " .Env.CORE_TEAM }}
+  {{- /* ensure we always skip snyk and dependabot in addition to the core team */}}
+  {{- $maintainers := list "dependabot[bot]" "snyk-bot"}}
+  {{- range $team_member := $core_team }}
+    {{- $team_member_lower := lower $team_member }}
+    {{- $maintainers = append $maintainers $team_member_lower }}
+  {{- end }}
   {{- range $change := .Changes }}
     {{- $authorList := splitList " " $change.Custom.Author }}
     {{- /* loop through all authors for a single changelog */}}
     {{- range $author := $authorList }}
       {{- $authorLower := lower $author }}
-      {{- /* we only want to include non-bot contributors */}}
-      {{- if not (has $authorLower $bots)}}
+      {{- /* we only want to include non-core team contributors */}}
+      {{- if not (has $authorLower $maintainers)}}
         {{- $changeList := splitList " " $change.Custom.Author }}
           {{- $IssueList := list }}
           {{- $changeLink := $change.Kind }}
-          {{- $changes := splitList " " $change.Custom.Issue }}
-          {{- range $issueNbr := $changes }}
-            {{- $changeLink := "[#nbr](https://github.com/dbt-labs/dbt-core/issues/nbr)" | replace "nbr" $issueNbr }}
-            {{- $IssueList = append $IssueList $changeLink  }}
+          {{- 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 }}

.flake8

@@ -7,8 +7,6 @@ ignore =
     W503 # makes Flake8 work like black
     W504
     E203 # makes Flake8 work like black
-    E704 # makes Flake8 work like black
     E741
     E501 # long line checking is done in black
-per-file-ignores =
-    */__init__.py: F401
+exclude = test/

.gitattributes

@@ -1,4 +1,4 @@
-core/dbt/task/docs/index.html binary
+core/dbt/include/index.html binary
 tests/functional/artifacts/data/state/*/manifest.json binary
 core/dbt/docs/build/html/searchindex.js binary
 core/dbt/docs/build/html/index.html binary

.github/CODEOWNERS

@@ -13,6 +13,31 @@
 # the core team as a whole will be assigned
 *       @dbt-labs/core-team
 
+### ADAPTERS
+
+# Adapter interface ("base" + "sql" adapter defaults, cache)
+/core/dbt/adapters              @dbt-labs/core-adapters
+
+# Global project (default macros + materializations), starter project
+/core/dbt/include               @dbt-labs/core-adapters
+
+# Postgres plugin
+/plugins/                       @dbt-labs/core-adapters
+/plugins/postgres/setup.py      @dbt-labs/core-adapters
+
+# Functional tests for adapter plugins
+/tests/adapter                  @dbt-labs/core-adapters
+
+### TESTS
+
+# Overlapping ownership for vast majority of unit + functional tests
+
+# Perf regression testing framework
+# This excludes the test project files itself since those aren't specific
+# framework changes (excluded by not setting an owner next to it- no owner)
+/performance                    @nathaniel-may
+/performance/projects
+
 ### ARTIFACTS
 
 /schemas/dbt                    @dbt-labs/cloud-artifacts

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -61,8 +61,8 @@ body:
       label: Environment
       description: |
         examples:
-          - **OS**: Ubuntu 24.04
-          - **Python**: 3.10.12 (`python3 --version`)
+          - **OS**: Ubuntu 20.04
+          - **Python**: 3.9.12 (`python3 --version`)
           - **dbt-core**: 1.1.1 (`dbt --version`)
       value: |
         - OS:

.github/ISSUE_TEMPLATE/code-docs.yml

@@ -1,18 +0,0 @@
-name: 📄 Code docs
-description: Report an issue for markdown files within this repo, such as README, ARCHITECTURE, etc.
-title: "[Code docs] <title>"
-labels: ["triage"]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Thanks for taking the time to fill out this code docs issue!
-  - type: textarea
-    attributes:
-      label: Please describe the issue and your proposals.
-      description: |
-        Links? References? Anything that will give us more context about the issue you are encountering!
-
-        Tip: You can attach images by clicking this area to highlight it and then dragging files in.
-    validations:
-      required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -1,8 +1,5 @@
 blank_issues_enabled: false
 contact_links:
-  - name: Documentation
-    url: https://github.com/dbt-labs/docs.getdbt.com/issues/new/choose
-    about: Problems and issues with dbt product documentation hosted on docs.getdbt.com. Issues for markdown files within this repo, such as README, should be opened using the "Code docs" template.
   - name: Ask the community for help
     url: https://github.com/dbt-labs/docs.getdbt.com/discussions
     about: Need help troubleshooting? Check out our guide on how to ask
@@ -12,6 +9,15 @@ contact_links:
   - 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 adapters
-    url: https://github.com/dbt-labs/dbt-adapters/issues/new/choose
-    about: Report a bug or request a feature for an adapter
+  - name: Create an issue for dbt-redshift
+    url: https://github.com/dbt-labs/dbt-redshift/issues/new/choose
+    about: Report a bug or request a feature for dbt-redshift
+  - name: Create an issue for dbt-bigquery
+    url: https://github.com/dbt-labs/dbt-bigquery/issues/new/choose
+    about: Report a bug or request a feature for dbt-bigquery
+  - name: Create an issue for dbt-snowflake
+    url: https://github.com/dbt-labs/dbt-snowflake/issues/new/choose
+    about: Report a bug or request a feature for dbt-snowflake
+  - name: Create an issue for dbt-spark
+    url: https://github.com/dbt-labs/dbt-spark/issues/new/choose
+    about: Report a bug or request a feature for dbt-spark

.github/ISSUE_TEMPLATE/implementation-ticket.yml

@@ -30,16 +30,6 @@ body:
         What is the definition of done for this ticket? Include any relevant edge cases and/or test cases
     validations:
       required: true
-  - type: textarea
-    attributes:
-      label: Suggested Tests
-      description: |
-        Provide scenarios to test.  Link to existing similar tests if appropriate.
-      placeholder: |
-         1. Test with no version specified in the schema file and use selection logic on a versioned model for a specific version.  Expect pass.
-         2. Test with a version specified in the schema file that is no valid.  Expect ParsingError.
-    validations:
-      required: true
   - type: textarea
     attributes:
       label: Impact to Other Teams
@@ -62,6 +52,7 @@ body:
     attributes:
       label: Context
       description: |
-        Provide the "why", motivation, and alternative approaches considered -- linking to previous refinement issues, spikes and documentation as appropriate
+        Provide the "why", motivation, and alternative approaches considered -- linking to previous refinement issues, spikes, Notion docs as appropriate
+          validations:
     validations:
       required: false

.github/ISSUE_TEMPLATE/regression-report.yml

@@ -55,8 +55,8 @@ body:
       label: Environment
       description: |
         examples:
-          - **OS**: Ubuntu 24.04
-          - **Python**: 3.10.12 (`python3 --version`)
+          - **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: |

.github/_README.md

@@ -47,8 +47,7 @@ ___
 
 ### How to re-run jobs
 
-- From the UI you can rerun from failure
-- You can retrigger the cla check by commenting on the PR with `@cla-bot check`
+- 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`
 
 ___
 
@@ -120,7 +119,7 @@ Some triggers of note that we use:
   ```yaml
   jobs:
     dependency_changelog:
-      runs-on: ${{ vars.UBUNTU_LATEST }}
+      runs-on: ubuntu-latest
 
       steps:
       - name: Get File Name Timestamp
@@ -188,12 +187,6 @@ ___
 - 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.
 
-### Runners
-- We dynamically set runners based on repository vars.  Admins can view repository vars and reset them.  Current values are the following but are subject to change:
-  - `vars.UBUNTU_LATEST` -> `ubuntu-latest`
-  - `vars.WINDOWS_LATEST` -> `windows-latest`
-  - `vars.MACOS_LATEST` -> `macos-14`
-
 ### 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

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

@@ -33,7 +33,7 @@ on:
 
 jobs:
   build:
-    runs-on: ${{ vars.UBUNTU_LATEST }}
+    runs-on: ubuntu-latest
     steps:
     - uses: actions/checkout@v3
     - name: Wrangle latest tag

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

@@ -1,21 +1,20 @@
-name: "GitHub package `latest` tag wrangler for containers"
-description: "Determines if the published image should include `latest` tags"
-
+name: "Github package 'latest' tag wrangler for containers"
+description: "Determines wether or not a given dbt container should be given a bare 'latest' tag (I.E. dbt-core:latest)"
 inputs:
   package_name:
-    description: "Package being published (i.e. `dbt-core`, `dbt-redshift`, etc.)"
+    description: "Package to check (I.E. dbt-core, dbt-redshift, etc)"
     required: true
   new_version:
-    description: "SemVer of the package being published (i.e. 1.7.2, 1.8.0a1, etc.)"
+    description: "Semver of the container being built (I.E. 1.0.4)"
     required: true
-  github_token:
-    description: "Auth token for GitHub (must have view packages scope)"
+  gh_token:
+    description: "Auth token for github (must have view packages scope)"
     required: true
-
 outputs:
-  tags:
-    description: "A list of tags to associate with this version"
-
+  latest:
+    description: "Wether or not built container should be tagged latest (bool)"
+  minor_latest:
+    description: "Wether or not built container should be tagged minor.latest (bool)"
 runs:
   using: "docker"
   image: "Dockerfile"

.github/actions/latest-wrangler/examples/example_workflow.yml

@@ -3,24 +3,24 @@ on:
   workflow_dispatch:
     inputs:
       package:
-        description: The package to publish
-        required: true
+       description: The package to publish
+       required: true
       version_number:
-        description: The version number
-        required: true
+       description: The version number
+       required: true
 
 jobs:
   build:
-    runs-on: ${{ vars.UBUNTU_LATEST }}
+    runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v3
-      - name: Wrangle latest tag
-        id: is_latest
-        uses: ./.github/actions/latest-wrangler
-        with:
-          package: ${{ github.event.inputs.package }}
-          new_version: ${{ github.event.inputs.new_version }}
-          gh_token: ${{ secrets.GITHUB_TOKEN }}
-      - name: Print the results
-        run: |
-          echo "Is it latest?  Survey says: ${{ steps.is_latest.outputs.latest }} !"
+    - uses: actions/checkout@v3
+    - name: Wrangle latest tag
+      id: is_latest
+      uses: ./.github/actions/latest-wrangler
+      with:
+        package: ${{ github.event.inputs.package }}
+        new_version: ${{ github.event.inputs.new_version }}
+        gh_token: ${{ secrets.GITHUB_TOKEN }}
+    - name: Print the results
+      run: |
+        echo "Is it latest?  Survey says: ${{ steps.is_latest.outputs.latest }} !"

.github/actions/latest-wrangler/main.py

@@ -1,72 +1,98 @@
 import os
 import sys
-from typing import List
-
 import requests
-from packaging.version import Version, parse
-
-
-def main():
-    package_name: str = os.environ["INPUT_PACKAGE_NAME"]
-    new_version: Version = parse(os.environ["INPUT_NEW_VERSION"])
-    github_token: str = os.environ["INPUT_GITHUB_TOKEN"]
-
-    response = _package_metadata(package_name, github_token)
-    published_versions = _published_versions(response)
-    new_version_tags = _new_version_tags(new_version, published_versions)
-    _register_tags(new_version_tags, package_name)
-
-
-def _package_metadata(package_name: str, github_token: str) -> requests.Response:
-    url = f"https://api.github.com/orgs/dbt-labs/packages/container/{package_name}/versions"
-    return requests.get(url, auth=("", github_token))
-
-
-def _published_versions(response: requests.Response) -> List[Version]:
-    package_metadata = response.json()
-    return [
-        parse(tag)
-        for version in package_metadata
-        for tag in version["metadata"]["container"]["tags"]
-        if "latest" not in tag
-    ]
-
-
-def _new_version_tags(new_version: Version, published_versions: List[Version]) -> List[str]:
-    # the package version is always a tag
-    tags = [str(new_version)]
-
-    # pre-releases don't get tagged with `latest`
-    if new_version.is_prerelease:
-        return tags
-
-    if new_version > max(published_versions):
-        tags.append("latest")
-
-    published_patches = [
-        version
-        for version in published_versions
-        if version.major == new_version.major and version.minor == new_version.minor
-    ]
-    if new_version > max(published_patches):
-        tags.append(f"{new_version.major}.{new_version.minor}.latest")
-
-    return tags
-
-
-def _register_tags(tags: List[str], package_name: str) -> None:
-    fully_qualified_tags = ",".join([f"ghcr.io/dbt-labs/{package_name}:{tag}" for tag in tags])
-    github_output = os.environ.get("GITHUB_OUTPUT")
-    with open(github_output, "at", encoding="utf-8") as gh_output:
-        gh_output.write(f"fully_qualified_tags={fully_qualified_tags}")
-
-
-def _validate_response(response: requests.Response) -> None:
-    message = response["message"]
-    if response.status_code != 200:
-        print(f"Call to GitHub API failed: {response.status_code} - {message}")
-        sys.exit(1)
-
+from distutils.util import strtobool
+from typing import Union
+from packaging.version import parse, Version
 
 if __name__ == "__main__":
-    main()
+
+    # get inputs
+    package = os.environ["INPUT_PACKAGE"]
+    new_version = parse(os.environ["INPUT_NEW_VERSION"])
+    gh_token = os.environ["INPUT_GH_TOKEN"]
+    halt_on_missing = strtobool(os.environ.get("INPUT_HALT_ON_MISSING", "False"))
+
+    # get package metadata from github
+    package_request = requests.get(
+        f"https://api.github.com/orgs/dbt-labs/packages/container/{package}/versions",
+        auth=("", gh_token),
+    )
+    package_meta = package_request.json()
+
+    # Log info if we don't get a 200
+    if package_request.status_code != 200:
+        print(f"Call to GH API failed: {package_request.status_code} {package_meta['message']}")
+
+    # Make an early exit if there is no matching package in github
+    if package_request.status_code == 404:
+        if halt_on_missing:
+            sys.exit(1)
+        # 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)
+
+    # TODO: verify package meta is "correct"
+    # https://github.com/dbt-labs/dbt-core/issues/4640
+
+    # map versions and tags
+    version_tag_map = {
+        version["id"]: version["metadata"]["container"]["tags"] for version in package_meta
+    }
+
+    # is pre-release
+    pre_rel = True if any(x in str(new_version) for x in ["a", "b", "rc"]) else False
+
+    # semver of current latest
+    for version, tags in version_tag_map.items():
+        if "latest" in tags:
+            # N.B. This seems counterintuitive, but we expect any version tagged
+            # 'latest' to have exactly three associated tags:
+            # latest, major.minor.latest, and major.minor.patch.
+            # Subtracting everything that contains the string 'latest' gets us
+            # the major.minor.patch which is what's needed for comparison.
+            current_latest = parse([tag for tag in tags if "latest" not in tag][0])
+        else:
+            current_latest = False
+
+    # semver of current_minor_latest
+    for version, tags in version_tag_map.items():
+        if f"{new_version.major}.{new_version.minor}.latest" in tags:
+            # Similar to above, only now we expect exactly two tags:
+            # major.minor.patch and major.minor.latest
+            current_minor_latest = parse([tag for tag in tags if "latest" not in tag][0])
+        else:
+            current_minor_latest = False
+
+    def is_latest(
+        pre_rel: bool, new_version: Version, remote_latest: Union[bool, Version]
+    ) -> bool:
+        """Determine if a given contaier should be tagged 'latest' based on:
+         - it's pre-release status
+         - it's version
+         - the version of a previously identified container tagged 'latest'
+
+        :param pre_rel: Wether or not the version of the new container is a pre-release
+        :param new_version: The version of the new container
+        :param remote_latest: The version of the previously identified container that's
+            already tagged latest or False
+        """
+        # is a pre-release = not latest
+        if pre_rel:
+            return False
+        # + no latest tag found = is latest
+        if not remote_latest:
+            return True
+        # + if remote version is lower than current = is latest, else not latest
+        return True if remote_latest <= new_version else False
+
+    latest = is_latest(pre_rel, new_version, current_latest)
+    minor_latest = is_latest(pre_rel, new_version, current_minor_latest)
+
+    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}")

.github/actions/setup-postgres-linux/action.yml

@@ -0,0 +1,10 @@
+name: "Set up postgres (linux)"
+description: "Set up postgres service on linux vm for dbt integration tests"
+runs:
+  using: "composite"
+  steps:
+    - shell: bash
+      run: |
+        sudo systemctl start postgresql.service
+        pg_isready
+        sudo -u postgres bash ${{ github.action_path }}/setup_db.sh

.github/actions/setup-postgres-linux/setup_db.sh

@@ -0,0 +1 @@
+../../../test/setup_db.sh

.github/actions/setup-postgres-macos/action.yml

@@ -0,0 +1,24 @@
+name: "Set up postgres (macos)"
+description: "Set up postgres service on macos vm for dbt integration tests"
+runs:
+  using: "composite"
+  steps:
+    - shell: bash
+      run: |
+        brew services start postgresql
+        echo "Check PostgreSQL service is running"
+        i=10
+        COMMAND='pg_isready'
+        while [ $i -gt -1 ]; do
+            if [ $i == 0 ]; then
+                echo "PostgreSQL service not ready, all attempts exhausted"
+                exit 1
+            fi
+            echo "Check PostgreSQL service status"
+            eval $COMMAND && break
+            echo "PostgreSQL service not ready, wait 10 more sec, attempts left: $i"
+            sleep 10
+            ((i--))
+        done
+        createuser -s postgres
+        bash ${{ github.action_path }}/setup_db.sh

.github/actions/setup-postgres-macos/setup_db.sh

@@ -0,0 +1 @@
+../../../test/setup_db.sh

.github/actions/setup-postgres-windows/action.yml

@@ -5,22 +5,8 @@ runs:
   steps:
     - shell: pwsh
       run: |
-        Write-Host -Object "Installing PostgreSQL 16 as windows service..."
-        $installerArgs = @("--install_runtimes 0", "--superpassword root", "--enable_acledit 1", "--unattendedmodeui none", "--mode unattended")
-        $filePath = Invoke-DownloadWithRetry -Url "https://get.enterprisedb.com/postgresql/postgresql-16.1-1-windows-x64.exe" -Path "$env:PGROOT/postgresql-16.1-1-windows-x64.exe"
-        Start-Process -FilePath $filePath -ArgumentList $installerArgs -Wait -PassThru
-
-        Write-Host -Object "Validating PostgreSQL 16 Install..."
-        Get-Service -Name postgresql*
-        $pgReady = Start-Process -FilePath "$env:PGBIN\pg_isready" -Wait -PassThru
-        $exitCode = $pgReady.ExitCode
-        if ($exitCode -ne 0) {
-            Write-Host -Object "PostgreSQL is not ready. Exitcode: $exitCode"
-            exit $exitCode
-        }
-
-        Write-Host -Object "Starting PostgreSQL 16 Service..."
-        $pgService = Get-Service -Name postgresql-x64-16
+        $pgService = Get-Service -Name postgresql*
         Set-Service -InputObject $pgService -Status running -StartupType automatic
+        Start-Process -FilePath "$env:PGBIN\pg_isready" -Wait -PassThru
         $env:Path += ";$env:PGBIN"
         bash ${{ github.action_path }}/setup_db.sh

.github/actions/setup-postgres-windows/setup_db.sh

@@ -1 +1 @@
-../../../scripts/setup_db.sh
+../../../test/setup_db.sh

.github/dbt-postgres-testing.yml

@@ -1,169 +0,0 @@
-# **what?**
-# Runs all tests in dbt-postgres with this branch of dbt-core to ensure nothing is broken
-
-# **why?**
-# Ensure dbt-core changes do not break dbt-postgres, as a basic proxy for other adapters
-
-# **when?**
-# This will run when trying to merge a PR into main.
-# It can also be manually triggered.
-
-# This workflow can be skipped by adding the "Skip Postgres Testing" label to the PR.  This is
-# useful when making a change in both `dbt-postgres` and `dbt-core` where the changes are dependant
-# and cause the other repository to break.
-
-name: "dbt-postgres Tests"
-run-name: >-
-  ${{ (github.event_name == 'workflow_dispatch' || github.event_name == 'workflow_call')
-  && format('dbt-postgres@{0} with dbt-core@{1}', inputs.dbt-postgres-ref, inputs.dbt-core-ref)
-  || 'dbt-postgres@main with dbt-core branch' }}
-
-on:
-  push:
-    branches:
-      - "main"
-      - "*.latest"
-      - "releases/*"
-  pull_request:
-  merge_group:
-    types: [checks_requested]
-  workflow_dispatch:
-    inputs:
-      dbt-postgres-ref:
-        description: "The branch of dbt-postgres to test against"
-        default: "main"
-      dbt-core-ref:
-        description: "The branch of dbt-core to test against"
-        default: "main"
-  workflow_call:
-    inputs:
-      dbt-postgres-ref:
-        description: "The branch of dbt-postgres to test against"
-        type: string
-        required: true
-        default: "main"
-      dbt-core-ref:
-        description: "The branch of dbt-core to test against"
-        type: string
-        required: true
-        default: "main"
-
-permissions: read-all
-
-# will cancel previous workflows triggered by the same event
-# and for the same ref for PRs/merges or same SHA otherwise
-# and for the same inputs on workflow_dispatch or workflow_call
-concurrency:
-  group: ${{ github.workflow }}-${{ github.event_name }}-${{ contains(fromJson('["pull_request", "merge_group"]'), github.event_name) && github.event.pull_request.head.ref || github.sha }}-${{ contains(fromJson('["workflow_call", "workflow_dispatch"]'), github.event_name) && github.event.inputs.dbt-postgres-ref && github.event.inputs.dbt-core-ref || github.sha }}
-  cancel-in-progress: true
-
-defaults:
-  run:
-    shell: bash
-
-jobs:
-  job-prep:
-    # This allow us to run the workflow on pull_requests as well so we can always run unit tests
-    # and only run integration tests on merge for time purposes
-    name: Setup Repo Refs
-    runs-on: ubuntu-latest
-    outputs:
-      dbt-postgres-ref: ${{ steps.core-ref.outputs.ref }}
-      dbt-core-ref: ${{ steps.common-ref.outputs.ref }}
-
-    steps:
-      - name: "Input Refs"
-        id: job-inputs
-        run: |
-          echo "inputs.dbt-postgres-ref=${{ inputs.dbt-postgres-ref }}"
-          echo "inputs.dbt-core-ref=${{ inputs.dbt-core-ref }}"
-
-      - name: "Determine dbt-postgres ref"
-        id: core-ref
-        run: |
-          if [[ -z "${{ inputs.dbt-postgres-ref }}" ]]; then
-            REF="main"
-          else
-            REF=${{ inputs.dbt-postgres-ref }}
-          fi
-          echo "ref=$REF" >> $GITHUB_OUTPUT
-
-      - name: "Determine dbt-core ref"
-        id: common-ref
-        run: |
-          if [[ -z "${{ inputs.dbt-core-ref }}" ]]; then
-            # these will be commits instead of branches
-            if [[ "${{ github.event_name }}" == "merge_group" ]]; then
-              REF=${{ github.event.merge_group.head_sha }}
-            else
-              REF=${{ github.event.pull_request.base.sha }}
-            fi
-          else
-            REF=${{ inputs.dbt-core-ref }}
-          fi
-          echo "ref=$REF" >> $GITHUB_OUTPUT
-
-      - name: "Final Refs"
-        run: |
-          echo "dbt-postgres-ref=${{ steps.core-ref.outputs.ref }}"
-          echo "dbt-core-ref=${{ steps.common-ref.outputs.ref }}"
-
-  integration-tests-postgres:
-    name: "dbt-postgres integration tests"
-    needs: [job-prep]
-    runs-on: ubuntu-latest
-    defaults:
-      run:
-        working-directory: "./dbt-postgres"
-    environment:
-      name: "dbt-postgres"
-    env:
-      POSTGRES_TEST_HOST: ${{ vars.POSTGRES_TEST_HOST }}
-      POSTGRES_TEST_PORT: ${{ vars.POSTGRES_TEST_PORT }}
-      POSTGRES_TEST_USER: ${{ vars.POSTGRES_TEST_USER }}
-      POSTGRES_TEST_PASS: ${{ secrets.POSTGRES_TEST_PASS }}
-      POSTGRES_TEST_DATABASE: ${{ vars.POSTGRES_TEST_DATABASE }}
-      POSTGRES_TEST_THREADS: ${{ vars.POSTGRES_TEST_THREADS }}
-    services:
-      postgres:
-          image: postgres
-          env:
-            POSTGRES_PASSWORD: postgres
-          options: >-
-              --health-cmd pg_isready
-              --health-interval 10s
-              --health-timeout 5s
-              --health-retries 5
-          ports:
-            - ${{ vars.POSTGRES_TEST_PORT }}:5432
-    steps:
-      - name: "Check out dbt-adapters@${{ needs.job-prep.outputs.dbt-postgres-ref }}"
-        uses: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955 # actions/checkout@v4
-        with:
-          repository: dbt-labs/dbt-adapters
-          ref: ${{ needs.job-prep.outputs.dbt-postgres-ref }}
-
-      - name: "Set up Python"
-        uses: actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065 # actions/setup-python@v5
-        with:
-            python-version: ${{ inputs.python-version }}
-
-      - name: "Set environment variables"
-        run: |
-            echo "HATCH_PYTHON=${{ inputs.python-version }}" >> $GITHUB_ENV
-            echo "PIP_ONLY_BINARY=psycopg2-binary" >> $GITHUB_ENV
-
-      - name: "Setup test database"
-        run: psql -f ./scripts/setup_test_database.sql
-        env:
-            PGHOST: ${{ vars.POSTGRES_TEST_HOST }}
-            PGPORT: ${{ vars.POSTGRES_TEST_PORT }}
-            PGUSER: postgres
-            PGPASSWORD: postgres
-            PGDATABASE: postgres
-
-      - name: "Install hatch"
-        uses: pypa/hatch@257e27e51a6a5616ed08a39a408a21c35c9931bc # pypa/hatch@install
-
-      - name: "Run integration tests"
-        run: hatch run ${{ inputs.hatch-env }}:integration-tests

.github/dependabot.yml

@@ -11,6 +11,11 @@ updates:
     schedule:
       interval: "daily"
     rebase-strategy: "disabled"
+  - package-ecosystem: "pip"
+    directory: "/plugins/postgres"
+    schedule:
+      interval: "daily"
+    rebase-strategy: "disabled"
 
   # docker dependencies
   - package-ecosystem: "docker"

.github/pull_request_template.md

@@ -1,7 +1,7 @@
-Resolves #
+resolves #
 
 <!---
-  Include the number of the issue addressed by this PR above, if applicable.
+  Include the number of the issue addressed by this PR above if applicable.
   PRs for code changes without an associated issue *will not be merged*.
   See CONTRIBUTING.md for more information.
 
@@ -26,8 +26,8 @@ Resolves #
 
 ### Checklist
 
-- [ ] I have read [the contributing guide](https://github.com/dbt-labs/dbt-core/blob/main/CONTRIBUTING.md) and understand what's expected of me.
-- [ ] I have run this code in development, and it appears to resolve the stated issue.
-- [ ] This PR includes tests, or tests are not required or relevant for this PR.
-- [ ] This PR has no interface changes (e.g., macros, CLI, logs, JSON artifacts, config files, adapter interface, etc.) or this PR has already received feedback and approval from Product or DX.
-- [ ] This PR includes [type annotations](https://docs.python.org/3/library/typing.html) for new and modified functions.
+- [ ] I have read [the contributing guide](https://github.com/dbt-labs/dbt-core/blob/main/CONTRIBUTING.md) and understand what's expected of me  
+- [ ] I have 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
+- [ ] This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX
+- [ ] This PR includes [type annotations](https://docs.python.org/3/library/typing.html) for new and modified functions

.github/workflows/artifact-reviews.yml

@@ -1,186 +0,0 @@
-# **what?**
-# Enforces 2 reviews when artifact or validation files are modified.
-
-# **why?**
-# Ensure artifact changes receive proper review from designated team members.  GitHub doesn't support
-# multiple reviews on a single PR based on files changed, so we need to enforce this manually.
-
-# **when?**
-# This will run when reviews are submitted and dismissed.
-
-name: "Enforce Additional Reviews on Artifact and Validations Changes"
-
-permissions:
-  checks: write
-  pull-requests: write
-  contents: read
-
-on:
-  # trigger check on review events.  use pull_request_target for forks.
-  pull_request_target:
-    types: [opened, reopened, ready_for_review, synchronize, review_requested]
-  pull_request_review:
-    types: [submitted, edited, dismissed]
-
-# only run this once per PR at a time
-concurrency:
-  group: ${{ github.workflow }}-${{ github.event.pull_request.number }}
-  cancel-in-progress: true
-
-env:
-    required_approvals: 2
-    team: "core-group"
-
-jobs:
-  check-reviews:
-    name: "Validate Additional Reviews"
-    runs-on: ubuntu-latest
-    steps:
-      - name: "Get list of changed files"
-        id: changed_files
-        run: |
-          # Fetch files as JSON and process with jq to sanitize output
-          gh api repos/${{ github.repository }}/pulls/${{ github.event.pull_request.number }}/files \
-            | jq -r '.[].filename' \
-            | while IFS= read -r file; do
-              # Sanitize the filename by removing any special characters and command injection attempts
-              clean_file=$(echo "$file" | sed 's/[^a-zA-Z0-9\.\/\-_]//g')
-              echo "$clean_file"
-            done > changed_files.txt
-          echo "CHANGED_FILES<<EOF" >> $GITHUB_OUTPUT
-          cat changed_files.txt >> $GITHUB_OUTPUT
-          echo "EOF" >> $GITHUB_OUTPUT
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: "Check if any artifact files changed"
-        id: artifact_files_changed
-        run: |
-          artifact_changes=false
-          while IFS= read -r file; do
-            # Only process if file path looks legitimate
-            if [[ "$file" =~ ^[a-zA-Z0-9\.\/\-_]+$ ]]; then
-              if [[ "$file" == "core/dbt/artifacts/"* ]] ; then
-                artifact_changes=true
-                break
-              fi
-            fi
-          done < changed_files.txt
-          echo "artifact_changes=$artifact_changes" >> $GITHUB_OUTPUT
-
-      - name: "Get Core Team Members"
-        if: steps.artifact_files_changed.outputs.artifact_changes == 'true'
-        id: core_members
-        run: |
-          gh api -H "Accept: application/vnd.github+json" \
-          /orgs/dbt-labs/teams/${{ env.team }}/members > core_members.json
-
-          # Extract usernames and set as multiline output
-          echo "membership<<EOF" >> $GITHUB_OUTPUT
-          jq -r '.[].login' core_members.json >> $GITHUB_OUTPUT
-          echo "EOF" >> $GITHUB_OUTPUT
-        env:
-          GH_TOKEN: ${{ secrets.IT_TEAM_MEMBERSHIP }}
-
-      - name: "Verify ${{ env.required_approvals }} core team approvals"
-        if: steps.artifact_files_changed.outputs.artifact_changes == 'true'
-        id: check_approvals
-        run: |
-
-            # Get all reviews
-            REVIEWS=$(gh api repos/${{ github.repository }}/pulls/${{ github.event.pull_request.number }}/reviews)
-            echo "All reviews:"
-            echo "$REVIEWS"
-            # Count approved reviews from core team members (only most recent review per user)
-            CORE_APPROVALS=0
-            while IFS= read -r member; do
-              echo "Checking member: $member"
-              APPROVED=$(echo "$REVIEWS" | jq --arg user "$member" '
-                group_by(.user.login) |
-                map(select(.[0].user.login == $user) |
-                    sort_by(.submitted_at) |
-                    last) |
-                map(select(.state == "APPROVED" and (.state != "DISMISSED"))) |
-                length')
-              echo "Latest review state for $member: $APPROVED"
-              CORE_APPROVALS=$((CORE_APPROVALS + APPROVED))
-              echo "Running total: $CORE_APPROVALS"
-            done <<< "${{ steps.core_members.outputs.membership }}"
-
-            echo "CORE_APPROVALS=$CORE_APPROVALS" >> $GITHUB_OUTPUT
-            echo "CORE_APPROVALS=$CORE_APPROVALS"
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: "Find Comment"
-        if: steps.artifact_files_changed.outputs.artifact_changes == 'true' && steps.check_approvals.outputs.CORE_APPROVALS < env.required_approvals
-        uses: peter-evans/find-comment@a54c31d7fa095754bfef525c0c8e5e5674c4b4b1 # peter-evans/find-comment@v2
-        id: find-comment
-        with:
-          issue-number: ${{ github.event.pull_request.number }}
-          comment-author: 'github-actions[bot]'
-          body-includes: "### Additional Artifact Review Required"
-
-      - name: "Create Comment"
-        if: steps.artifact_files_changed.outputs.artifact_changes == 'true' && steps.find-comment.outputs.comment-id == '' && steps.check_approvals.outputs.CORE_APPROVALS < env.required_approvals
-        uses: peter-evans/create-or-update-comment@23ff15729ef2fc348714a3bb66d2f655ca9066f2 # peter-evans/create-or-update-comment@v3
-        with:
-          issue-number: ${{ github.event.pull_request.number }}
-          body: |
-            ### Additional Artifact Review Required
-
-            Changes to artifact directory files requires at least ${{ env.required_approvals }} approvals from core team members.
-
-      - name: "Notify if not enough approvals"
-        if: steps.artifact_files_changed.outputs.artifact_changes == 'true'
-        run: |
-          if [[ "${{ steps.check_approvals.outputs.CORE_APPROVALS }}" -ge "${{ env.required_approvals }}" ]]; then
-            title="Extra requirements met"
-            message="Changes to artifact directory files requires at least ${{ env.required_approvals }} approvals from core team members. Current number of core team approvals: ${{ steps.check_approvals.outputs.CORE_APPROVALS }} "
-            echo "::notice title=$title::$message"
-            echo "REVIEW_STATUS=success" >> $GITHUB_OUTPUT
-          else
-            title="PR Approval Requirements Not Met"
-            message="Changes to artifact directory files requires at least ${{ env.required_approvals }} approvals from core team members. Current number of core team approvals: ${{ steps.check_approvals.outputs.CORE_APPROVALS }} "
-            echo "::notice title=$title::$message"
-            echo "REVIEW_STATUS=neutral" >> $GITHUB_OUTPUT
-          fi
-        id: review_check
-
-      - name: "Set check status"
-        id: status_check
-        run: |
-          if [[ "${{ steps.artifact_files_changed.outputs.artifact_changes }}" == 'false' ]]; then
-            # no extra review required
-            echo "current_status=success" >> $GITHUB_OUTPUT
-          elif [[ "${{ steps.review_check.outputs.REVIEW_STATUS }}" == "success" ]]; then
-            # we have all the required reviews
-            echo "current_status=success" >> $GITHUB_OUTPUT
-          else
-            # neutral exit - neither success nor failure
-            # we can't fail here because we use multiple triggers for this workflow and they won't reset the check
-            # workaround is to use a neutral exit to skip the check run until it's actually successful
-            echo "current_status=neutral" >> $GITHUB_OUTPUT
-          fi
-
-      - name: "Post Event"
-        # This step posts the status of the check because the workflow is triggered by multiple events
-        # and we need to ensure the check is always updated.  Otherwise we would end up with duplicate
-        # checks in the GitHub UI.
-        run: |
-          if [[ "${{ steps.status_check.outputs.current_status }}" == "success" ]]; then
-            state="success"
-          else
-            state="failure"
-          fi
-
-          gh api \
-            --method POST \
-            -H "Accept: application/vnd.github+json" \
-            /repos/${{ github.repository }}/statuses/${{ github.event.pull_request.base.sha }} \
-            -f state="$state" \
-            -f description="Artifact Review Check" \
-            -f context="Artifact Review Check" \
-            -f target_url="${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}"
-        env:
-          GH_TOKEN: ${{ secrets.FISHTOWN_BOT_PAT }}

.github/workflows/auto-respond-bug-reports.yml

@@ -1,50 +0,0 @@
-# **what?**
-# Check if the an issue is opened near or during an extended holiday period.
-# If so, post an automatically-generated comment about the holiday for bug reports.
-# Also provide specific information to customers of dbt Cloud.
-
-# **why?**
-# Explain why responses will be delayed during our holiday period.
-
-# **when?**
-# This will run when new issues are opened.
-
-name: Auto-Respond to Bug Reports During Holiday Period
-
-on:
-  issues:
-    types:
-      - opened
-
-permissions:
-  contents: read
-  issues: write
-
-jobs:
-  auto-response:
-    runs-on: ${{ vars.UBUNTU_LATEST }}
-    steps:
-      - name: Check if current date is within holiday period
-        id: date-check
-        run: |
-          current_date=$(date -u +"%Y-%m-%d")
-          start_date="2024-12-23"
-          end_date="2025-01-05"
-
-          if [[ "$current_date" < "$start_date" || "$current_date" > "$end_date" ]]; then
-            echo "outside_holiday=true" >> $GITHUB_ENV
-          else
-            echo "outside_holiday=false" >> $GITHUB_ENV
-          fi
-
-      - name: Post comment
-        if: ${{ env.outside_holiday == 'false' && contains(github.event.issue.labels.*.name, 'bug') }}
-        run: |
-          gh issue comment ${{ github.event.issue.number }} --repo ${{ github.repository }} --body "Thank you for your bug report! Our team is will be out of the office for [Christmas and our Global Week of Rest](https://handbook.getdbt.com/docs/time_off#2024-us-holidays), from December 25, 2024, through January 3, 2025.
-
-          We will review your issue as soon as possible after returning.
-          Thank you for your understanding, and happy holidays! 🎄🎉
-
-          If you are a customer of dbt Cloud, please contact our Customer Support team via the dbt Cloud web interface or email **support@dbtlabs.com**."
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/backport.yml

@@ -28,13 +28,13 @@ permissions:
 jobs:
   backport:
     name: Backport
-    runs-on: ${{ vars.UBUNTU_LATEST }}
+    runs-on: ubuntu-latest
     # Only react to merged PRs for security reasons.
     # See https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request_target.
     if: >
       github.event.pull_request.merged
       && contains(github.event.label.name, 'backport')
     steps:
-      - uses: tibdex/backport@9565281eda0731b1d20c4025c43339fb0a23812e # tibdex/backport@v2.0.4
+      - uses: tibdex/backport@v2.0.3
         with:
           github_token: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/bot-changelog.yml

@@ -41,14 +41,16 @@ jobs:
         include:
           - label: "dependencies"
             changie_kind: "Dependencies"
-    runs-on: ${{ vars.UBUNTU_LATEST }}
+          - 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@22b70618b13d0d1c64ea95212bafca2d2bf6b764 # emmyoop/changie_bot@v1.1.0
+      uses: emmyoop/changie_bot@v1.1.0
       with:
         GITHUB_TOKEN: ${{ secrets.FISHTOWN_BOT_PAT }}
         commit_author_name: "Github Build Bot"
@@ -56,4 +58,4 @@ jobs:
         commit_message: "Add automated changelog yaml from template for bot PR"
         changie_kind: ${{ matrix.changie_kind }}
         label: ${{ matrix.label }}
-        custom_changelog_string: "custom:\n  Author: ${{ github.event.pull_request.user.login }}\n  Issue: ${{ github.event.pull_request.number }}"
+        custom_changelog_string: "custom:\n  Author: ${{ github.event.pull_request.user.login }}\n  PR: ${{ github.event.pull_request.number }}"

.github/workflows/changelog-existence.yml

@@ -19,8 +19,6 @@ name: Check Changelog Entry
 on:
   pull_request_target:
     types: [opened, reopened, labeled, unlabeled, synchronize]
-    paths-ignore: ['.changes/**', '.github/**', 'tests/**', '**.md', '**.yml']
-
   workflow_dispatch:
 
 defaults:

.github/workflows/check-artifact-changes.yml

@@ -1,45 +0,0 @@
-name: Check Artifact Changes
-
-on:
-  pull_request:
-    types: [ opened, reopened, labeled, unlabeled, synchronize ]
-    paths-ignore: [ '.changes/**', '.github/**', 'tests/**', '**.md', '**.yml' ]
-  merge_group:
-    types: [checks_requested]
-  workflow_dispatch:
-
-permissions:
-  contents: read
-
-jobs:
-  check-artifact-changes:
-    runs-on: ${{ vars.UBUNTU_LATEST }}
-    if: ${{ !contains(github.event.pull_request.labels.*.name, 'artifact_minor_upgrade') }}
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955 # actions/checkout@v4
-        with:
-          fetch-depth: 0
-
-      - name: Check for changes in core/dbt/artifacts
-        # https://github.com/marketplace/actions/paths-changes-filter
-        uses: dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36 # dorny/paths-filter@v3
-        id: check_artifact_changes
-        with:
-          filters: |
-            artifacts_changed:
-              - 'core/dbt/artifacts/**'
-          list-files: shell
-
-      - name: Fail CI if artifacts have changed
-        if: steps.check_artifact_changes.outputs.artifacts_changed == 'true'
-        run: |
-          echo "CI failure: Artifact changes checked in core/dbt/artifacts directory."
-          echo "Files changed: ${{ steps.check_artifact_changes.outputs.artifacts_changed_files }}"
-          echo "To bypass this check, confirm that the change is not breaking (https://github.com/dbt-labs/dbt-core/blob/main/core/dbt/artifacts/README.md#breaking-changes) and add the 'artifact_minor_upgrade' label to the PR. Modifications and additions to all fields require updates to https://github.com/dbt-labs/dbt-jsonschema."
-          exit 1
-
-      - name: CI check passed
-        if: steps.check_artifact_changes.outputs.artifacts_changed == 'false'
-        run: |
-          echo "No prohibited artifact changes found in core/dbt/artifacts. CI check passed."

.github/workflows/community-label.yml

@@ -1,44 +0,0 @@
-# **what?**
-# Label a PR with a `community` label when a PR is opened by a user outside core/adapters
-
-# **why?**
-# To streamline triage and ensure that community contributions are recognized and prioritized
-
-# **when?**
-# When a PR is opened, not in draft or moved from draft to ready for review
-
-name: Label community PRs
-
-on:
-  # have to use pull_request_target since community PRs come from forks
-  pull_request_target:
-    types: [opened, ready_for_review]
-
-defaults:
-  run:
-    shell: bash
-
-permissions:
-    pull-requests: write # labels PRs
-    contents: read # reads team membership
-
-jobs:
-  open_issues:
-    # If this PR already has the community label, no need to relabel it
-    # If this PR is opened and not draft, determine if it needs to be labeled
-    # if the PR is converted out of draft, determine if it needs to be labeled
-    if: |
-      (
-        !contains(github.event.pull_request.labels.*.name, 'community')
-        && (
-          (github.event.action == 'opened' && github.event.pull_request.draft == false)
-          || github.event.action == 'ready_for_review'
-        )
-        && github.event.pull_request.user.type != 'Bot'
-        && github.event.pull_request.user.login != 'dependabot[bot]'
-      )
-    uses: dbt-labs/actions/.github/workflows/label-community.yml@main
-    with:
-        github_team: 'core-group'
-        label: 'community'
-    secrets: inherit

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

@@ -1,44 +1,25 @@
 # **what?**
-# Cuts the `*.latest` branch, bumps dependencies on it, cleans up all files in `.changes/unreleased`
-# and `.changes/previous verion on main and bumps main to the input version.
+# 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?**
-# Clean up the main branch after a release branch is cut and automate cutting the release branch.
-# Generally reduces the workload of engineers and reducing error.
+# Generally reduces the workload of engineers and reduces error.  Allow automation.
 
 # **when?**
-# This will run when called manually or when triggered in another workflow.
-
-# Example Usage including required permissions:  TODO: update once finalized
-
-# permissions:
-#   contents: read
-#   pull-requests: write
-#
-# name: Cut Release Branch
-# jobs:
-#   changelog:
-#     uses: dbt-labs/actions/.github/workflows/cut-release-branch.yml@main
-#     with:
-#       new_branch_name: 1.7.latest
-#       PR_title: "Cleanup main after cutting new 1.7.latest 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 }}
-
-# TODOs
-# add note to eventually commit changes directly and bypass checks - same as release - when we move to this model run test action after merge
+# This will run when called manually.
 
 name: Cut new release branch
-run-name: "Cutting New Branch:  ${{ inputs.new_branch_name }}"
 
 on:
   workflow_dispatch:
     inputs:
-      new_branch_name:
-        description: "The full name of the new branch (ex. 1.5.latest)"
+      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
-        type: string
 
 defaults:
   run:
@@ -46,346 +27,15 @@ defaults:
 
 permissions:
   contents: write
-  pull-requests: write
-
-env:
-  PYTHON_TARGET_VERSION: "3.10"
-  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."
 
 jobs:
-  prep_work:
-    name: "Prep Work"
-    runs-on: ubuntu-latest
-    steps:
-      - name: "[DEBUG] Print Inputs"
-        run: |
-          echo "new_branch_name:        ${{ inputs.new_branch_name }}"
-          echo "PR_title:               ${{ env.PR_TITLE }}"
-          echo "PR_body:                ${{ env.PR_BODY }}"
-
-  create_temp_branch:
-    name: "Create Temp branch off main"
-    runs-on: ubuntu-latest
-    outputs:
-      temp_branch_name: ${{ steps.variables.outputs.BRANCH_NAME }}
-
-    steps:
-      - name: "Set Branch Value"
-        id: variables
-        run: |
-          echo "BRANCH_NAME=cutting_release_branch/main_cleanup_$GITHUB_RUN_ID" >> $GITHUB_OUTPUT
-
-      - name: "Checkout ${{ github.repository }}"
-        uses: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955 # actions/checkout@v4
-        with:
-          ref: "main"
-          token: ${{ secrets.FISHTOWN_BOT_PAT }}
-
-      - name: "Create PR Branch"
-        run: |
-          user="Github Build Bot"
-          email="buildbot@fishtownanalytics.com"
-          git config user.name "$user"
-          git config user.email "$email"
-          git checkout -b ${{ steps.variables.outputs.BRANCH_NAME }}
-          git push --set-upstream origin ${{ steps.variables.outputs.BRANCH_NAME }}
-
-      - name: "[Notification] Temp branch created"
-        run: |
-          message="Temp branch ${{ steps.variables.outputs.BRANCH_NAME }} created"
-          echo "::notice title="Temporary branch created": $title::$message"
-
-  cleanup_changelog:
-    name: "Clean Up Changelog"
-    needs: ["create_temp_branch"]
-    runs-on: ubuntu-latest
-    outputs:
-      next-version: ${{ steps.semver-current.outputs.next-minor-alpha-version }}
-
-    steps:
-      - name: "Checkout ${{ github.repository }}"
-        uses: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955 # actions/checkout@v4
-        with:
-          ref: ${{ needs.create_temp_branch.outputs.temp_branch_name }}
-          token: ${{ secrets.FISHTOWN_BOT_PAT }}
-
-      - name: "Add Homebrew To PATH"
-        run: |
-          echo "/home/linuxbrew/.linuxbrew/bin:/home/linuxbrew/.linuxbrew/sbin" >> $GITHUB_PATH
-
-      - name: "Install Homebrew Packages"
-        run: |
-          brew install pre-commit
-          brew tap miniscruff/changie https://github.com/miniscruff/changie
-          brew install changie
-
-      - name: "Check Current Version In Code"
-        id: determine_version
-        run: |
-          current_version=$(grep '^version = ' core/pyproject.toml | sed 's/version = "\(.*\)"/\1/')
-          echo "current_version=$current_version" >> $GITHUB_OUTPUT
-
-      - name: "[Notification] Check Current Version In Code"
-        run: |
-          message="The current version is ${{ steps.determine_version.outputs.current_version }}"
-          echo "::notice title="Version Bump Check": $title::$message"
-
-      - name: "Parse Current Version Into Parts for Changelog Directories"
-        id: semver-current
-        uses: dbt-labs/actions/parse-semver@main
-        with:
-          version: ${{ steps.determine_version.outputs.current_version }}
-
-      - name: "[Notification] Next Alpha Version"
-        run: |
-          message="The next alpha version is ${{ steps.semver-current.outputs.next-minor-alpha-version }}"
-          echo "::notice title="Version Bump Check": $title::$message"
-
-      - name: "Delete Unreleased Changelog YAMLs"
-        # removal fails if no files exist. OK to continue since we're just cleaning up the files.
-        continue-on-error: true
-        run: |
-          rm .changes/unreleased/*.yaml || true
-
-      - name: "Delete Pre Release Changelogs and YAMLs"
-        # removal fails if no files exist. OK to continue since we're just cleaning up the files.
-        continue-on-error: true
-        run: |
-          rm .changes/${{ steps.semver-current.outputs.base-version }}/*.yaml || true
-          rm .changes/${{ steps.semver-current.outputs.major }}.${{ steps.semver-current.outputs.minor }}.*.md || true
-
-      - name: "Cleanup CHANGELOG.md"
-        run: |
-          changie merge
-
-      - name: "Commit Changelog Cleanup to Branch"
-        run: |
-          user="Github Build Bot"
-          email="buildbot@fishtownanalytics.com"
-          git config user.name "$user"
-          git config user.email "$email"
-          git status
-          git add .
-          git commit -m "Clean up changelog on main"
-          git push
-
-      - name: "[Notification] Changelog cleaned up"
-        run: |
-          message="Changelog on ${{ needs.create_temp_branch.outputs.temp_branch_name }} cleaned up"
-          echo "::notice title="Changelog cleaned up": $title::$message"
-
-  bump_version:
-    name: "Bump to next minor version"
-    needs: ["cleanup_changelog", "create_temp_branch"]
-    runs-on: ubuntu-latest
-
-    steps:
-      - name: "Checkout ${{ github.repository }}"
-        uses: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955 # actions/checkout@v4
-        with:
-          ref: ${{ needs.create_temp_branch.outputs.temp_branch_name }}
-          token: ${{ secrets.FISHTOWN_BOT_PAT }}
-
-      - name: "Set up Python - ${{ env.PYTHON_TARGET_VERSION }}"
-        uses: actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065 # actions/setup-python@v5
-        with:
-          python-version: "${{ env.PYTHON_TARGET_VERSION }}"
-
-      - name: "Install Spark Dependencies"
-        if: ${{ contains(github.repository, 'dbt-labs/dbt-spark') }}
-        run: |
-          sudo apt-get update
-          sudo apt-get install libsasl2-dev
-
-      - name: "Install Python Dependencies"
-        run: |
-          python -m pip install --upgrade pip
-          python -m pip install hatch
-
-      - name: "Bump Version To ${{ needs.cleanup_changelog.outputs.next-version }}"
-        run: |
-          cd core
-          hatch version ${{ needs.cleanup_changelog.outputs.next-version }}
-          hatch run dev-req
-          dbt --version
-
-      - name: "Commit Version Bump to Branch"
-        run: |
-          user="Github Build Bot"
-          email="buildbot@fishtownanalytics.com"
-          git config user.name "$user"
-          git config user.email "$email"
-          git status
-          git add .
-          git commit -m "Bumping version to ${{ needs.cleanup_changelog.outputs.next-version }}"
-          git push
-
-      - name: "[Notification] Version Bump completed"
-        run: |
-          message="Version on ${{ needs.create_temp_branch.outputs.temp_branch_name }} bumped to ${{ needs.cleanup_changelog.outputs.next-version }}"
-          echo "::notice title="Version Bump Completed": $title::$message"
-
-  cleanup:
-    name: "Cleanup Code Quality"
-    needs: ["create_temp_branch", "bump_version"]
-    runs-on: ubuntu-latest
-    steps:
-      - name: "Checkout ${{ github.repository }}"
-        uses: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955 # actions/checkout@v4
-        with:
-          ref: ${{ needs.create_temp_branch.outputs.temp_branch_name }}
-          token: ${{ secrets.FISHTOWN_BOT_PAT }}
-
-      - name: "Add Homebrew To PATH"
-        run: |
-          echo "/home/linuxbrew/.linuxbrew/bin:/home/linuxbrew/.linuxbrew/sbin" >> $GITHUB_PATH
-
-      - name: "brew install pre-commit"
-        run: |
-          brew install pre-commit
-
-      # this step will fail on whitespace errors but also correct them
-      - name: "Cleanup - Remove Trailing Whitespace Via Pre-commit"
-        continue-on-error: true
-        run: |
-          pre-commit run trailing-whitespace --files CHANGELOG.md .changes/* || true
-
-      # this step will fail on newline errors but also correct them
-      - name: "Cleanup - Remove Extra Newlines Via Pre-commit"
-        continue-on-error: true
-        run: |
-          pre-commit run end-of-file-fixer --files CHANGELOG.md .changes/* || true
-
-      - name: "Commit Version Bump to Branch"
-        run: |
-          user="Github Build Bot"
-          email="buildbot@fishtownanalytics.com"
-          git config user.name "$user"
-          git config user.email "$email"
-          git status
-          git add .
-          git commit -m "Code quality cleanup"
-          git push
-
-  open_pr:
-    name: "Open PR Against main"
-    needs: ["cleanup_changelog", "create_temp_branch", "cleanup"]
-    runs-on: ubuntu-latest
-    outputs:
-      pr_number: ${{ steps.create_pr.outputs.pull-request-number }}
-
-    steps:
-      - name: "Checkout ${{ github.repository }}"
-        uses: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955 # actions/checkout@v4
-        with:
-          ref: ${{ needs.create_temp_branch.outputs.temp_branch_name }}
-          token: ${{ secrets.FISHTOWN_BOT_PAT }}
-
-      - name: "Determine PR Title"
-        id: pr_title
-        run: |
-          echo "pr_title=${{ env.PR_TITLE }}" >> $GITHUB_OUTPUT
-          if [${{ env.PR_TITLE }} == ""]; then
-            echo "pr_title='Clean up changelogs and bump to version ${{ needs.cleanup_changelog.outputs.next-version }}'" >> $GITHUB_OUTPUT
-          fi
-
-      - name: "Determine PR Body"
-        id: pr_body
-        run: |
-          echo "pr_body=${{ env.PR_BODY }}" >> $GITHUB_OUTPUT
-          if [${{ env.PR_BODY }} == ""]; then
-            echo "pr_body='Clean up changelogs and bump to version ${{ needs.cleanup_changelog.outputs.next-version }}'" >> $GITHUB_OUTPUT
-          fi
-
-      - name: "Add Branch Details"
-        id: pr_body_branch
-        run: |
-          branch_details="The workflow that generated this PR also created a new branch: ${{ inputs.new_branch_name }}"
-          full_body="${{ steps.pr_body.outputs.pr_body }} $branch_details"
-          echo "pr_full_body=$full_body" >> $GITHUB_OUTPUT
-
-      - name: "Open Pull Request"
-        id: create_pr
-        run: |
-          pr_url=$(gh pr create -B main -H ${{ needs.create_temp_branch.outputs.temp_branch_name }} -l "Skip Changelog" -t "${{ steps.pr_title.outputs.pr_title }}" -b "${{ steps.pr_body_branch.outputs.pr_full_body }}")
-          echo "pr_url=$pr_url" >> $GITHUB_OUTPUT
-        env:
-          GH_TOKEN: ${{ secrets.FISHTOWN_BOT_PAT }}
-
-      - name: "[Notification] Pull Request Opened"
-        run: |
-          message="PR opened at ${{ steps.create_pr.outputs.pr_url }}"
-          echo "::notice title="Pull Request Opened": $title::$message"
-
-  cut_new_branch:
-    # don't cut the new branch until we're done opening the PR against main
-    name: "Cut New Branch ${{ inputs.new_branch_name }}"
-    needs: [open_pr]
-    runs-on: ubuntu-latest
-
-    steps:
-      - name: "Checkout ${{ github.repository }}"
-        uses: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955 # actions/checkout@v4
-        with:
-          token: ${{ secrets.FISHTOWN_BOT_PAT }}
-          fetch-depth: 0
-
-      - name: "Ensure New Branch Does Not Exist"
-        id: check_new_branch
-        run: |
-          title="Check New Branch Existence"
-          if git show-ref --quiet ${{ inputs.new_branch_name }}; then
-            message="Branch ${{ inputs.new_branch_name }} already exists.  Exiting."
-            echo "::error $title::$message"
-            exit 1
-          fi
-
-      - name: "Create New Release Branch"
-        run: |
-          git checkout -b ${{ inputs.new_branch_name }}
-
-      - name: "Push up New Branch"
-        run: |
-          #Data for commit
-          user="Github Build Bot"
-          email="buildbot@fishtownanalytics.com"
-          git config user.name "$user"
-          git config user.email "$email"
-          git push --set-upstream origin ${{ inputs.new_branch_name }}
-
-      - name: "[Notification] New branch created"
-        run: |
-          message="New branch ${{ inputs.new_branch_name }} created"
-          echo "::notice title="New branch created": $title::$message"
-
-      - name: "Bump dependencies via script"
-        # This bumps the dependency on dbt-core in the adapters
-        if: ${{ !contains(github.repository, 'dbt-core') }}
-        run: |
-          echo ${{ github.repository }}
-          echo "running update_dependencies script"
-          bash ${GITHUB_WORKSPACE}/.github/scripts/update_dependencies.sh ${{ inputs.new_branch_name }}
-          commit_message="bumping .latest branch variable in update_dependencies.sh to ${{ inputs.new_branch_name }}"
-          git status
-          git add .
-          git commit -m "$commit_message"
-          git push
-
-      - name: "Bump env variable via script"
-        # bumps the RELEASE_BRANCH variable in nightly-release.yml in adapters
-        if: ${{ !contains(github.repository, 'dbt-core') }}
-        run: |
-          file="./.github/scripts/update_release_branch.sh"
-          if test -f "$file"; then
-            echo ${{ github.repository }}
-            echo "running some script yet to be written now"
-            bash $file ${{ inputs.new_branch_name }}
-            commit_message="updating env variable to ${{ inputs.new_branch_name }} in nightly-release.yml"
-            git status
-            git add .
-            git commit -m "$commit_message"
-            git push
-          else
-            echo "no $file seen skipping step"
-          fi
+  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/docs-issue.yml

@@ -1,18 +1,19 @@
 # **what?**
-# Open an issue in docs.getdbt.com when an issue is labeled `user docs` and closed as completed
+# Open an issue in docs.getdbt.com when a PR is labeled `user docs`
 
 # **why?**
 # To reduce barriers for keeping docs up to date
 
 # **when?**
-# When an issue is labeled `user docs` and is closed as completed.  Can be labeled before or after the issue is closed.
+# When a PR is labeled `user docs` and is merged.  Runs on pull_request_target to run off the workflow already merged,
+# not the workflow that existed on the PR branch.  This allows old PRs to get comments.
 
 
-name: Open issues in docs.getdbt.com repo when an issue is labeled
-run-name: "Open an issue in docs.getdbt.com for issue #${{ github.event.issue.number }}"
+name: Open issues in docs.getdbt.com repo when a PR is labeled
+run-name: "Open an issue in docs.getdbt.com for PR #${{ github.event.pull_request.number }}"
 
 on:
-  issues:
+  pull_request_target:
     types: [labeled, closed]
 
 defaults:
@@ -20,22 +21,23 @@ defaults:
     shell: bash
 
 permissions:
-    issues: write # comments on issues
+    issues: write # opens new issues
+    pull-requests: write # comments on PRs
+
 
 jobs:
   open_issues:
-    # we only want to run this when the issue is closed as completed and the label `user docs` has been assigned.
-    # If this logic does not exist in this workflow, it runs the
+    # we only want to run this when the PR has been merged or the label in the labeled event is `user docs`.  Otherwise it runs the
     # risk of duplicaton of issues being created due to merge and label both triggering this workflow to run and neither having
     # generating the comment before the other runs.  This lives here instead of the shared workflow because this is where we
     # decide if it should run or not.
     if: |
-      (github.event.issue.state == 'closed' &&
-       github.event.issue.state_reason == 'completed' &&
-       contains( github.event.issue.labels.*.name, 'user docs'))
+      (github.event.pull_request.merged == true) &&
+      ((github.event.action == 'closed' && contains( github.event.pull_request.labels.*.name, 'user docs')) ||
+      (github.event.action == 'labeled' && github.event.label.name == 'user docs'))
     uses: dbt-labs/actions/.github/workflows/open-issue-in-repo.yml@main
     with:
         issue_repository: "dbt-labs/docs.getdbt.com"
-        issue_title: "[Core] Docs Changes Needed from ${{ github.event.repository.name }} Issue #${{ github.event.issue.number }}"
-        issue_body: "At a minimum, update body to include a link to the page on docs.getdbt.com requiring updates and what part(s) of the page you would like to see updated.\n Originating from this issue: https://github.com/dbt-labs/dbt-core/issues/${{ github.event.issue.number }}"
+        issue_title: "Docs Changes Needed from ${{ github.event.repository.name }} PR #${{ github.event.pull_request.number }}"
+        issue_body: "At a minimum, update body to include a link to the page on docs.getdbt.com requiring updates and what part(s) of the page you would like to see updated."
     secrets: inherit

.github/workflows/jira-creation.yml

@@ -0,0 +1,26 @@
+# **what?**
+# Mirrors issues into Jira. Includes the information: title,
+# GitHub Issue ID and URL
+
+# **why?**
+# Jira is our tool for tracking and we need to see these issues in there
+
+# **when?**
+# On issue creation or when an issue is labeled `Jira`
+
+name: Jira Issue Creation
+
+on:
+  issues:
+    types: [opened, labeled]
+
+permissions:
+  issues: write
+
+jobs:
+  call-creation-action:
+    uses: dbt-labs/actions/.github/workflows/jira-creation-actions.yml@main
+    secrets:
+      JIRA_BASE_URL: ${{ secrets.JIRA_BASE_URL }}
+      JIRA_USER_EMAIL: ${{ secrets.JIRA_USER_EMAIL }}
+      JIRA_API_TOKEN: ${{ secrets.JIRA_API_TOKEN }}

.github/workflows/jira-label.yml

@@ -0,0 +1,26 @@
+# **what?**
+# Calls mirroring Jira label Action. Includes adding a new label
+# to an existing issue or removing a label as well
+
+# **why?**
+# Jira is our tool for tracking and we need to see these labels in there
+
+# **when?**
+# On labels being added or removed from issues
+
+name: Jira Label Mirroring
+
+on:
+  issues:
+    types: [labeled, unlabeled]
+
+permissions:
+  issues: read
+
+jobs:
+  call-label-action:
+    uses: dbt-labs/actions/.github/workflows/jira-label-actions.yml@main
+    secrets:
+      JIRA_BASE_URL: ${{ secrets.JIRA_BASE_URL }}
+      JIRA_USER_EMAIL: ${{ secrets.JIRA_USER_EMAIL }}
+      JIRA_API_TOKEN: ${{ secrets.JIRA_API_TOKEN }}

.github/workflows/jira-transition.yml

@@ -0,0 +1,27 @@
+# **what?**
+# Transition a Jira issue to a new state
+# Only supports these GitHub Issue transitions:
+#   closed, deleted, reopened
+
+# **why?**
+# Jira needs to be kept up-to-date
+
+# **when?**
+# On issue closing, deletion, reopened
+
+name: Jira Issue Transition
+
+on:
+  issues:
+    types: [closed, deleted, reopened]
+
+# no special access is needed
+permissions: read-all
+
+jobs:
+  call-transition-action:
+    uses: dbt-labs/actions/.github/workflows/jira-transition-actions.yml@main
+    secrets:
+      JIRA_BASE_URL: ${{ secrets.JIRA_BASE_URL }}
+      JIRA_USER_EMAIL: ${{ secrets.JIRA_USER_EMAIL }}
+      JIRA_API_TOKEN: ${{ secrets.JIRA_API_TOKEN }}

.github/workflows/main.yml

@@ -20,8 +20,6 @@ on:
       - "*.latest"
       - "releases/*"
   pull_request:
-  merge_group:
-    types: [checks_requested]
   workflow_dispatch:
 
 permissions: read-all
@@ -49,33 +47,26 @@ jobs:
 
     steps:
       - name: Check out the repository
-        uses: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955 # actions/checkout@v4
+        uses: actions/checkout@v3
 
       - name: Set up Python
-        uses: actions/setup-python@e797f83bcb11b83ae66e0230d6156d7c80228e7c # actions/setup-python@v6
+        uses: actions/setup-python@v4
         with:
-          python-version: "3.10"
+          python-version: '3.8'
 
       - name: Install python dependencies
         run: |
           python -m pip install --user --upgrade pip
           python -m pip --version
-          python -m pip install hatch
-          cd core
-          hatch run setup
-
-      - name: Verify dbt installation
-        run: |
-          cd core
-          hatch run dbt --version
+          make dev
+          mypy --version
+          dbt --version
 
       - name: Run pre-commit hooks
-        run: |
-          cd core
-          hatch run code-quality
+        run: pre-commit run --all-files --show-diff-on-failure
 
   unit:
-    name: "unit test / python ${{ matrix.python-version }}"
+    name: unit test / python ${{ matrix.python-version }}
 
     runs-on: ubuntu-latest
     timeout-minutes: 10
@@ -83,14 +74,17 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        python-version: ["3.10", "3.11", "3.12", "3.13"]
+        python-version: ["3.8", "3.9", "3.10", "3.11"]
+
+    env:
+      TOXENV: "unit"
 
     steps:
       - name: Check out the repository
-        uses: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955 # actions/checkout@v4
+        uses: actions/checkout@v3
 
       - name: Set up Python ${{ matrix.python-version }}
-        uses: actions/setup-python@e797f83bcb11b83ae66e0230d6156d7c80228e7c # actions/setup-python@v6
+        uses: actions/setup-python@v4
         with:
           python-version: ${{ matrix.python-version }}
 
@@ -98,15 +92,11 @@ jobs:
         run: |
           python -m pip install --user --upgrade pip
           python -m pip --version
-          python -m pip install hatch
-          hatch --version
+          python -m pip install tox
+          tox --version
 
-      - name: Run unit tests
-        uses: nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08 # nick-fields/retry@v3
-        with:
-          timeout_minutes: 10
-          max_attempts: 3
-          command: cd core && hatch run ci:unit-tests
+      - name: Run tox
+        run: tox
 
       - name: Get current date
         if: always()
@@ -117,11 +107,10 @@ jobs:
 
       - name: Upload Unit Test Coverage to Codecov
         if: ${{ matrix.python-version == '3.11' }}
-        uses: codecov/codecov-action@5a1091511ad55cbe89839c7260b706298ca349f7 # codecov/codecov-action@v5
+        uses: codecov/codecov-action@v3
         with:
           token: ${{ secrets.CODECOV_TOKEN }}
           flags: unit
-          fail_ci_if_error: false
 
   integration-metadata:
     name: integration test metadata generation
@@ -146,7 +135,7 @@ jobs:
       - name: generate include
         id: generate-include
         run: |
-          INCLUDE=('"python-version":"3.10","os":"windows-latest"' '"python-version":"3.10","os":"macos-14"' )
+          INCLUDE=('"python-version":"3.8","os":"windows-latest"' '"python-version":"3.8","os":"macos-latest"' )
           INCLUDE_GROUPS="["
           for include in ${INCLUDE[@]}; do
               for group in $(seq 1 ${{ env.PYTHON_INTEGRATION_TEST_WORKERS }}); do
@@ -158,102 +147,7 @@ jobs:
           echo "include=${INCLUDE_GROUPS}"
           echo "include=${INCLUDE_GROUPS}" >> $GITHUB_OUTPUT
 
-  integration-postgres:
-    name: "(${{ matrix.split-group }}) integration test / python ${{ matrix.python-version }} / ${{ matrix.os }}"
-
-    runs-on: ${{ matrix.os }}
-    timeout-minutes: 30
-    needs:
-      - integration-metadata
-    strategy:
-      fail-fast: false
-      matrix:
-        python-version: ["3.10", "3.11", "3.12", "3.13"]
-        os: ["ubuntu-latest"]
-        split-group: ${{ fromJson(needs.integration-metadata.outputs.split-groups) }}
-    env:
-      DBT_INVOCATION_ENV: github-actions
-      DBT_TEST_USER_1: dbt_test_user_1
-      DBT_TEST_USER_2: dbt_test_user_2
-      DBT_TEST_USER_3: dbt_test_user_3
-      DD_CIVISIBILITY_AGENTLESS_ENABLED: true
-      DD_API_KEY: ${{ secrets.DATADOG_API_KEY }}
-      DD_SITE: datadoghq.com
-      DD_ENV: ci
-      DD_SERVICE: ${{ github.event.repository.name }}
-
-    services:
-      # Label used to access the service container
-      postgres:
-        # Docker Hub image
-        image: postgres
-        # Provide the password for postgres
-        env:
-          POSTGRES_PASSWORD: password
-          POSTGRES_USER: postgres
-        # Set health checks to wait until postgres has started
-        options: >-
-          --health-cmd pg_isready
-          --health-interval 10s
-          --health-timeout 5s
-          --health-retries 5
-        ports:
-          - 5432:5432
-
-    steps:
-      - name: Check out the repository
-        uses: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955 # actions/checkout@v4
-
-      - name: Set up Python ${{ matrix.python-version }}
-        uses: actions/setup-python@e797f83bcb11b83ae66e0230d6156d7c80228e7c # actions/setup-python@v6
-        with:
-          python-version: ${{ matrix.python-version }}
-
-      - name: Run postgres setup script
-        run: |
-          ./scripts/setup_db.sh
-        env:
-          PGHOST: localhost
-          PGPORT: 5432
-          PGPASSWORD: password
-
-      - name: Install python tools
-        run: |
-          python -m pip install --user --upgrade pip
-          python -m pip --version
-          python -m pip install hatch
-          hatch --version
-
-      - name: Run integration tests
-        uses: nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08 # nick-fields/retry@v3
-        with:
-          timeout_minutes: 30
-          max_attempts: 3
-          shell: bash
-          command: cd core && hatch run ci:integration-tests -- --ddtrace --splits ${{ env.PYTHON_INTEGRATION_TEST_WORKERS }} --group ${{ matrix.split-group }}
-
-      - 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
-
-      - uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # actions/upload-artifact@v4
-        if: always()
-        with:
-          name: logs_${{ matrix.python-version }}_${{ matrix.os }}_${{ matrix.split-group }}_${{ steps.date.outputs.date }}
-          path: ./logs
-
-      - name: Upload Integration Test Coverage to Codecov
-        if: ${{ matrix.python-version == '3.11' }}
-        uses: codecov/codecov-action@5a1091511ad55cbe89839c7260b706298ca349f7 # codecov/codecov-action@v5
-        with:
-          token: ${{ secrets.CODECOV_TOKEN }}
-          flags: integration
-          fail_ci_if_error: false
-
-  integration-mac-windows:
+  integration:
     name: (${{ matrix.split-group }}) integration test / python ${{ matrix.python-version }} / ${{ matrix.os }}
 
     runs-on: ${{ matrix.os }}
@@ -263,9 +157,12 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        # already includes split group and runs mac + windows
+        python-version: ["3.8", "3.9", "3.10", "3.11"]
+        os: [ubuntu-20.04]
+        split-group: ${{ fromJson(needs.integration-metadata.outputs.split-groups) }}
         include: ${{ fromJson(needs.integration-metadata.outputs.include) }}
     env:
+      TOXENV: integration
       DBT_INVOCATION_ENV: github-actions
       DBT_TEST_USER_1: dbt_test_user_1
       DBT_TEST_USER_2: dbt_test_user_2
@@ -278,21 +175,20 @@ jobs:
 
     steps:
       - name: Check out the repository
-        uses: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955 # actions/checkout@v4
+        uses: actions/checkout@v3
 
       - name: Set up Python ${{ matrix.python-version }}
-        uses: actions/setup-python@e797f83bcb11b83ae66e0230d6156d7c80228e7c # actions/setup-python@v6
+        uses: actions/setup-python@v4
         with:
           python-version: ${{ matrix.python-version }}
 
+      - name: Set up postgres (linux)
+        if: runner.os == 'Linux'
+        uses: ./.github/actions/setup-postgres-linux
+
       - name: Set up postgres (macos)
         if: runner.os == 'macOS'
-
-        uses: nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08 # nick-fields/retry@v3
-        with:
-          timeout_minutes: 10
-          max_attempts: 3
-          command: ./scripts/setup_db.sh
+        uses: ./.github/actions/setup-postgres-macos
 
       - name: Set up postgres (windows)
         if: runner.os == 'Windows'
@@ -302,16 +198,13 @@ jobs:
         run: |
           python -m pip install --user --upgrade pip
           python -m pip --version
-          python -m pip install hatch
-          hatch --version
+          python -m pip install tox
+          tox --version
 
-      - name: Run integration tests
-        uses: nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08 # nick-fields/retry@v3
-        with:
-          timeout_minutes: 30
-          max_attempts: 3
-          shell: bash
-          command: cd core && hatch run ci:integration-tests -- --ddtrace --splits ${{ env.PYTHON_INTEGRATION_TEST_WORKERS }} --group ${{ matrix.split-group }}
+      - name: Run tests
+        run: tox -- --ddtrace
+        env:
+          PYTEST_ADDOPTS: ${{ format('--splits {0} --group {1}', env.PYTHON_INTEGRATION_TEST_WORKERS, matrix.split-group) }}
 
       - name: Get current date
         if: always()
@@ -320,28 +213,27 @@ jobs:
           CURRENT_DATE=$(date +'%Y-%m-%dT%H_%M_%S') # no colons allowed for artifacts
           echo "date=$CURRENT_DATE" >> $GITHUB_OUTPUT
 
-      - uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # actions/upload-artifact@v4
+      - uses: actions/upload-artifact@v3
         if: always()
         with:
-          name: logs_${{ matrix.python-version }}_${{ matrix.os }}_${{ matrix.split-group }}_${{ steps.date.outputs.date }}
+          name: logs_${{ matrix.python-version }}_${{ matrix.os }}_${{ steps.date.outputs.date }}
           path: ./logs
 
       - name: Upload Integration Test Coverage to Codecov
         if: ${{ matrix.python-version == '3.11' }}
-        uses: codecov/codecov-action@5a1091511ad55cbe89839c7260b706298ca349f7 # codecov/codecov-action@v5
+        uses: codecov/codecov-action@v3
         with:
           token: ${{ secrets.CODECOV_TOKEN }}
           flags: integration
-          fail_ci_if_error: false
 
   integration-report:
     if: ${{ always() }}
     name: Integration Test Suite
     runs-on: ubuntu-latest
-    needs: [integration-mac-windows, integration-postgres]
+    needs: integration
     steps:
       - name: "Integration Tests Failed"
-        if: ${{ contains(needs.integration-mac-windows.result, 'failure') || contains(needs.integration-mac-windows.result, 'cancelled') || contains(needs.integration-postgres.result, 'failure') || contains(needs.integration-postgres.result, 'cancelled') }}
+        if: ${{ contains(needs.integration.result, 'failure') || contains(needs.integration.result, 'cancelled') }}
         # when this is true the next step won't execute
         run: |
           echo "::notice title='Integration test suite failed'"
@@ -358,17 +250,17 @@ jobs:
 
     steps:
       - name: Check out the repository
-        uses: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955 # actions/checkout@v4
+        uses: actions/checkout@v3
 
       - name: Set up Python
-        uses: actions/setup-python@e797f83bcb11b83ae66e0230d6156d7c80228e7c # actions/setup-python@v6
+        uses: actions/setup-python@v4
         with:
-          python-version: "3.10"
+          python-version: '3.8'
 
       - name: Install python dependencies
         run: |
           python -m pip install --user --upgrade pip
-          python -m pip install --upgrade hatch twine check-wheel-contents
+          python -m pip install --upgrade setuptools wheel twine check-wheel-contents
           python -m pip --version
 
       - name: Build distributions
@@ -377,7 +269,27 @@ jobs:
       - name: Show distributions
         run: ls -lh dist/
 
-      - name: Check and verify distributions
+      - name: Check distribution descriptions
         run: |
-          cd core
-          hatch run build:check-all
+          twine check dist/*
+
+      - name: Check wheel contents
+        run: |
+          check-wheel-contents dist/*.whl --ignore W007,W008
+
+      - name: Install wheel distributions
+        run: |
+          find ./dist/*.whl -maxdepth 1 -type f | xargs python -m pip install --force-reinstall --find-links=dist/
+
+      - name: Check wheel distributions
+        run: |
+          dbt --version
+
+      - name: Install source distributions
+        # ignore dbt-1.0.0, which intentionally raises an error when installed from source
+        run: |
+          find ./dist/dbt-[a-z]*.gz -maxdepth 1 -type f | xargs python -m pip install --force-reinstall --find-links=dist/
+
+      - name: Check source distributions
+        run: |
+          dbt --version

.github/workflows/model_performance.yml

@@ -0,0 +1,265 @@
+# **what?**
+# This workflow models the performance characteristics of a point in time in dbt.
+# It runs specific dbt commands on committed projects multiple times to create and
+# commit information about the distribution to the current branch. For more information
+# see the readme in the performance module at /performance/README.md.
+#
+# **why?**
+# When developing new features, we can take quick performance samples and compare
+# them against the commited baseline measurements produced by this workflow to detect
+# some performance regressions at development time before they reach users.
+#
+# **when?**
+# This is only run once directly after each release (for non-prereleases). If for some
+# reason the results of a run are not satisfactory, it can also be triggered manually.
+
+name: Model Performance Characteristics
+
+on:
+  # runs after non-prereleases are published.
+  release:
+    types: [released]
+  # run manually from the actions tab
+  workflow_dispatch:
+    inputs:
+      release_id:
+        description: 'dbt version to model (must be non-prerelease in Pypi)'
+        type: string
+        required: true
+
+env:
+  RUNNER_CACHE_PATH: performance/runner/target/release/runner
+
+# both jobs need to write
+permissions:
+  contents: write
+  pull-requests: write
+
+jobs:
+  set-variables:
+    name: Setting Variables
+    runs-on: ubuntu-latest
+    outputs:
+      cache_key: ${{ steps.variables.outputs.cache_key }}
+      release_id: ${{ steps.semver.outputs.base-version }}
+      release_branch: ${{ steps.variables.outputs.release_branch }}
+    steps:
+
+      # explicitly checkout the performance runner from main regardless of which
+      # version we are modeling.
+      - name: Checkout
+        uses: actions/checkout@v3
+        with:
+          ref: main
+
+      - name: Parse version into parts
+        id: semver
+        uses: dbt-labs/actions/parse-semver@v1
+        with:
+          version: ${{ github.event.inputs.release_id || github.event.release.tag_name }}
+
+      # collect all the variables that need to be used in subsequent jobs
+      - name: Set variables
+        id: variables
+        run: |
+          # create a cache key that will be used in the next job. without this the
+          # next job would have to checkout from main and hash the files itself.
+          echo "cache_key=${{ runner.os }}-${{ hashFiles('performance/runner/Cargo.toml')}}-${{ hashFiles('performance/runner/src/*') }}" >> $GITHUB_OUTPUT
+
+          branch_name="${{steps.semver.outputs.major}}.${{steps.semver.outputs.minor}}.latest"
+          echo "release_branch=$branch_name" >> $GITHUB_OUTPUT
+          echo "release branch is inferred to be ${branch_name}"
+
+  latest-runner:
+    name: Build or Fetch Runner
+    runs-on: ubuntu-latest
+    needs: [set-variables]
+    env:
+      RUSTFLAGS: "-D warnings"
+    steps:
+      - name: '[DEBUG] print variables'
+        run: |
+          echo "all variables defined in set-variables"
+          echo "cache_key:      ${{ needs.set-variables.outputs.cache_key }}"
+          echo "release_id:     ${{ needs.set-variables.outputs.release_id }}"
+          echo "release_branch: ${{ needs.set-variables.outputs.release_branch }}"
+
+      # explicitly checkout the performance runner from main regardless of which
+      # version we are modeling.
+      - name: Checkout
+        uses: actions/checkout@v3
+        with:
+          ref: main
+
+      # attempts to access a previously cached runner
+      - uses: actions/cache@v3
+        id: cache
+        with:
+          path: ${{ env.RUNNER_CACHE_PATH }}
+          key: ${{ needs.set-variables.outputs.cache_key }}
+
+      - name: Fetch Rust Toolchain
+        if: steps.cache.outputs.cache-hit != 'true'
+        uses: actions-rs/toolchain@v1
+        with:
+          profile: minimal
+          toolchain: stable
+          override: true
+
+      - name: Add fmt
+        if: steps.cache.outputs.cache-hit != 'true'
+        run: rustup component add rustfmt
+
+      - name: Cargo fmt
+        if: steps.cache.outputs.cache-hit != 'true'
+        uses: actions-rs/cargo@v1
+        with:
+          command: fmt
+          args: --manifest-path performance/runner/Cargo.toml --all -- --check
+
+      - name: Test
+        if: steps.cache.outputs.cache-hit != 'true'
+        uses: actions-rs/cargo@v1
+        with:
+          command: test
+          args: --manifest-path performance/runner/Cargo.toml
+
+      - name: Build (optimized)
+        if: steps.cache.outputs.cache-hit != 'true'
+        uses: actions-rs/cargo@v1
+        with:
+          command: build
+          args: --release --manifest-path performance/runner/Cargo.toml
+      # the cache action automatically caches this binary at the end of the job
+
+  model:
+    # depends on `latest-runner` as a separate job so that failures in this job do not prevent
+    # a successfully tested and built binary from being cached.
+    needs: [set-variables, latest-runner]
+    name: Model a release
+    runs-on: ubuntu-latest
+    steps:
+
+      - name: '[DEBUG] print variables'
+        run: |
+          echo "all variables defined in set-variables"
+          echo "cache_key:      ${{ needs.set-variables.outputs.cache_key }}"
+          echo "release_id:     ${{ needs.set-variables.outputs.release_id }}"
+          echo "release_branch: ${{ needs.set-variables.outputs.release_branch }}"
+
+      - name: Setup Python
+        uses: actions/setup-python@v4
+        with:
+          python-version: "3.8"
+
+      - name: Install dbt
+        run: pip install dbt-postgres==${{ needs.set-variables.outputs.release_id }}
+
+      - name: Install Hyperfine
+        run: wget https://github.com/sharkdp/hyperfine/releases/download/v1.11.0/hyperfine_1.11.0_amd64.deb && sudo dpkg -i hyperfine_1.11.0_amd64.deb
+
+      # explicitly checkout main to get the latest project definitions
+      - name: Checkout
+        uses: actions/checkout@v3
+        with:
+          ref: main
+
+      # this was built in the previous job so it will be there.
+      - name: Fetch Runner
+        uses: actions/cache@v3
+        id: cache
+        with:
+          path: ${{ env.RUNNER_CACHE_PATH }}
+          key: ${{ needs.set-variables.outputs.cache_key }}
+
+      - name: Move Runner
+        run: mv performance/runner/target/release/runner performance/app
+
+      - name: Change Runner Permissions
+        run: chmod +x ./performance/app
+
+      - name: '[DEBUG] ls baseline directory before run'
+        run: ls -R performance/baselines/
+
+      # `${{ github.workspace }}` is used to pass the absolute path
+      - name: Create directories
+        run: |
+          mkdir ${{ github.workspace }}/performance/tmp/
+          mkdir -p performance/baselines/${{ needs.set-variables.outputs.release_id }}/
+
+      # Run modeling with taking 20 samples
+      - name: Run Measurement
+        run: |
+          performance/app model -v ${{ needs.set-variables.outputs.release_id }} -b ${{ github.workspace }}/performance/baselines/ -p ${{ github.workspace }}/performance/projects/ -t ${{ github.workspace }}/performance/tmp/ -n 20
+
+      - name: '[DEBUG] ls baseline directory after run'
+        run: ls -R performance/baselines/
+
+      - uses: actions/upload-artifact@v3
+        with:
+          name: baseline
+          path: performance/baselines/${{ needs.set-variables.outputs.release_id }}/
+
+  create-pr:
+    name: Open PR for ${{ matrix.base-branch }}
+
+    # depends on `model` as a separate job so that the baseline can be committed to more than one branch
+    # i.e. release branch and main
+    needs: [set-variables, latest-runner, model]
+    runs-on: ubuntu-latest
+
+    strategy:
+      matrix:
+        include:
+          - base-branch: refs/heads/main
+            target-branch: performance-bot/main_${{ needs.set-variables.outputs.release_id }}_${{GITHUB.RUN_ID}}
+          - base-branch: refs/heads/${{ needs.set-variables.outputs.release_branch }}
+            target-branch: performance-bot/release_${{ needs.set-variables.outputs.release_id }}_${{GITHUB.RUN_ID}}
+
+    steps:
+      - name: '[DEBUG] print variables'
+        run: |
+          echo "all variables defined in set-variables"
+          echo "cache_key:      ${{ needs.set-variables.outputs.cache_key }}"
+          echo "release_id:     ${{ needs.set-variables.outputs.release_id }}"
+          echo "release_branch: ${{ needs.set-variables.outputs.release_branch }}"
+
+      - name: Checkout
+        uses: actions/checkout@v3
+        with:
+          ref: ${{ matrix.base-branch }}
+
+      - name: Create PR branch
+        run: |
+          git checkout -b ${{ matrix.target-branch }}
+          git push origin ${{ matrix.target-branch }}
+          git branch --set-upstream-to=origin/${{ matrix.target-branch }} ${{ matrix.target-branch }}
+
+      - uses: actions/download-artifact@v3
+        with:
+          name: baseline
+          path: performance/baselines/${{ needs.set-variables.outputs.release_id }}
+
+      - name: '[DEBUG] ls baselines after artifact download'
+        run: ls -R performance/baselines/
+
+      - name: Commit baseline
+        uses: EndBug/add-and-commit@v9
+        with:
+          add: 'performance/baselines/*'
+          author_name: 'Github Build Bot'
+          author_email: 'buildbot@fishtownanalytics.com'
+          message: 'adding performance baseline for ${{ needs.set-variables.outputs.release_id }}'
+          push: 'origin origin/${{ matrix.target-branch }}'
+
+      - name: Create Pull Request
+        uses: peter-evans/create-pull-request@v5
+        with:
+          author: 'Github Build Bot <buildbot@fishtownanalytics.com>'
+          base: ${{ matrix.base-branch }}
+          branch: '${{ matrix.target-branch }}'
+          title: 'Adding performance modeling for ${{needs.set-variables.outputs.release_id}} to ${{ matrix.base-branch }}'
+          body: 'Committing perf results for tracking for the ${{needs.set-variables.outputs.release_id}}'
+          labels: |
+            Skip Changelog
+            Performance

.github/workflows/nightly-release.yml

@@ -20,7 +20,6 @@ on:
 
 permissions:
   contents: write # this is the permission that allows creating a new release
-  packages: write # this is the permission that allows Docker release
 
 defaults:
   run:
@@ -31,22 +30,29 @@ env:
 
 jobs:
   aggregate-release-data:
-    runs-on: ${{ vars.UBUNTU_LATEST }}
+    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@08eba0b27e820071cde6df949e0beb9ba4906955 # actions/checkout@v4
+        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=$(grep '^version = ' core/dbt/__version__.py | sed 's/version = "\(.*\)"/\1/')
+          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"
@@ -76,12 +82,13 @@ jobs:
           echo "name=${{ env.RELEASE_BRANCH }}" >> $GITHUB_OUTPUT
 
   log-outputs-aggregate-release-data:
-    runs-on: ${{ vars.UBUNTU_LATEST }}
+    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 }}
 
@@ -90,8 +97,13 @@ jobs:
 
     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-docker.yml

@@ -0,0 +1,118 @@
+# **what?**
+# This workflow will generate a series of docker images for dbt and push them to the github container registry
+
+# **why?**
+# Docker images for dbt are used in a number of important places throughout the dbt ecosystem.  This is how we keep those images up-to-date.
+
+# **when?**
+# This is triggered manually
+
+# **next steps**
+# - build this into the release workflow (or conversly, break out the different release methods into their own workflow files)
+
+name: Docker release
+
+permissions:
+  packages: write
+
+on:
+  workflow_dispatch:
+    inputs:
+      package:
+       description: The package to release. _One_ of [dbt-core, dbt-redshift, dbt-bigquery, dbt-snowflake, dbt-spark, dbt-postgres]
+       required: true
+      version_number:
+       description: The release version number (i.e. 1.0.0b1). Do not include `latest` tags or a leading `v`!
+       required: true
+
+jobs:
+  get_version_meta:
+    name: Get version meta
+    runs-on: ubuntu-latest
+    outputs:
+      major: ${{ steps.version.outputs.major }}
+      minor: ${{ steps.version.outputs.minor }}
+      patch: ${{ steps.version.outputs.patch }}
+      latest: ${{ steps.latest.outputs.latest }}
+      minor_latest: ${{ steps.latest.outputs.minor_latest }}
+    steps:
+      - uses: actions/checkout@v3
+      - name: Split version
+        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
+
+      - name: Is pkg 'latest'
+        id: latest
+        uses: ./.github/actions/latest-wrangler
+        with:
+          package: ${{ github.event.inputs.package }}
+          new_version: ${{ github.event.inputs.version_number }}
+          gh_token: ${{ secrets.GITHUB_TOKEN }}
+          halt_on_missing: False
+
+  setup_image_builder:
+    name: Set up docker image builder
+    runs-on: ubuntu-latest
+    needs: [get_version_meta]
+    steps:
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v2
+
+  build_and_push:
+    name: Build images and push to GHCR
+    runs-on: ubuntu-latest
+    needs: [setup_image_builder, get_version_meta]
+    steps:
+      - 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
+
+      - name: Log in to the GHCR
+        uses: docker/login-action@v2
+        with:
+          registry: ghcr.io
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Build and push MAJOR.MINOR.PATCH tag
+        uses: docker/build-push-action@v5
+        with:
+          file: docker/Dockerfile
+          push: True
+          target: ${{ github.event.inputs.package }}
+          build-args: |
+            ${{ steps.build_arg.outputs.build_arg_name }}_ref=${{ steps.build_arg.outputs.build_arg_value }}@v${{ github.event.inputs.version_number }}
+          tags: |
+            ghcr.io/dbt-labs/${{ github.event.inputs.package }}:${{ github.event.inputs.version_number }}
+
+      - name: Build and push MINOR.latest tag
+        uses: docker/build-push-action@v5
+        if: ${{ needs.get_version_meta.outputs.minor_latest == 'True' }}
+        with:
+          file: docker/Dockerfile
+          push: True
+          target: ${{ github.event.inputs.package }}
+          build-args: |
+            ${{ steps.build_arg.outputs.build_arg_name }}_ref=${{ steps.build_arg.outputs.build_arg_value }}@v${{ github.event.inputs.version_number }}
+          tags: |
+            ghcr.io/dbt-labs/${{ github.event.inputs.package }}:${{ needs.get_version_meta.outputs.major }}.${{ needs.get_version_meta.outputs.minor }}.latest
+
+      - name: Build and push latest tag
+        uses: docker/build-push-action@v5
+        if: ${{ needs.get_version_meta.outputs.latest == 'True' }}
+        with:
+          file: docker/Dockerfile
+          push: True
+          target: ${{ github.event.inputs.package }}
+          build-args: |
+            ${{ steps.build_arg.outputs.build_arg_name }}_ref=${{ steps.build_arg.outputs.build_arg_value }}@v${{ github.event.inputs.version_number }}
+          tags: |
+            ghcr.io/dbt-labs/${{ github.event.inputs.package }}:latest

.github/workflows/release.yml

@@ -7,7 +7,6 @@
 # - run unit and integration tests against given commit;
 # - build and package that SHA;
 # - release it to GitHub and PyPI with that specific build;
-# - release it to Docker
 #
 # **why?**
 # Ensure an automated and tested release process
@@ -15,12 +14,15 @@
 # **when?**
 # This workflow can be run manually on demand or can be called by other workflows
 
-name: "Release to GitHub, PyPI & Docker"
-run-name: "Release ${{ inputs.version_number }} to GitHub, PyPI & Docker"
+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
@@ -29,6 +31,26 @@ on:
         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
@@ -39,13 +61,12 @@ on:
         type: boolean
         default: false
         required: false
-      only_docker:
-        description: "Only release Docker image, skip GitHub & PyPI"
-        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
@@ -54,6 +75,26 @@ on:
         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
@@ -72,74 +113,45 @@ defaults:
   run:
     shell: bash
 
-env:
-  MIN_HATCH_VERSION: "1.11.0"
-
 jobs:
-  job-setup:
+  log-inputs:
     name: Log Inputs
-    runs-on: ${{ vars.UBUNTU_LATEST }}
-    outputs:
-      use_hatch: ${{ steps.use_hatch.outputs.use_hatch }}
+    runs-on: ubuntu-latest
     steps:
       - name: "[DEBUG] Print Variables"
         run: |
-          echo Inputs
+          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 }}
-          echo Only Docker:                        ${{ inputs.only_docker }}
-
-      # In version env.HATCH_VERSION we started to use hatch for build tooling.  Before that we used setuptools.
-      # This needs to check if we're using hatch or setuptools based on the version being released.  We should
-      # check if the version is greater than or equal to env.HATCH_VERSION.  If it is, we use hatch, otherwise we use setuptools.
-      - name: "Check if using hatch"
-        id: use_hatch
-        run: |
-          # Extract major.minor from versions like 1.11.0a1 -> 1.11
-          INPUT_MAJ_MIN=$(echo "${{ inputs.version_number }}" | sed -E 's/^([0-9]+\.[0-9]+).*/\1/')
-          HATCH_MAJ_MIN=$(echo "${{ env.MIN_HATCH_VERSION }}" | sed -E 's/^([0-9]+\.[0-9]+).*/\1/')
-
-          if [ $(echo "$INPUT_MAJ_MIN >= $HATCH_MAJ_MIN" | bc) -eq 1 ]; then
-            echo "use_hatch=true" >> $GITHUB_OUTPUT
-          else
-            echo "use_hatch=false" >> $GITHUB_OUTPUT
-          fi
-
-      - name: "Notify if using hatch"
-        run: |
-          if [ ${{ steps.use_hatch.outputs.use_hatch }} = "true" ]; then
-            echo "::notice title="Using Hatch": $title::Using Hatch for release"
-          else
-            echo "::notice title="Using Setuptools": $title::Using Setuptools for release"
-          fi
 
   bump-version-generate-changelog:
     name: Bump package version, Generate changelog
-    needs: [job-setup]
-    if: ${{ !inputs.only_docker }}
 
     uses: dbt-labs/dbt-release/.github/workflows/release-prep.yml@main
 
     with:
+      sha: ${{ inputs.sha }}
       version_number: ${{ inputs.version_number }}
-      hatch_directory: "core"
       target_branch: ${{ inputs.target_branch }}
-      env_setup_script_path: "scripts/env-setup.sh"
+      env_setup_script_path: ${{ inputs.env_setup_script_path }}
       test_run: ${{ inputs.test_run }}
       nightly_release: ${{ inputs.nightly_release }}
-      use_hatch: ${{ needs.job-setup.outputs.use_hatch == 'true' }}  # workflow outputs are strings...
 
     secrets: inherit
 
   log-outputs-bump-version-generate-changelog:
     name: "[Log output] Bump package version, Generate changelog"
-    if: ${{ !failure() && !cancelled() && !inputs.only_docker }}
+    if: ${{ !failure() && !cancelled() }}
 
     needs: [bump-version-generate-changelog]
 
-    runs-on: ${{ vars.UBUNTU_LATEST }}
+    runs-on: ubuntu-latest
 
     steps:
       - name: Print variables
@@ -149,25 +161,28 @@ jobs:
 
   build-test-package:
     name: Build, Test, Package
-    if: ${{ !failure() && !cancelled() && !inputs.only_docker }}
-    needs: [job-setup, bump-version-generate-changelog]
+    if: ${{ !failure() && !cancelled() }}
+    needs: [bump-version-generate-changelog]
 
     uses: dbt-labs/dbt-release/.github/workflows/build.yml@main
 
     with:
       sha: ${{ needs.bump-version-generate-changelog.outputs.final_sha }}
       version_number: ${{ inputs.version_number }}
-      hatch_directory: "core"
       changelog_path: ${{ needs.bump-version-generate-changelog.outputs.changelog_path }}
-      build_script_path: "scripts/build-dist.sh"
-      package_test_command: "dbt --version"
+      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 }}
-      use_hatch: ${{ needs.job-setup.outputs.use_hatch == 'true' }}  # workflow outputs are strings...
+
+    secrets:
+      AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
+      AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
 
   github-release:
     name: GitHub Release
-    if: ${{ !failure() && !cancelled() && !inputs.only_docker }}
+    if: ${{ !failure() && !cancelled() }}
 
     needs: [bump-version-generate-changelog, build-test-package]
 
@@ -194,51 +209,6 @@ jobs:
       PYPI_API_TOKEN: ${{ secrets.PYPI_API_TOKEN }}
       TEST_PYPI_API_TOKEN: ${{ secrets.TEST_PYPI_API_TOKEN }}
 
-  determine-docker-package:
-    # dbt-postgres exists within dbt-core for versions 1.7 and earlier but is a separate package for 1.8 and later.
-    # determine if we need to release dbt-core or both dbt-core and dbt-postgres
-    name: Determine Docker Package
-    if: ${{ !failure() && !cancelled() }}
-    runs-on: ${{ vars.UBUNTU_LATEST }}
-    needs: [pypi-release]
-    outputs:
-      matrix: ${{ steps.determine-docker-package.outputs.matrix }}
-    steps:
-      - name: "Audit Version And Parse Into Parts"
-        id: semver
-        uses: dbt-labs/actions/parse-semver@v1.1.0
-        with:
-          version: ${{ inputs.version_number }}
-
-      - name: "Determine Packages to Release"
-        id: determine-docker-package
-        run: |
-          if [ ${{ steps.semver.outputs.minor }} -ge 8 ]; then
-            json_output={\"package\":[\"dbt-core\"]}
-          else
-            json_output={\"package\":[\"dbt-core\",\"dbt-postgres\"]}
-          fi
-          echo "matrix=$json_output" >> $GITHUB_OUTPUT
-
-  docker-release:
-    name: "Docker Release for ${{ matrix.package }}"
-    needs: [determine-docker-package]
-    # We cannot release to docker on a test run because it uses the tag in GitHub as
-    # what we need to release but draft releases don't actually tag the commit so it
-    # finds nothing to release
-    if: ${{ !failure() && !cancelled() && (!inputs.test_run || inputs.only_docker) }}
-    strategy:
-      matrix: ${{fromJson(needs.determine-docker-package.outputs.matrix)}}
-
-    permissions:
-      packages: write
-
-    uses: dbt-labs/dbt-release/.github/workflows/release-docker.yml@main
-    with:
-      package: ${{ matrix.package }}
-      version_number: ${{ inputs.version_number }}
-      test_run: ${{ inputs.test_run }}
-
   slack-notification:
     name: Slack Notification
     if: ${{ failure() && (!inputs.test_run || inputs.nightly_release) }}
@@ -249,7 +219,6 @@ jobs:
         build-test-package,
         github-release,
         pypi-release,
-        docker-release,
       ]
 
     uses: dbt-labs/dbt-release/.github/workflows/slack-post-notification.yml@main
@@ -258,24 +227,3 @@ jobs:
 
     secrets:
       SLACK_WEBHOOK_URL: ${{ secrets.SLACK_DEV_CORE_ALERTS }}
-
-  testing-slack-notification:
-    # sends notifications to #slackbot-test
-    name: Testing - Slack Notification
-    if: ${{ failure() && inputs.test_run && !inputs.nightly_release }}
-
-    needs:
-      [
-        bump-version-generate-changelog,
-        build-test-package,
-        github-release,
-        pypi-release,
-        docker-release,
-      ]
-
-    uses: dbt-labs/dbt-release/.github/workflows/slack-post-notification.yml@main
-    with:
-      status: "failure"
-
-    secrets:
-      SLACK_WEBHOOK_URL: ${{ secrets.SLACK_TESTING_WEBHOOK_URL }}

.github/workflows/schema-check.yml

@@ -9,93 +9,82 @@
 # occur so we want to proactively alert to it.
 #
 # **when?**
-# Only can be run manually
+# On pushes to `develop` and release branches. Manual runs are also enabled.
 name: Artifact Schema Check
 
 on:
-  #  pull_request:
-  #    types: [ opened, reopened, labeled, unlabeled, synchronize ]
-  #    paths-ignore: [ '.changes/**', '.github/**', 'tests/**', '**.md', '**.yml' ]
-
   workflow_dispatch:
-    inputs:
-      target_branch:
-        description: "The branch to check against"
-        type: string
-        default: "main"
-        required: true
+  pull_request: #TODO: remove before merging
+  push:
+    branches:
+      - "develop"
+      - "*.latest"
+      - "releases/*"
 
 # no special access is needed
 permissions: read-all
 
 env:
   LATEST_SCHEMA_PATH: ${{ github.workspace }}/new_schemas
-  SCHEMA_DIFF_ARTIFACT: ${{ github.workspace }}/schema_changes.txt
+  SCHEMA_DIFF_ARTIFACT: ${{ github.workspace }}//schema_schanges.txt
   DBT_REPO_DIRECTORY: ${{ github.workspace }}/dbt
   SCHEMA_REPO_DIRECTORY: ${{ github.workspace }}/schemas.getdbt.com
 
 jobs:
   checking-schemas:
-    name: "Post-merge schema changes required"
-    runs-on: ${{ vars.UBUNTU_LATEST }}
+    name: "Checking schemas"
+    runs-on: ubuntu-latest
 
     steps:
       - name: Set up Python
-        uses: actions/setup-python@e797f83bcb11b83ae66e0230d6156d7c80228e7c # actions/setup-python@v6
+        uses: actions/setup-python@v4
         with:
-          python-version: "3.10"
+          python-version: 3.8
 
       - name: Checkout dbt repo
-        uses: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955 # actions/checkout@v4
+        uses: actions/checkout@v3
         with:
-          path: ${{ env.DBT_REPO_DIRECTORY }}
-          ref: ${{ inputs.target_branch }}
-
-      - name: Check for changes in core/dbt/artifacts
-        # https://github.com/marketplace/actions/paths-changes-filter
-        uses: dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36 # dorny/paths-filter@v3
-        id: check_artifact_changes
-        with:
-          filters: |
-            artifacts_changed:
-              - 'core/dbt/artifacts/**'
-          list-files: shell
-          working-directory: ${{ env.DBT_REPO_DIRECTORY }}
-
-      - name: Succeed if no artifacts have changed
-        if: steps.check_artifact_changes.outputs.artifacts_changed == 'false'
-        run: |
-          echo "No artifact changes found in core/dbt/artifacts. CI check passed."
+            path: ${{ env.DBT_REPO_DIRECTORY }}
 
       - name: Checkout schemas.getdbt.com repo
-        if: steps.check_artifact_changes.outputs.artifacts_changed == 'true'
-        uses: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955 # actions/checkout@v4
+        uses: actions/checkout@v3
         with:
           repository: dbt-labs/schemas.getdbt.com
-          ref: "main"
+          ref: 'main'
+          ssh-key: ${{ secrets.SCHEMA_SSH_PRIVATE_KEY }}
           path: ${{ env.SCHEMA_REPO_DIRECTORY }}
 
       - name: Generate current schema
-        if: steps.check_artifact_changes.outputs.artifacts_changed == 'true'
         run: |
-          cd ${{ env.DBT_REPO_DIRECTORY }}/core
-          pip install --upgrade pip hatch
-          hatch run setup
-          hatch run json-schema -- --path ${{ env.LATEST_SCHEMA_PATH }}
+          cd ${{ env.DBT_REPO_DIRECTORY }}
+          python3 -m venv env
+          source env/bin/activate
+          pip install --upgrade pip
+          pip install -r dev-requirements.txt -r editable-requirements.txt
+          python scripts/collect-artifact-schema.py --path ${{ env.LATEST_SCHEMA_PATH }}
 
       # Copy generated schema files into the schemas.getdbt.com repo
       # Do a git diff to find any changes
-      # Ignore any lines with date-like (yyyy-mm-dd) or version-like (x.y.z) changes
+      # Ignore any date or version changes though
       - name: Compare schemas
-        if: steps.check_artifact_changes.outputs.artifacts_changed == 'true'
         run: |
           cp -r ${{ env.LATEST_SCHEMA_PATH }}/dbt ${{ env.SCHEMA_REPO_DIRECTORY }}
           cd ${{ env.SCHEMA_REPO_DIRECTORY }}
-          git diff -I='*[0-9]{4}-[0-9]{2}-[0-9]{2}' -I='*[0-9]+\.[0-9]+\.[0-9]+' --exit-code > ${{ env.SCHEMA_DIFF_ARTIFACT }}
+          diff_results=$(git diff -I='*[0-9]{4}-(0[1-9]|1[0-2])-(0[1-9]|[1-2][0-9]|3[0-1])T' \
+          -I='*[0-9]{1}.[0-9]{2}.[0-9]{1}(rc[0-9]|b[0-9]| )' --compact-summary)
+          if [[ $(echo diff_results) ]]; then
+            echo $diff_results
+            echo "Schema changes detected!"
+            git diff -I='*[0-9]{4}-(0[1-9]|1[0-2])-(0[1-9]|[1-2][0-9]|3[0-1])T' \
+              -I='*[0-9]{1}.[0-9]{2}.[0-9]{1}(rc[0-9]|b[0-9]| )' > ${{ env.SCHEMA_DIFF_ARTIFACT }}
+            exit 1
+          else
+            echo "No schema changes detected"
+          fi
 
       - name: Upload schema diff
-        uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # actions/upload-artifact@v4
-        if: ${{ failure() && steps.check_artifact_changes.outputs.artifacts_changed == 'true' }}
+        uses: actions/upload-artifact@v3
+        if: ${{ failure() }}
         with:
-          name: "schema_changes.txt"
-          path: "${{ env.SCHEMA_DIFF_ARTIFACT }}"
+          name: 'schema_schanges.txt'
+          path: '${{ env.SCHEMA_DIFF_ARTIFACT }}'

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

@@ -14,8 +14,6 @@ on:
       - "*.latest"
       - "releases/*"
   pull_request:
-  merge_group:
-    types: [checks_requested]
   workflow_dispatch:
 
 permissions: read-all
@@ -47,7 +45,7 @@ jobs:
   # run the performance measurements on the current or default branch
   test-schema:
     name: Test Log Schema
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-20.04
     timeout-minutes: 30
     needs:
       - integration-metadata
@@ -69,49 +67,26 @@ jobs:
       DBT_TEST_USER_2: dbt_test_user_2
       DBT_TEST_USER_3: dbt_test_user_3
 
-    services:
-      # Label used to access the service container
-      postgres:
-        # Docker Hub image
-        image: postgres
-        # Provide the password for postgres
-        env:
-          POSTGRES_PASSWORD: password
-          POSTGRES_USER: postgres
-        # Set health checks to wait until postgres has started
-        options: >-
-          --health-cmd pg_isready
-          --health-interval 10s
-          --health-timeout 5s
-          --health-retries 5
-        ports:
-          - 5432:5432
-
     steps:
       - name: checkout dev
-        uses: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955 # actions/checkout@v4
+        uses: actions/checkout@v3
         with:
           persist-credentials: false
 
       - name: Setup Python
-        uses: actions/setup-python@e797f83bcb11b83ae66e0230d6156d7c80228e7c # actions/setup-python@v6
+        uses: actions/setup-python@v4
         with:
-          python-version: "3.10"
+          python-version: "3.8"
 
       - name: Install python dependencies
         run: |
           pip install --user --upgrade pip
           pip --version
-          pip install hatch
-          hatch --version
+          pip install tox
+          tox --version
 
-      - name: Run postgres setup script
-        run: |
-          ./scripts/setup_db.sh
-        env:
-          PGHOST: localhost
-          PGPORT: 5432
-          PGPASSWORD: password
+      - name: Set up postgres
+        uses: ./.github/actions/setup-postgres-linux
 
       - name: ls
         run: ls
@@ -119,11 +94,7 @@ jobs:
       # integration tests generate a ton of logs in different files. the next step will find them all.
       # we actually care if these pass, because the normal test run doesn't usually include many json log outputs
       - name: Run integration tests
-        uses: nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08 # nick-fields/retry@v3
-        with:
-          timeout_minutes: 30
-          max_attempts: 3
-          command: cd core && hatch run ci:integration-tests -- -nauto
+        run: tox -e integration -- -nauto
         env:
           PYTEST_ADDOPTS: ${{ format('--splits {0} --group {1}', env.PYTHON_INTEGRATION_TEST_WORKERS, matrix.split-group) }}
 

.github/workflows/test-repeater.yml

@@ -14,33 +14,35 @@ on:
   workflow_dispatch:
     inputs:
       branch:
-        description: "Branch to check out"
+        description: 'Branch to check out'
         type: string
         required: true
-        default: "main"
+        default: 'main'
       test_path:
-        description: "Path to single test to run (ex: tests/functional/retry/test_retry.py::TestRetry::test_fail_fast)"
+        description: 'Path to single test to run (ex: tests/functional/retry/test_retry.py::TestRetry::test_fail_fast)'
         type: string
         required: true
-        default: "tests/functional/..."
+        default: 'tests/functional/...'
       python_version:
-        description: "Version of Python to Test Against"
+        description: 'Version of Python to Test Against'
         type: choice
         options:
-          - "3.10"
-          - "3.11"
+          - '3.8'
+          - '3.9'
+          - '3.10'
+          - '3.11'
       os:
-        description: "OS to run test in"
+        description: 'OS to run test in'
         type: choice
         options:
-          - "ubuntu-latest"
-          - "macos-14"
-          - "windows-latest"
+          - 'ubuntu-latest'
+          - 'macos-latest'
+          - 'windows-latest'
       num_runs_per_batch:
-        description: "Max number of times to run the test per batch.  We always run 10 batches."
+        description: 'Max number of times to run the test per batch.  We always run 10 batches.'
         type: number
         required: true
-        default: "50"
+        default: '50'
 
 permissions: read-all
 
@@ -50,7 +52,7 @@ defaults:
 
 jobs:
   debug:
-    runs-on: ${{ vars.UBUNTU_LATEST }}
+    runs-on: ubuntu-latest
     steps:
       - name: "[DEBUG] Output Inputs"
         run: |
@@ -81,37 +83,26 @@ jobs:
 
     steps:
       - name: "Checkout code"
-        uses: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955 # actions/checkout@v4
+        uses: actions/checkout@v3
         with:
           ref: ${{ inputs.branch }}
 
       - name: "Setup Python"
-        uses: actions/setup-python@e797f83bcb11b83ae66e0230d6156d7c80228e7c # actions/setup-python@v6
+        uses: actions/setup-python@v4
         with:
           python-version: "${{ inputs.python_version }}"
 
-      - name: "Install hatch"
-        run: python -m pip install --user --upgrade pip hatch
-
       - name: "Setup Dev Environment"
-        run: |
-          cd core
-          hatch run setup
+        run: make dev
 
       - name: "Set up postgres (linux)"
-        if: inputs.os == '${{ vars.UBUNTU_LATEST }}'
-        run: |
-          cd core
-          hatch run setup-db
+        if: inputs.os == 'ubuntu-latest'
+        run: make setup-db
 
         # mac and windows don't use make due to limitations with docker with those runners in GitHub
-      - name: Set up postgres (macos)
-        if: runner.os == 'macOS'
-        uses: nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08 # nick-fields/retry@v3
-        with:
-          timeout_minutes: 10
-          max_attempts: 3
-          command: ./scripts/setup_db.sh
+      - name: "Set up postgres (macos)"
+        if: inputs.os == 'macos-latest'
+        uses: ./.github/actions/setup-postgres-macos
 
       - name: "Set up postgres (windows)"
         if: inputs.os == 'windows-latest'
@@ -160,5 +151,5 @@ jobs:
       - name: "Error for Failures"
         if: ${{ steps.pytest.outputs.failure }}
         run: |
-          echo "Batch ${{ matrix.batch }} failed ${{ steps.pytest.outputs.failure }} of ${{ inputs.num_runs_per_batch }} tests"
-          exit 1
+            echo "Batch ${{ matrix.batch }} failed ${{ steps.pytest.outputs.failure }} of ${{ inputs.num_runs_per_batch }} tests"
+            exit 1

.github/workflows/test/.actrc

@@ -0,0 +1 @@
+-P ubuntu-latest=ghcr.io/catthehacker/ubuntu:act-latest

.github/workflows/test/.gitignore

@@ -0,0 +1 @@
+.secrets

.github/workflows/test/.secrets.EXAMPLE

@@ -0,0 +1 @@
+GITHUB_TOKEN=GH_PERSONAL_ACCESS_TOKEN_GOES_HERE

.github/workflows/test/inputs/release_docker.json

@@ -0,0 +1,6 @@
+{
+    "inputs": {
+      "version_number": "1.0.1",
+      "package": "dbt-postgres"
+    }
+}

.github/workflows/version-bump.yml

@@ -0,0 +1,28 @@
+# **what?**
+# This workflow will take the new version number to bump to. 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.
+
+# **why?**
+# This is to aid in releasing dbt and making sure we have updated
+# the version in all places and generated the changelog.
+
+# **when?**
+# This is triggered manually
+
+name: Version Bump
+
+on:
+  workflow_dispatch:
+    inputs:
+      version_number:
+       description: 'The version number to bump to (ex. 1.2.0, 1.3.0b1)'
+       required: true
+
+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

.gitignore

@@ -15,7 +15,6 @@ build/
 !core/dbt/docs/build
 develop-eggs/
 dist/
-dist-*/
 downloads/
 eggs/
 .eggs/
@@ -58,9 +57,6 @@ test.env
 makefile.test.env
 *.pytest_cache/
 
-# Unit test artifacts
-index.html
-
 
 # Translations
 *.mo
@@ -96,7 +92,6 @@ target/
 # pycharm
 .idea/
 venv/
-.venv*/
 
 # AWS credentials
 .aws/
@@ -110,6 +105,3 @@ venv/
 
 # poetry
 poetry.lock
-
-# asdf
-.tool-versions

.isort.cfg

@@ -1,4 +0,0 @@
-[settings]
-profile=black
-extend_skip_glob=.github/*,third-party-stubs/*,scripts/*
-known_first_party=dbt,dbt_adapters,dbt_common,dbt_extractor,dbt_semantic_interfaces

.pre-commit-config.yaml

@@ -1,91 +1,62 @@
 # Configuration for pre-commit hooks (see https://pre-commit.com/).
 # Eventually the hooks described here will be run as tests before merging each PR.
 
-exclude: ^(core/dbt/docs/build/|core/dbt/common/events/types_pb2.py|core/dbt/adapters/events/adapter_types_pb2.py)
+exclude: ^(core/dbt/docs/build/|core/dbt/events/types_pb2.py)
 
-# Force all unspecified python hooks to run python 3.10
+# Force all unspecified python hooks to run python 3.8
 default_language_version:
   python: python3
 
 repos:
-  - repo: https://github.com/pre-commit/pre-commit-hooks
-    rev: v3.2.0
-    hooks:
-      - id: check-yaml
-        args: [--unsafe]
-      - id: check-json
-      - id: end-of-file-fixer
-        exclude: schemas/dbt/manifest/
-      - id: trailing-whitespace
-        exclude_types:
-          - "markdown"
-      - id: check-case-conflict
-  # local hooks are used to run the hooks in the local environment instead of a pre-commit isolated one.
-  # This ensures that the hooks are run with the same version of the dependencies as the local environment
-  # without having to manually keep them in sync.
-  - repo: local
-    hooks:
-      # Formatter/linter/type-checker pins live in the pyproject.dev optional dependency.
-      - id: isort
-        name: isort
-        entry: python -m isort
-        language: system
-        types: [python]
-      - id: black
-        name: black
-        entry: python -m black
-        language: system
-        types: [python]
-      - id: black-check
-        name: black-check
-        entry: python -m black
-        args:
-          - "--check"
-          - "--diff"
-        language: system
-        stages: [manual]
-        types: [python]
-      - id: flake8
-        name: flake8
-        entry: python -m flake8
-        language: system
-        types: [python]
-      - id: flake8-check
-        name: flake8-check
-        entry: python -m flake8
-        language: system
-        stages: [manual]
-        types: [python]
-      # N.B.: Mypy is... a bit fragile.
-      #
-      # By using `language: system` we run this hook in the local
-      # environment instead of a pre-commit isolated one.  This is needed
-      # to ensure mypy correctly parses the project.
-      #
-      # It may cause trouble
-      # in that it adds environmental variables out of our control to the
-      # mix.  Unfortunately, there's nothing we can do about per pre-commit's
-      # author.
-      # See https://github.com/pre-commit/pre-commit/issues/730 for details.
-      - id: mypy
-        name: mypy
-        entry: python -m mypy
-        args: [--show-error-codes]
-        files: ^core/dbt/
-        language: system
-        types: [python]
-      - id: mypy-check
-        name: mypy-check
-        entry: python -m mypy
-        args: [--show-error-codes, --pretty]
-        files: ^core/dbt/
-        language: system
-        stages: [manual]
-        types: [python]
-      - id: no_versioned_artifact_resource_imports
-        name: no_versioned_artifact_resource_imports
-        entry: python scripts/pre-commit-hooks/no_versioned_artifact_resource_imports.py
-        language: system
-        files: ^core/dbt/
-        types: [python]
-        pass_filenames: true
+- repo: https://github.com/pre-commit/pre-commit-hooks
+  rev: v3.2.0
+  hooks:
+  - id: check-yaml
+    args: [--unsafe]
+  - id: check-json
+  - id: end-of-file-fixer
+  - id: trailing-whitespace
+    exclude_types:
+      - "markdown"
+  - id: check-case-conflict
+- repo: https://github.com/psf/black
+  rev: 22.3.0
+  hooks:
+  - id: black
+  - id: black
+    alias: black-check
+    stages: [manual]
+    args:
+    - "--check"
+    - "--diff"
+- repo: https://github.com/pycqa/flake8
+  rev: 4.0.1
+  hooks:
+  - id: flake8
+  - id: flake8
+    alias: flake8-check
+    stages: [manual]
+- repo: https://github.com/pre-commit/mirrors-mypy
+  rev: v1.4.1
+  hooks:
+  - id: mypy
+    # N.B.: Mypy is... a bit fragile.
+    #
+    # By using `language: system` we run this hook in the local
+    # environment instead of a pre-commit isolated one.  This is needed
+    # to ensure mypy correctly parses the project.
+
+    # It may cause trouble
+    # in that it adds environmental variables out of our control to the
+    # mix.  Unfortunately, there's nothing we can do about per pre-commit's
+    # author.
+    # See https://github.com/pre-commit/pre-commit/issues/730 for details.
+    args: [--show-error-codes]
+    files: ^core/dbt/
+    language: system
+  - id: mypy
+    alias: mypy-check
+    stages: [manual]
+    args: [--show-error-codes, --pretty]
+    files: ^core/dbt/
+    language: system

ARCHITECTURE.md

@@ -6,6 +6,7 @@ Most of the python code in the repository is within the `core/dbt` directory.
 - [`single python files`](core/dbt/README.md): A number of individual files, such as 'compilation.py' and 'exceptions.py'
 
 The main subdirectories of core/dbt:
+- [`adapters`](core/dbt/adapters/README.md): Define base classes for behavior that is likely to differ across databases
 - [`clients`](core/dbt/clients/README.md): Interface with dependencies (agate, jinja) or across operating systems
 - [`config`](core/dbt/config/README.md): Reconcile user-supplied configuration from connection profiles, project files, and Jinja macros
 - [`context`](core/dbt/context/README.md): Build and expose dbt-specific Jinja functionality
@@ -13,21 +14,24 @@ The main subdirectories of core/dbt:
 - [`deps`](core/dbt/deps/README.md): Package installation and dependency resolution
 - [`events`](core/dbt/events/README.md): Logging events
 - [`graph`](core/dbt/graph/README.md): Produce a `networkx` DAG of project resources, and selecting those resources given user-supplied criteria
-- [`include`](core/dbt/include/README.md): Set up the starter project scaffold.
+- [`include`](core/dbt/include/README.md): The dbt "global project," which defines default implementations of Jinja2 macros
 - [`parser`](core/dbt/parser/README.md): Read project files, validate, construct python objects
 - [`task`](core/dbt/task/README.md): Set forth the actions that dbt can perform when invoked
 
+Legacy tests are found in the 'test' directory:
+- [`unit tests`](core/dbt/test/unit/README.md): Unit tests
+- [`integration tests`](core/dbt/test/integration/README.md): Integration tests
+
 ### Invoking dbt
 
 The "tasks" map to top-level dbt commands. So `dbt run` => task.run.RunTask, etc. Some are more like abstract base classes (GraphRunnableTask, for example) but all the concrete types outside of task should map to tasks. Currently one executes at a time. The tasks kick off their “Runners” and those do execute in parallel. The parallelism is managed via a thread pool, in GraphRunnableTask.
 
-core/dbt/task/docs/index.html
+core/dbt/include/index.html
 This is the docs website code. It comes from the dbt-docs repository, and is generated when a release is packaged.
 
 ## Adapters
 
-dbt uses an adapter-plugin pattern to extend support to different databases, warehouses, query engines, etc. 
-Note: dbt-postgres used to exist in dbt-core but is now in [the dbt-adapters repo](https://github.com/dbt-labs/dbt-adapters/tree/main/dbt-postgres) 
+dbt uses an adapter-plugin pattern to extend support to different databases, warehouses, query engines, etc. For testing and development purposes, the dbt-postgres plugin lives alongside the dbt-core codebase, in the [`plugins`](plugins) subdirectory. Like other adapter plugins, it is a self-contained codebase and package that builds on top of dbt-core.
 
 Each adapter is a mix of python, Jinja2, and SQL. The adapter code also makes heavy use of Jinja2 to wrap modular chunks of SQL functionality, define default implementations, and allow plugins to override it.
 
@@ -35,15 +39,16 @@ Each adapter plugin is a standalone python package that includes:
 
 - `dbt/include/[name]`: A "sub-global" dbt project, of YAML and SQL files, that reimplements Jinja macros to use the adapter's supported SQL syntax
 - `dbt/adapters/[name]`: Python modules that inherit, and optionally reimplement, the base adapter classes defined in dbt-core
-- `pyproject.toml`
+- `setup.py`
 
 The Postgres adapter code is the most central, and many of its implementations are used as the default defined in the dbt-core global project. The greater the distance of a data technology from Postgres, the more its adapter plugin may need to reimplement.
 
 ## Testing dbt
 
-The [`tests/`](tests/) subdirectory includes unit and fuctional tests that run as continuous integration checks against open pull requests. Unit tests check mock inputs and outputs of specific python functions. Functional tests perform end-to-end dbt invocations against real adapters (Postgres) and assert that the results match expectations. See [the contributing guide](CONTRIBUTING.md) for a step-by-step walkthrough of setting up a local development and testing environment.
+The [`test/`](test/) subdirectory includes unit and integration tests that run as continuous integration checks against open pull requests. Unit tests check mock inputs and outputs of specific python functions. Integration tests perform end-to-end dbt invocations against real adapters (Postgres, Redshift, Snowflake, BigQuery) and assert that the results match expectations. See [the contributing guide](CONTRIBUTING.md) for a step-by-step walkthrough of setting up a local development and testing environment.
 
 ## Everything else
 
 - [docker](docker/): All dbt versions are published as Docker images on DockerHub. This subfolder contains the `Dockerfile` (constant) and `requirements.txt` (one for each version).
+- [etc](etc/): Images for README
 - [scripts](scripts/): Helper scripts for testing, releasing, and producing JSON schemas. These are not included in distributions of dbt, nor are they rigorously tested—they're just handy tools for the dbt maintainers :)

CHANGELOG.md

@@ -1,19 +1,184 @@
 # dbt Core Changelog
 
-- This file provides a full account of all changes to `dbt-core`
+- This file provides a full account of all changes to `dbt-core` and `dbt-postgres`
 - Changes are listed under the (pre)release in which they first appear. Subsequent releases include changes from previous releases.
 - "Breaking changes" listed under a version may require action from end users or external maintainers when upgrading to that version.
 - Do not edit this file directly. This file is auto-generated using [changie](https://github.com/miniscruff/changie). For details on how to document a change, see [the contributing guide](https://github.com/dbt-labs/dbt-core/blob/main/CONTRIBUTING.md#adding-changelog-entry)
 
+## dbt-core 1.7.1 - November 07, 2023
+
+### Fixes
+
+- Fix compilation exception running empty seed file and support new Integer agate data_type ([#8895](https://github.com/dbt-labs/dbt-core/issues/8895))
+- Update run_results.json from previous versions of dbt to support deferral and rerun from failure ([#9010](https://github.com/dbt-labs/dbt-core/issues/9010))
+- Use MANIFEST.in to recursively include all jinja templates; fixes issue where some templates were not included in the distribution ([#9016](https://github.com/dbt-labs/dbt-core/issues/9016))
+- Fix git repository with subdirectory for Deps ([#9000](https://github.com/dbt-labs/dbt-core/issues/9000))
+
+
+
+## dbt-core 1.7.0 - November 02, 2023
+
+### Breaking Changes
+
+- Removed the FirstRunResultError and AfterFirstRunResultError event types, using the existing RunResultError in their place. ([#7963](https://github.com/dbt-labs/dbt-core/issues/7963))
+
+### Features
+
+- add log file of installed packages via dbt deps ([#6643](https://github.com/dbt-labs/dbt-core/issues/6643))
+- Enable re-population of metadata vars post-environment change during programmatic invocation ([#8010](https://github.com/dbt-labs/dbt-core/issues/8010))
+- Added support to configure a delimiter for a seed file, defaults to comma ([#3990](https://github.com/dbt-labs/dbt-core/issues/3990))
+- Allow specification of `create_metric: true` on measures ([#8125](https://github.com/dbt-labs/dbt-core/issues/8125))
+- Add node attributes related to compilation to run_results.json ([#7519](https://github.com/dbt-labs/dbt-core/issues/7519))
+- Add --no-inject-ephemeral-ctes flag for `compile` command, for usage by linting. ([#8480](https://github.com/dbt-labs/dbt-core/issues/8480))
+- Support configuration of semantic models with the addition of enable/disable and group enablement. ([#7968](https://github.com/dbt-labs/dbt-core/issues/7968))
+- Accept a `dbt-cloud` config in dbt_project.yml ([#8438](https://github.com/dbt-labs/dbt-core/issues/8438))
+- Support atomic replace in the global replace macro ([#8539](https://github.com/dbt-labs/dbt-core/issues/8539))
+- Use translate_type on data_type in model.columns in templates by default, remove no op `TYPE_LABELS` ([#8007](https://github.com/dbt-labs/dbt-core/issues/8007))
+- Add an option to generate static documentation ([#8614](https://github.com/dbt-labs/dbt-core/issues/8614))
+- Allow setting "access" as a config in addition to as a property ([#8383](https://github.com/dbt-labs/dbt-core/issues/8383))
+- Loosen typing requirement on renameable/replaceable relations to Iterable to allow adapters more flexibility in registering relation types, include docstrings as suggestions ([#8647](https://github.com/dbt-labs/dbt-core/issues/8647))
+- Add support for optional label in semantic_models, measures, dimensions and entities. ([#8595](https://github.com/dbt-labs/dbt-core/issues/8595), [#8755](https://github.com/dbt-labs/dbt-core/issues/8755))
+- Allow adapters to include package logs in dbt standard logging  ([#7859](https://github.com/dbt-labs/dbt-core/issues/7859))
+- Support storing test failures as views ([#6914](https://github.com/dbt-labs/dbt-core/issues/6914))
+- resolve packages with same git repo and unique subdirectory ([#5374](https://github.com/dbt-labs/dbt-core/issues/5374))
+- Add new ResourceReport event to record memory/cpu/io metrics ([#8342](https://github.com/dbt-labs/dbt-core/issues/8342))
+- Adding `date_spine` macro (and supporting macros) from dbt-utils to dbt-core ([#8172](https://github.com/dbt-labs/dbt-core/issues/8172))
+- Support `fill_nulls_with` and `join_to_timespine` for metric nodes ([#8593](https://github.com/dbt-labs/dbt-core/issues/8593), [#8755](https://github.com/dbt-labs/dbt-core/issues/8755))
+- Raise a warning when a contracted model has a numeric field without scale defined ([#8183](https://github.com/dbt-labs/dbt-core/issues/8183))
+- Added support for retrieving partial catalog information from a schema ([#8521](https://github.com/dbt-labs/dbt-core/issues/8521))
+- Add meta attribute to SemanticModels config ([#8511](https://github.com/dbt-labs/dbt-core/issues/8511))
+- Selectors with docs generate limits catalog generation ([#6014](https://github.com/dbt-labs/dbt-core/issues/6014))
+- Allow freshness to be determined via DBMS metadata for supported adapters ([#8704](https://github.com/dbt-labs/dbt-core/issues/8704))
+- Add support semantic layer SavedQuery node type ([#8594](https://github.com/dbt-labs/dbt-core/issues/8594))
+- Add exports to SavedQuery spec ([#8892](https://github.com/dbt-labs/dbt-core/issues/8892))
+
+### Fixes
+
+- Copy dir during `dbt deps` if symlink fails ([#7428](https://github.com/dbt-labs/dbt-core/issues/7428), [#8223](https://github.com/dbt-labs/dbt-core/issues/8223))
+- If --profile specified with dbt-init, create the project with the specified profile ([#6154](https://github.com/dbt-labs/dbt-core/issues/6154))
+- Fixed double-underline ([#5301](https://github.com/dbt-labs/dbt-core/issues/5301))
+- Copy target_schema from config into snapshot node ([#6745](https://github.com/dbt-labs/dbt-core/issues/6745))
+- Enable converting deprecation warnings to errors ([#8130](https://github.com/dbt-labs/dbt-core/issues/8130))
+- Add status to Parse Inline Error ([#8173](https://github.com/dbt-labs/dbt-core/issues/8173))
+- Ensure `warn_error_options` get serialized in `invocation_args_dict` ([#7694](https://github.com/dbt-labs/dbt-core/issues/7694))
+- Stop detecting materialization macros based on macro name ([#6231](https://github.com/dbt-labs/dbt-core/issues/6231))
+- Update `dbt deps` download retry logic to handle `EOFError` exceptions ([#6653](https://github.com/dbt-labs/dbt-core/issues/6653))
+- Improve handling of CTE injection with ephemeral models ([#8213](https://github.com/dbt-labs/dbt-core/issues/8213))
+- Fix unbound local variable error in `checked_agg_time_dimension_for_measure` ([#8230](https://github.com/dbt-labs/dbt-core/issues/8230))
+- Ensure runtime errors are raised for graph runnable tasks (compile, show, run, etc) ([#8166](https://github.com/dbt-labs/dbt-core/issues/8166))
+- Fix retry not working with log-file-max-bytes ([#8297](https://github.com/dbt-labs/dbt-core/issues/8297))
+- Add explicit support for integers for the show command ([#8153](https://github.com/dbt-labs/dbt-core/issues/8153))
+- Detect changes to model access, version, or latest_version in state:modified ([#8189](https://github.com/dbt-labs/dbt-core/issues/8189))
+- Add connection status into list of statuses for dbt debug ([#8350](https://github.com/dbt-labs/dbt-core/issues/8350))
+- fix fqn-selection for external versioned models ([#8374](https://github.com/dbt-labs/dbt-core/issues/8374))
+- Fix: DbtInternalError after model that previously ref'd external model is deleted ([#8375](https://github.com/dbt-labs/dbt-core/issues/8375))
+- Fix using list command with path selector and project-dir ([#8385](https://github.com/dbt-labs/dbt-core/issues/8385))
+- Remedy performance regression by only writing run_results.json once. ([#8360](https://github.com/dbt-labs/dbt-core/issues/8360))
+- Add support for swapping materialized views with tables/views and vice versa ([#8449](https://github.com/dbt-labs/dbt-core/issues/8449))
+- Turn breaking changes to contracted models into warnings for unversioned models ([#8384](https://github.com/dbt-labs/dbt-core/issues/8384), [#8282](https://github.com/dbt-labs/dbt-core/issues/8282))
+- Ensure parsing does not break when `window_groupings` is not specified for `non_additive_dimension` ([#8453](https://github.com/dbt-labs/dbt-core/issues/8453))
+- fix ambiguous reference error for tests and versions when model name is duplicated across packages ([#8327](https://github.com/dbt-labs/dbt-core/issues/8327), [#8493](https://github.com/dbt-labs/dbt-core/issues/8493))
+- Fix "Internal Error: Expected node <unique-id> not found in manifest" when depends_on set on ModelNodeArgs ([#8506](https://github.com/dbt-labs/dbt-core/issues/8506))
+- Fix snapshot success message ([#7583](https://github.com/dbt-labs/dbt-core/issues/7583))
+- Parse the correct schema version from manifest ([#8544](https://github.com/dbt-labs/dbt-core/issues/8544))
+- make version comparison insensitive to order ([#8571](https://github.com/dbt-labs/dbt-core/issues/8571))
+- Update metric helper functions to work with new semantic layer metrics ([#8134](https://github.com/dbt-labs/dbt-core/issues/8134))
+- Disallow cleaning paths outside current working directory ([#8318](https://github.com/dbt-labs/dbt-core/issues/8318))
+- Warn when --state == --target ([#8160](https://github.com/dbt-labs/dbt-core/issues/8160))
+- update dbt show to include limit in DWH query  ([#8496,](https://github.com/dbt-labs/dbt-core/issues/8496,), [#8417](https://github.com/dbt-labs/dbt-core/issues/8417))
+- Support quoted parameter list for MultiOption CLI options. ([#8598](https://github.com/dbt-labs/dbt-core/issues/8598))
+- Support global flags passed in after subcommands ([#6497](https://github.com/dbt-labs/dbt-core/issues/6497))
+- Lower bound of `8.0.2` for `click` ([#8683](https://github.com/dbt-labs/dbt-core/issues/8683))
+- Fixes test type edges filter ([#8692](https://github.com/dbt-labs/dbt-core/issues/8692))
+- semantic models in graph selection ([#8589](https://github.com/dbt-labs/dbt-core/issues/8589))
+- Support doc blocks in nested semantic model YAML ([#8509](https://github.com/dbt-labs/dbt-core/issues/8509))
+- avoid double-rendering sql_header in dbt show ([#8739](https://github.com/dbt-labs/dbt-core/issues/8739))
+- Fix tag selection for projects with semantic models ([#8749](https://github.com/dbt-labs/dbt-core/issues/8749))
+- Foreign key constraint on incremental model results in Database Error ([#8022](https://github.com/dbt-labs/dbt-core/issues/8022))
+- Support docs blocks on versioned model column descriptions ([#8540](https://github.com/dbt-labs/dbt-core/issues/8540))
+- Enable seeds to be handled from stored manifest data ([#6875](https://github.com/dbt-labs/dbt-core/issues/6875))
+- Override path-like args in dbt retry ([#8682](https://github.com/dbt-labs/dbt-core/issues/8682))
+- Group updates on unmodified nodes are handled gracefully for state:modified ([#8371](https://github.com/dbt-labs/dbt-core/issues/8371))
+- Partial parsing fix for adding groups and updating models at the same time ([#8697](https://github.com/dbt-labs/dbt-core/issues/8697))
+- Fix partial parsing not working for semantic model change ([#8859](https://github.com/dbt-labs/dbt-core/issues/8859))
+- Rework get_catalog implementation to retain previous adapter interface semantics ([#8846](https://github.com/dbt-labs/dbt-core/issues/8846))
+- Add back contract enforcement for temporary tables on postgres ([#8857](https://github.com/dbt-labs/dbt-core/issues/8857))
+- Add version to fqn when version==0 ([#8836](https://github.com/dbt-labs/dbt-core/issues/8836))
+- Fix cased comparison in catalog-retrieval function. ([#8939](https://github.com/dbt-labs/dbt-core/issues/8939))
+- Catalog queries now assign the correct type to materialized views ([#8864](https://github.com/dbt-labs/dbt-core/issues/8864))
+- Make relation filtering None-tolerant for maximal flexibility across adapters. ([#8974](https://github.com/dbt-labs/dbt-core/issues/8974))
+
+### Docs
+
+- Corrected spelling of "Partiton" ([dbt-docs/#8100](https://github.com/dbt-labs/dbt-docs/issues/8100))
+- Remove static SQL codeblock for metrics ([dbt-docs/#436](https://github.com/dbt-labs/dbt-docs/issues/436))
+- fixed comment util.py ([dbt-docs/#None](https://github.com/dbt-labs/dbt-docs/issues/None))
+- Fix newline escapes and improve formatting in docker README ([dbt-docs/#8211](https://github.com/dbt-labs/dbt-docs/issues/8211))
+- Display contract and column constraints on the model page ([dbt-docs/#433](https://github.com/dbt-labs/dbt-docs/issues/433))
+- Display semantic model details in docs ([dbt-docs/#431](https://github.com/dbt-labs/dbt-docs/issues/431))
+
+### Under the Hood
+
+- Switch from hologram to mashumaro jsonschema ([#8426](https://github.com/dbt-labs/dbt-core/issues/8426))
+- Refactor flaky test pp_versioned_models ([#7781](https://github.com/dbt-labs/dbt-core/issues/7781))
+- format exception from dbtPlugin.initialize ([#8152](https://github.com/dbt-labs/dbt-core/issues/8152))
+- A way to control maxBytes for a single dbt.log file ([#8199](https://github.com/dbt-labs/dbt-core/issues/8199))
+- Ref expressions with version can now be processed by the latest version of the high-performance dbt-extractor library. ([#7688](https://github.com/dbt-labs/dbt-core/issues/7688))
+- Bump manifest schema version to v11, freeze manifest v10 ([#8333](https://github.com/dbt-labs/dbt-core/issues/8333))
+- add tracking for plugin.get_nodes calls ([#8344](https://github.com/dbt-labs/dbt-core/issues/8344))
+- add internal flag: --no-partial-parse-file-diff to inform whether to compute a file diff during partial parsing ([#8363](https://github.com/dbt-labs/dbt-core/issues/8363))
+- Add return values to a number of functions for mypy ([#8389](https://github.com/dbt-labs/dbt-core/issues/8389))
+- Fix mypy warnings for ManifestLoader.load() ([#8401](https://github.com/dbt-labs/dbt-core/issues/8401))
+- Use python version 3.10.7 in Docker image. ([#8444](https://github.com/dbt-labs/dbt-core/issues/8444))
+- Re-organize jinja macros: relation-specific in /macros/adapters/relations/<relation>, relation agnostic in /macros/relations ([#8449](https://github.com/dbt-labs/dbt-core/issues/8449))
+- Update typing to meet mypy standards ([#8396](https://github.com/dbt-labs/dbt-core/issues/8396))
+- Mypy errors - adapters/factory.py ([#8387](https://github.com/dbt-labs/dbt-core/issues/8387))
+- Added more type annotations. ([#8537](https://github.com/dbt-labs/dbt-core/issues/8537))
+- Audit potential circular dependencies ([#8349](https://github.com/dbt-labs/dbt-core/issues/8349))
+- Add functional test for advanced ref override ([#8566](https://github.com/dbt-labs/dbt-core/issues/8566))
+- Add typing to __init__ in base.py ([#8398](https://github.com/dbt-labs/dbt-core/issues/8398))
+- Fix untyped functions in task/runnable.py (mypy warning) ([#8402](https://github.com/dbt-labs/dbt-core/issues/8402))
+- add a test for ephemeral cte injection ([#8225](https://github.com/dbt-labs/dbt-core/issues/8225))
+- Fix test_numeric_values to look for more specific strings ([#8470](https://github.com/dbt-labs/dbt-core/issues/8470))
+- Pin types-requests<2.31.0 in `dev-requirements.txt` ([#8789](https://github.com/dbt-labs/dbt-core/issues/8789))
+- Add warning_tag to UnversionedBreakingChange ([#8827](https://github.com/dbt-labs/dbt-core/issues/8827))
+- Update v10 manifest schema to match 1.6 for testing schema compatibility ([#8835](https://github.com/dbt-labs/dbt-core/issues/8835))
+- Add a no-op runner for Saved Qeury ([#8893](https://github.com/dbt-labs/dbt-core/issues/8893))
+
+### Dependencies
+
+- Bump mypy from 1.3.0 to 1.4.0 ([#7912](https://github.com/dbt-labs/dbt-core/pull/7912))
+- Bump mypy from 1.4.0 to 1.4.1 ([#8219](https://github.com/dbt-labs/dbt-core/pull/8219))
+- Update pin for click<9 ([#8232](https://github.com/dbt-labs/dbt-core/pull/8232))
+- Add upper bound to sqlparse pin of <0.5 ([#8236](https://github.com/dbt-labs/dbt-core/pull/8236))
+- Support dbt-semantic-interfaces 0.2.0 ([#8250](https://github.com/dbt-labs/dbt-core/pull/8250))
+- Bump docker/build-push-action from 4 to 5 ([#8783](https://github.com/dbt-labs/dbt-core/pull/8783))
+- Upgrade dbt-semantic-interfaces dep to 0.3.0 ([#8819](https://github.com/dbt-labs/dbt-core/pull/8819))
+- Begin using DSI 0.4.x ([#8892](https://github.com/dbt-labs/dbt-core/pull/8892))
+
+### Contributors
+- [@anjutiwari](https://github.com/anjutiwari) ([#7428](https://github.com/dbt-labs/dbt-core/issues/7428), [#8223](https://github.com/dbt-labs/dbt-core/issues/8223))
+- [@benmosher](https://github.com/benmosher) ([#8480](https://github.com/dbt-labs/dbt-core/issues/8480))
+- [@d-kaneshiro](https://github.com/d-kaneshiro) ([#None](https://github.com/dbt-labs/dbt-core/issues/None))
+- [@dave-connors-3](https://github.com/dave-connors-3) ([#8153](https://github.com/dbt-labs/dbt-core/issues/8153), [#8589](https://github.com/dbt-labs/dbt-core/issues/8589))
+- [@dylan-murray](https://github.com/dylan-murray) ([#8683](https://github.com/dbt-labs/dbt-core/issues/8683))
+- [@ezraerb](https://github.com/ezraerb) ([#6154](https://github.com/dbt-labs/dbt-core/issues/6154))
+- [@gem7318](https://github.com/gem7318) ([#8010](https://github.com/dbt-labs/dbt-core/issues/8010))
+- [@jamezrin](https://github.com/jamezrin) ([#8211](https://github.com/dbt-labs/dbt-core/issues/8211))
+- [@jusbaldw](https://github.com/jusbaldw) ([#6643](https://github.com/dbt-labs/dbt-core/issues/6643))
+- [@lllong33](https://github.com/lllong33) ([#5301](https://github.com/dbt-labs/dbt-core/issues/5301))
+- [@marcodamore](https://github.com/marcodamore) ([#436](https://github.com/dbt-labs/dbt-core/issues/436))
+- [@mescanne](https://github.com/mescanne) ([#8614](https://github.com/dbt-labs/dbt-core/issues/8614))
+- [@pgoslatara](https://github.com/pgoslatara) ([#8100](https://github.com/dbt-labs/dbt-core/issues/8100))
+- [@philippeboyd](https://github.com/philippeboyd) ([#5374](https://github.com/dbt-labs/dbt-core/issues/5374))
+- [@ramonvermeulen](https://github.com/ramonvermeulen) ([#3990](https://github.com/dbt-labs/dbt-core/issues/3990))
+- [@renanleme](https://github.com/renanleme) ([#8692](https://github.com/dbt-labs/dbt-core/issues/8692))
+
 ## Previous Releases
 
 For information on prior major and minor releases, see their changelogs:
 
-* [1.11](https://github.com/dbt-labs/dbt-core/blob/1.11.latest/CHANGELOG.md)
-* [1.10](https://github.com/dbt-labs/dbt-core/blob/1.10.latest/CHANGELOG.md)
-* [1.9](https://github.com/dbt-labs/dbt-core/blob/1.9.latest/CHANGELOG.md)
-* [1.8](https://github.com/dbt-labs/dbt-core/blob/1.8.latest/CHANGELOG.md)
-* [1.7](https://github.com/dbt-labs/dbt-core/blob/1.7.latest/CHANGELOG.md)
+
 * [1.6](https://github.com/dbt-labs/dbt-core/blob/1.6.latest/CHANGELOG.md)
 * [1.5](https://github.com/dbt-labs/dbt-core/blob/1.5.latest/CHANGELOG.md)
 * [1.4](https://github.com/dbt-labs/dbt-core/blob/1.4.latest/CHANGELOG.md)

CONTRIBUTING.md

@@ -2,48 +2,29 @@
 
 `dbt-core` is open source software. It is what it is today because community members have opened issues, provided feedback, and [contributed to the knowledge loop](https://www.getdbt.com/dbt-labs/values/). Whether you are a seasoned open source contributor or a first-time committer, we welcome and encourage you to contribute code, documentation, ideas, or problem statements to this project.
 
-- [Contributing to `dbt-core`](#contributing-to-dbt-core)
-  - [About this document](#about-this-document)
-    - [Notes](#notes)
-  - [Getting the code](#getting-the-code)
-    - [Installing git](#installing-git)
-    - [External contributors](#external-contributors)
-    - [dbt Labs contributors](#dbt-labs-contributors)
-  - [Setting up an environment](#setting-up-an-environment)
-    - [Tools](#tools)
-      - [Virtual environments](#virtual-environments)
-      - [Docker and `docker-compose`](#docker-and-docker-compose)
-      - [Postgres (optional)](#postgres-optional)
-  - [Running `dbt-core` in development](#running-dbt-core-in-development)
-    - [Installation](#installation)
-    - [Running `dbt-core`](#running-dbt-core)
-  - [Testing](#testing)
-    - [Initial setup](#initial-setup)
-    - [Test commands](#test-commands)
-      - [Hatch scripts](#hatch-scripts)
-      - [`pre-commit`](#pre-commit)
-      - [`pytest`](#pytest)
-    - [Unit, Integration, Functional?](#unit-integration-functional)
-  - [Debugging](#debugging)
-    - [Assorted development tips](#assorted-development-tips)
-  - [Adding or modifying a CHANGELOG Entry](#adding-or-modifying-a-changelog-entry)
-  - [Submitting a Pull Request](#submitting-a-pull-request)
-  - [Troubleshooting Tips](#troubleshooting-tips)
+1. [About this document](#about-this-document)
+2. [Getting the code](#getting-the-code)
+3. [Setting up an environment](#setting-up-an-environment)
+4. [Running dbt-core in development](#running-dbt-core-in-development)
+5. [Testing dbt-core](#testing)
+6. [Debugging](#debugging)
+7. [Adding or modifying a changelog entry](#adding-or-modifying-a-changelog-entry)
+8. [Submitting a Pull Request](#submitting-a-pull-request)
 
 ## About this document
 
 There are many ways to contribute to the ongoing development of `dbt-core`, such as by participating in discussions and issues. We encourage you to first read our higher-level document: ["Expectations for Open Source Contributors"](https://docs.getdbt.com/docs/contributing/oss-expectations).
 
-The rest of this document serves as a more granular guide for contributing code changes to `dbt-core` (this repository). It is not intended as a guide for using `dbt-core`, and some pieces assume a level of familiarity with Python development and package managers. Specific code snippets in this guide assume you are using macOS or Linux and are comfortable with the command line.
+The rest of this document serves as a more granular guide for contributing code changes to `dbt-core` (this repository). It is not intended as a guide for using `dbt-core`, and some pieces assume a level of familiarity with Python development (virtualenvs, `pip`, etc). Specific code snippets in this guide assume you are using macOS or Linux and are comfortable with the command line.
 
 If you get stuck, we're happy to help! Drop us a line in the `#dbt-core-development` channel in the [dbt Community Slack](https://community.getdbt.com).
 
 ### Notes
 
-- **Adapters:** Is your issue or proposed code change related to a specific [database adapter](https://docs.getdbt.com/docs/available-adapters)? If so, please open issues, PRs, and discussions in that adapter's repository instead.
+- **Adapters:** Is your issue or proposed code change related to a specific [database adapter](https://docs.getdbt.com/docs/available-adapters)? If so, please open issues, PRs, and discussions in that adapter's repository instead. The sole exception is Postgres; the `dbt-postgres` plugin lives in this repository (`dbt-core`).
 - **CLA:** Please note that anyone contributing code to `dbt-core` must sign the [Contributor License Agreement](https://docs.getdbt.com/docs/contributor-license-agreements). If you are unable to sign the CLA, the `dbt-core` maintainers will unfortunately be unable to merge any of your Pull Requests. We welcome you to participate in discussions, open issues, and comment on existing ones.
 - **Branches:** All pull requests from community contributors should target the `main` branch (default). If the change is needed as a patch for a minor version of dbt that has already been released (or is already a release candidate), a maintainer will backport the changes in your PR to the relevant "latest" release branch (`1.0.latest`, `1.1.latest`, ...). If an issue fix applies to a release branch, that fix should be first committed to the development branch and then to the release branch (rarely release-branch fixes may not apply to `main`).
-- **Releases**: Before releasing a new minor version of Core, we prepare a series of alphas and release candidates to allow users (especially employees of dbt Labs!) to test the new version in live environments. This is an important quality assurance step, as it exposes the new code to a wide variety of complicated deployments and can surface bugs before official release. Releases are accessible via our [supported installation methods](https://docs.getdbt.com/docs/core/installation-overview#install-dbt-core).
+- **Releases**: Before releasing a new minor version of Core, we prepare a series of alphas and release candidates to allow users (especially employees of dbt Labs!) to test the new version in live environments. This is an important quality assurance step, as it exposes the new code to a wide variety of complicated deployments and can surface bugs before official release. Releases are accessible via pip, homebrew, and dbt Cloud.
 
 ## Getting the code
 
@@ -63,7 +44,9 @@ If you are not a member of the `dbt-labs` GitHub organization, you can contribut
 
 ### dbt Labs contributors
 
-If you are a member of the `dbt-labs` GitHub organization, you will have push access to the `dbt-core` repo. Rather than forking `dbt-core` to make your changes, just clone the repository, check out a new branch, and push directly to that branch.
+If you are a member of the `dbt-labs` GitHub organization, you will have push access to the `dbt-core` repo. Rather than forking `dbt-core` to make your changes, just clone the repository, check out a new branch, and push directly to that branch. Branch names should be fixed by `CT-XXX/` where:
+* CT stands for 'core team'
+* XXX stands for a JIRA ticket number
 
 ## Setting up an environment
 
@@ -73,22 +56,28 @@ There are some tools that will be helpful to you in developing locally. While th
 
 These are the tools used in `dbt-core` development and testing:
 
-- [`hatch`](https://hatch.pypa.io/) for build backend, environment management, and running tests across Python versions (3.10, 3.11, 3.12, and 3.13)
+- [`tox`](https://tox.readthedocs.io/en/latest/) to manage virtualenvs across python versions. We currently target the latest patch releases for Python 3.8, 3.9, 3.10 and 3.11
 - [`pytest`](https://docs.pytest.org/en/latest/) to define, discover, and run tests
 - [`flake8`](https://flake8.pycqa.org/en/latest/) for code linting
 - [`black`](https://github.com/psf/black) for code formatting
 - [`mypy`](https://mypy.readthedocs.io/en/stable/) for static type checking
 - [`pre-commit`](https://pre-commit.com) to easily run those checks
 - [`changie`](https://changie.dev/) to create changelog entries, without merge conflicts
+- [`make`](https://users.cs.duke.edu/~ola/courses/programming/Makefiles/Makefiles.html) to run multiple setup or test steps in combination. Don't worry too much, nobody _really_ understands how `make` works, and our Makefile aims to be super simple.
 - [GitHub Actions](https://github.com/features/actions) for automating tests and checks, once a PR is pushed to the `dbt-core` repository
 
 A deep understanding of these tools in not required to effectively contribute to `dbt-core`, but we recommend checking out the attached documentation if you're interested in learning more about each one.
 
 #### Virtual environments
 
-dbt-core uses [Hatch](https://hatch.pypa.io/) for dependency and environment management. Hatch automatically creates and manages isolated environments for development, testing, and building, so you don't need to manually create virtual environments.
+We strongly recommend using virtual environments when developing code in `dbt-core`. We recommend creating this virtualenv
+in the root of the `dbt-core` repository. To create a new virtualenv, run:
+```sh
+python3 -m venv env
+source env/bin/activate
+```
 
-For more information on how Hatch manages environments, see the [Hatch environment documentation](https://hatch.pypa.io/latest/environment/).
+This will create and activate a new Python virtual environment.
 
 #### Docker and `docker-compose`
 
@@ -107,42 +96,22 @@ brew install postgresql
 
 ### Installation
 
-First make sure you have Python 3.10 or later installed. Ensure you have the latest version of pip installed with `pip install --upgrade pip`. Next, install `hatch`.  Finally set up `dbt-core` for development:
+First make sure that you set up your `virtualenv` as described in [Setting up an environment](#setting-up-an-environment).  Also ensure you have the latest version of pip installed with `pip install --upgrade pip`. Next, install `dbt-core` (and its dependencies):
 
 ```sh
-cd core
-hatch run setup
+make dev
 ```
-
-This will install all development dependencies and set up pre-commit hooks.
-
-By default, hatch will use whatever Python version is active in your environment. To specify a particular Python version, set the `HATCH_PYTHON` environment variable:
-
+or, alternatively:
 ```sh
-export HATCH_PYTHON=3.12
-hatch env create
+pip install -r dev-requirements.txt -r editable-requirements.txt
+pre-commit install
 ```
 
-Or add it to your shell profile (e.g., `~/.zshrc` or `~/.bashrc`) for persistence.
-
 When installed in this way, any changes you make to your local copy of the source code will be reflected immediately in your next `dbt` run.
 
-#### Building dbt-core
-
-dbt-core uses [Hatch](https://hatch.pypa.io/) (specifically `hatchling`) as its build backend. To build distribution packages:
-
-```sh
-cd core
-hatch build
-```
-
-This will create both wheel (`.whl`) and source distribution (`.tar.gz`) files in the `dist/` directory.
-
-The build configuration is defined in `core/pyproject.toml`. You can also use the standard `python -m build` command if you prefer.
-
 ### Running `dbt-core`
 
-Once you've run `hatch run setup`, the `dbt` command will be available in your PATH. You can verify this by running `which dbt`.
+With your virtualenv activated, the `dbt` script should point back to the source code you've cloned on your machine. You can verify this by running `which dbt`. This command should show you a path to an executable in your virtualenv.
 
 Configure your [profile](https://docs.getdbt.com/docs/configure-your-profile) as necessary to connect to your target databases. It may be a good idea to add a new profile pointing to a local Postgres instance, or a specific test sandbox within your data warehouse if appropriate. Make sure to create a profile before running integration tests.
 
@@ -160,84 +129,51 @@ Although `dbt-core` works with a number of different databases, you won't need t
 Postgres offers the easiest way to test most `dbt-core` functionality today. They are the fastest to run, and the easiest to set up. To run the Postgres integration tests, you'll have to do one extra step of setting up the test database:
 
 ```sh
-cd core
-hatch run setup-db
+make setup-db
 ```
-
-Alternatively, you can run the setup commands directly:
-
+or, alternatively:
 ```sh
 docker-compose up -d database
-PGHOST=localhost PGUSER=root PGPASSWORD=password PGDATABASE=postgres bash scripts/setup_db.sh
+PGHOST=localhost PGUSER=root PGPASSWORD=password PGDATABASE=postgres bash test/setup_db.sh
 ```
 
 ### Test commands
 
 There are a few methods for running tests locally.
 
-#### Hatch scripts
+#### Makefile
 
-The primary way to run tests and checks is using hatch scripts (defined in `core/hatch.toml`):
+There are multiple targets in the Makefile to run common test suites and code
+checks, most notably:
 
 ```sh
-cd core
-
-# Run all unit tests
-hatch run unit-tests
-
-# Run unit tests and all code quality checks
-hatch run test
-
-# Run integration tests
-hatch run integration-tests
-
-# Run integration tests in fail-fast mode
-hatch run integration-tests-fail-fast
-
-# Run linting checks only
-hatch run lint
-hatch run flake8
-hatch run mypy
-hatch run black
-
-# Run all pre-commit hooks
-hatch run code-quality
-
-# Clean build artifacts
-hatch run clean
+# Runs unit tests with py38 and code checks in parallel.
+make test
+# Runs postgres integration tests with py38 in "fail fast" mode.
+make integration
 ```
+> These make targets assume you have a local installation of a recent version of [`tox`](https://tox.readthedocs.io/en/latest/) for unit/integration testing and pre-commit for code quality checks,
+> unless you use choose a Docker container to run tests. Run `make help` for more info.
 
-Hatch manages isolated environments and dependencies automatically. The commands above use the `default` environment which is recommended for most local development.
-
-**Using the `ci` environment (optional)**
-
-If you need to replicate exactly what runs in GitHub Actions (e.g., with coverage reporting), use the `ci` environment:
-
-```sh
-cd core
-
-# Run unit tests with coverage
-hatch run ci:unit-tests
-
-# Run unit tests with a specific Python version
-hatch run +py=3.11 ci:unit-tests
-```
-
-> **Note:** Most developers should use the default environment (`hatch run unit-tests`). The `ci` environment is primarily for debugging CI failures or running tests with coverage.
+Check out the other targets in the Makefile to see other commonly used test
+suites.
 
 #### `pre-commit`
+[`pre-commit`](https://pre-commit.com) takes care of running all code-checks for formatting and linting. Run `make dev` to install `pre-commit` in your local environment (we recommend running this command with a python virtual environment active). This command installs several pip executables including black, mypy, and flake8. Once this is done you can use any of the linter-based make targets as well as a git pre-commit hook that will ensure proper formatting and linting.
 
-[`pre-commit`](https://pre-commit.com) takes care of running all code-checks for formatting and linting. Run `hatch run setup` to install `pre-commit` in your local environment (we recommend running this command with a python virtual environment active). This installs several pip executables including black, mypy, and flake8. Once installed, hooks will run automatically on `git commit`, or you can run them manually with `hatch run code-quality`.
+#### `tox`
+
+[`tox`](https://tox.readthedocs.io/en/latest/) takes care of managing virtualenvs and install dependencies in order to run tests. You can also run tests in parallel, for example, you can run unit tests for Python 3.8, Python 3.9, Python 3.10 and Python 3.11 checks in parallel with `tox -p`. Also, you can run unit tests for specific python versions with `tox -e py38`. The configuration for these tests in located in `tox.ini`.
 
 #### `pytest`
 
-Finally, you can also run a specific test or group of tests using [`pytest`](https://docs.pytest.org/en/latest/) directly. After running `hatch run setup`, you can run pytest commands like:
+Finally, you can also run a specific test or group of tests using [`pytest`](https://docs.pytest.org/en/latest/) directly. With a virtualenv active and dev dependencies installed you can do things like:
 
 ```sh
 # run all unit tests in a file
-python3 -m pytest tests/unit/test_invocation_id.py
+python3 -m pytest tests/unit/test_graph.py
 # run a specific unit test
-python3 -m pytest tests/unit/test_invocation_id.py::TestInvocationId::test_invocation_id
+python3 -m pytest tests/unit/test_graph.py::GraphTest::test__dependency_list
 # run specific Postgres functional tests
 python3 -m pytest tests/functional/sources
 ```
@@ -285,14 +221,10 @@ You don't need to worry about which `dbt-core` version your change will go into.
 
 ## Submitting a Pull Request
 
-Code can be merged into the current development branch `main` by opening a pull request. If the proposal looks like it's on the right track, then a `dbt-core` maintainer will triage the PR and label it as `ready_for_review`. From this point, two code reviewers will be assigned with the aim of responding to any updates to the PR within about one week. They may suggest code revision for style or clarity, or request that you add unit or integration test(s). These are good things! We believe that, with a little bit of help, anyone can contribute high-quality code. Once merged, your contribution will be available for the next release of `dbt-core`.
+Code can be merged into the current development branch `main` by opening a pull request. A `dbt-core` maintainer will review your PR. They may suggest code revision for style or clarity, or request that you add unit or integration test(s). These are good things! We believe that, with a little bit of help, anyone can contribute high-quality code.
 
 Automated tests run via GitHub Actions. If you're a first-time contributor, all tests (including code checks and unit tests) will require a maintainer to approve. Changes in the `dbt-core` repository trigger integration tests against Postgres. dbt Labs also provides CI environments in which to test changes to other adapters, triggered by PRs in those adapters' repositories, as well as periodic maintenance checks of each adapter in concert with the latest `dbt-core` code changes.
 
-We require signed git commits. See docs [here](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) for setting up code signing.
-
-Once all tests are passing, all comments are resolved, and your PR has been approved, a `dbt-core` maintainer will merge your changes into the active development branch. And that's it! Happy developing :tada:
-
-## Troubleshooting Tips
+Once all tests are passing and your PR has been approved, a `dbt-core` maintainer will merge your changes into the active development branch. And that's it! Happy developing :tada:
 
 Sometimes, the content license agreement auto-check bot doesn't find a user's entry in its roster. If you need to force a rerun, add `@cla-bot check` in a comment on the pull request.

Dockerfile.test

@@ -33,6 +33,12 @@ RUN apt-get update \
     python-is-python3 \
     python-dev-is-python3 \
     python3-pip \
+    python3.8 \
+    python3.8-dev \
+    python3.8-venv \
+    python3.9 \
+    python3.9-dev \
+    python3.9-venv \
     python3.10 \
     python3.10-dev \
     python3.10-venv \
@@ -47,7 +53,7 @@ RUN curl -LO https://github.com/jwilder/dockerize/releases/download/$DOCKERIZE_V
     && tar -C /usr/local/bin -xzvf dockerize-linux-amd64-$DOCKERIZE_VERSION.tar.gz \
     && rm dockerize-linux-amd64-$DOCKERIZE_VERSION.tar.gz
 
-RUN pip3 install -U hatch wheel pre-commit
+RUN pip3 install -U tox wheel six setuptools
 
 # These args are passed in via docker-compose, which reads then from the .env file.
 # On Linux, run `make .env` to create the .env file for the current user.
@@ -62,6 +68,7 @@ RUN if [ ${USER_ID:-0} -ne 0 ] && [ ${GROUP_ID:-0} -ne 0 ]; then \
     useradd -mU -l dbt_test_user; \
     fi
 RUN mkdir /usr/app && chown dbt_test_user /usr/app
+RUN mkdir /home/tox && chown dbt_test_user /home/tox
 
 WORKDIR /usr/app
 VOLUME /usr/app

LICENSE

@@ -1 +0,0 @@
-core/LICENSE

Makefile

@@ -1,95 +1,141 @@
-# ============================================================================
-# DEPRECATED: This Makefile is maintained for backwards compatibility only.
-#
-# dbt-core now uses Hatch for task management and development workflows.
-# Please migrate to using hatch commands directly:
-#
-#   make dev               →  cd core && hatch run setup
-#   make unit              →  cd core && hatch run unit-tests
-#   make test              →  cd core && hatch run test
-#   make integration       →  cd core && hatch run integration-tests
-#   make lint              →  cd core && hatch run lint
-#   make code_quality      →  cd core && hatch run code-quality
-#   make setup-db          →  cd core && hatch run setup-db
-#   make clean             →  cd core && hatch run clean
-#
-# See core/pyproject.toml [tool.hatch.envs.default.scripts] for all available
-# commands and CONTRIBUTING.md for detailed usage instructions.
-#
-# This Makefile will be removed in a future version of dbt-core.
-# ============================================================================
-
 .DEFAULT_GOAL:=help
 
+# Optional flag to run target in a docker container.
+# (example `make test USE_DOCKER=true`)
+ifeq ($(USE_DOCKER),true)
+	DOCKER_CMD := docker-compose run --rm test
+endif
+
+#
+# To override CI_flags, create a file at this repo's root dir named `makefile.test.env`. Fill it
+# with any ENV_VAR overrides required by your test environment, e.g.
+#    DBT_TEST_USER_1=user
+#    LOG_DIR="dir with a space in it"
+#
+# Warn: Restrict each line to one variable only.
+#
+ifeq (./makefile.test.env,$(wildcard ./makefile.test.env))
+	include ./makefile.test.env
+endif
+
+CI_FLAGS =\
+	DBT_TEST_USER_1=$(if $(DBT_TEST_USER_1),$(DBT_TEST_USER_1),dbt_test_user_1)\
+	DBT_TEST_USER_2=$(if $(DBT_TEST_USER_2),$(DBT_TEST_USER_2),dbt_test_user_2)\
+	DBT_TEST_USER_3=$(if $(DBT_TEST_USER_3),$(DBT_TEST_USER_3),dbt_test_user_3)\
+	RUSTFLAGS=$(if $(RUSTFLAGS),$(RUSTFLAGS),"-D warnings")\
+	LOG_DIR=$(if $(LOG_DIR),$(LOG_DIR),./logs)\
+	DBT_LOG_FORMAT=$(if $(DBT_LOG_FORMAT),$(DBT_LOG_FORMAT),json)
+
+
 .PHONY: dev_req
 dev_req: ## Installs dbt-* packages in develop mode along with only development dependencies.
-	@cd core && hatch run dev-req
+	@\
+	pip install -r dev-requirements.txt
+	pip install -r editable-requirements.txt
 
 .PHONY: dev
-dev: ## Installs dbt-* packages in develop mode along with development dependencies and pre-commit.
-	@cd core && hatch run setup
+dev: dev_req ## Installs dbt-* packages in develop mode along with development dependencies and pre-commit.
+	@\
+	pre-commit install
 
-.PHONY: dev-uninstall
-dev-uninstall: ## Uninstall all packages in venv except for build tools
-	@pip freeze | grep -v "^-e" | cut -d "@" -f1 | xargs pip uninstall -y; \
-	pip uninstall -y dbt-core
+.PHONY: proto_types
+proto_types:  ## generates google protobuf python file from types.proto
+	protoc -I=./core/dbt/events --python_out=./core/dbt/events ./core/dbt/events/types.proto
 
 .PHONY: mypy
-mypy: ## Runs mypy against staged changes for static type checking.
-	@cd core && hatch run mypy
+mypy: .env ## Runs mypy against staged changes for static type checking.
+	@\
+	$(DOCKER_CMD) pre-commit run --hook-stage manual mypy-check | grep -v "INFO"
 
 .PHONY: flake8
-flake8: ## Runs flake8 against staged changes to enforce style guide.
-	@cd core && hatch run flake8
+flake8: .env ## Runs flake8 against staged changes to enforce style guide.
+	@\
+	$(DOCKER_CMD) pre-commit run --hook-stage manual flake8-check | grep -v "INFO"
 
 .PHONY: black
-black: ## Runs black against staged changes to enforce style guide.
-	@cd core && hatch run black
+black: .env ## Runs black  against staged changes to enforce style guide.
+	@\
+	$(DOCKER_CMD) pre-commit run --hook-stage manual black-check -v | grep -v "INFO"
 
 .PHONY: lint
-lint: ## Runs flake8 and mypy code checks against staged changes.
-	@cd core && hatch run lint
-
-.PHONY: code_quality
-code_quality: ## Runs all pre-commit hooks against all files.
-	@cd core && hatch run code-quality
+lint: .env ## Runs flake8 and mypy code checks against staged changes.
+	@\
+	$(DOCKER_CMD) pre-commit run flake8-check --hook-stage manual | grep -v "INFO"; \
+	$(DOCKER_CMD) pre-commit run mypy-check --hook-stage manual | grep -v "INFO"
 
 .PHONY: unit
-unit: ## Runs unit tests with py
-	@cd core && hatch run unit-tests
+unit: .env ## Runs unit tests with py
+	@\
+	$(DOCKER_CMD) tox -e py
 
 .PHONY: test
-test: ## Runs unit tests with py and code checks against staged changes.
-	@cd core && hatch run test
+test: .env ## Runs unit tests with py and code checks against staged changes.
+	@\
+	$(DOCKER_CMD) tox -e py; \
+	$(DOCKER_CMD) pre-commit run black-check --hook-stage manual | grep -v "INFO"; \
+	$(DOCKER_CMD) pre-commit run flake8-check --hook-stage manual | grep -v "INFO"; \
+	$(DOCKER_CMD) pre-commit run mypy-check --hook-stage manual | grep -v "INFO"
 
 .PHONY: integration
-integration: ## Runs core integration tests using postgres with py-integration
-	@cd core && hatch run integration-tests
+integration: .env ## Runs postgres integration tests with py-integration
+	@\
+	$(CI_FLAGS) $(DOCKER_CMD) tox -e py-integration -- -nauto
 
 .PHONY: integration-fail-fast
-integration-fail-fast: ## Runs core integration tests using postgres with py-integration in "fail fast" mode.
-	@cd core && hatch run integration-tests-fail-fast
+integration-fail-fast: .env ## Runs postgres integration tests with py-integration in "fail fast" mode.
+	@\
+	$(DOCKER_CMD) tox -e py-integration -- -x -nauto
+
+.PHONY: interop
+interop: clean
+	@\
+	mkdir $(LOG_DIR) && \
+	$(CI_FLAGS) $(DOCKER_CMD) tox -e py-integration -- -nauto && \
+	LOG_DIR=$(LOG_DIR) cargo run --manifest-path test/interop/log_parsing/Cargo.toml
 
 .PHONY: setup-db
 setup-db: ## Setup Postgres database with docker-compose for system testing.
-	@cd core && hatch run setup-db
+	@\
+	docker-compose up -d database && \
+	PGHOST=localhost PGUSER=root PGPASSWORD=password PGDATABASE=postgres bash test/setup_db.sh
+
+# This rule creates a file named .env that is used by docker-compose for passing
+# the USER_ID and GROUP_ID arguments to the Docker image.
+.env: ## Setup step for using using docker-compose with make target.
+	@touch .env
+ifneq ($(OS),Windows_NT)
+ifneq ($(shell uname -s), Darwin)
+	@echo USER_ID=$(shell id -u) > .env
+	@echo GROUP_ID=$(shell id -g) >> .env
+endif
+endif
 
 .PHONY: clean
 clean: ## Resets development environment.
-	@cd core && hatch run clean
+	@echo 'cleaning repo...'
+	@rm -f .coverage
+	@rm -f .coverage.*
+	@rm -rf .eggs/
+	@rm -f .env
+	@rm -rf .tox/
+	@rm -rf build/
+	@rm -rf dbt.egg-info/
+	@rm -f dbt_project.yml
+	@rm -rf dist/
+	@rm -f htmlcov/*.{css,html,js,json,png}
+	@rm -rf logs/
+	@rm -rf target/
+	@find . -type f -name '*.pyc' -delete
+	@find . -type d -name '__pycache__' -depth -delete
+	@echo 'done.'
 
-.PHONY: json_schema
-json_schema: ## Update generated JSON schema using code changes.
-	@cd core && hatch run json-schema
 
 .PHONY: help
 help: ## Show this help message.
-	@echo 'usage: make [target]'
-	@echo
-	@echo 'DEPRECATED: This Makefile is a compatibility shim.'
-	@echo 'Please use "cd core && hatch run <command>" directly.'
+	@echo 'usage: make [target] [USE_DOCKER=true]'
 	@echo
 	@echo 'targets:'
 	@grep -E '^[8+a-zA-Z_-]+:.*?## .*$$' $(MAKEFILE_LIST) | awk 'BEGIN {FS = ":.*?## "}; {printf "\033[36m%-30s\033[0m %s\n", $$1, $$2}'
 	@echo
-	@echo 'For more information, see CONTRIBUTING.md'
+	@echo 'options:'
+	@echo 'use USE_DOCKER=true to run target in a docker container'

README.md

@@ -5,7 +5,6 @@
   <a href="https://github.com/dbt-labs/dbt-core/actions/workflows/main.yml">
     <img src="https://github.com/dbt-labs/dbt-core/actions/workflows/main.yml/badge.svg?event=push" alt="CI Badge"/>
   </a>
-  <a href="https://www.bestpractices.dev/projects/11095"><img src="https://www.bestpractices.dev/projects/11095/badge"></a>
 </p>
 
 **[dbt](https://www.getdbt.com/)** enables data analysts and engineers to transform their data using the same practices that software engineers use to build applications.
@@ -22,7 +21,7 @@ These select statements, or "models", form a dbt project. Models frequently buil
 
 ## Getting started
 
-- [Install dbt Core](https://docs.getdbt.com/docs/get-started/installation) or explore the [dbt Cloud CLI](https://docs.getdbt.com/docs/cloud/cloud-cli-installation), a command-line interface powered by [dbt Cloud](https://docs.getdbt.com/docs/cloud/about-cloud/dbt-cloud-features) that enhances collaboration.
+- [Install dbt](https://docs.getdbt.com/docs/get-started/installation)
 - Read the [introduction](https://docs.getdbt.com/docs/introduction/) and [viewpoint](https://docs.getdbt.com/docs/about/viewpoint/)
 
 ## Join the dbt Community
@@ -32,7 +31,7 @@ These select statements, or "models", form a dbt project. Models frequently buil
 
 ## Reporting bugs and contributing code
 
-- Want to report a bug or request a feature? Let us know and open [an issue](https://github.com/dbt-labs/dbt-core/issues/new/choose)
+- Want to report a bug or request a feature? Let us know on [Slack](http://community.getdbt.com/), or open [an issue](https://github.com/dbt-labs/dbt-core/issues/new)
 - Want to help us build dbt? Check out the [Contributing Guide](https://github.com/dbt-labs/dbt-core/blob/HEAD/CONTRIBUTING.md)
 
 ## Code of Conduct

SECURITY.md

@@ -1 +0,0 @@
-[About dbt Core versions](https://docs.getdbt.com/docs/dbt-versions/core)

codecov.yml

@@ -1,24 +1,13 @@
 ignore:
   - ".github"
   - ".changes"
-
-# Disable all status checks to prevent red X's in CI
-# Coverage data is still uploaded and PR comments are still posted
 coverage:
   status:
-    project: off
-    patch: off
-
-comment:
-  layout: "header, diff, flags, components" # show component info in the PR comment
-
-component_management:
-  individual_components:
-    - component_id: unittests
-      name: "Unit Tests"
-      flag_regexes:
-        - "unit"
-    - component_id: integrationtests
-      name: "Integration Tests"
-      flag_regexes:
-        - "integration"
+    project:
+      default:
+        target: auto
+        threshold: 0.1% # Reduce noise by ignoring rounding errors in coverage drops
+    patch:
+      default:
+        target: auto
+        threshold: 80%

core/MANIFEST.in

@@ -0,0 +1,2 @@
+recursive-include dbt/include *.py *.sql *.yml *.html *.md .gitkeep .gitignore
+include dbt/py.typed

core/README.md

@@ -1,5 +1,5 @@
 <p align="center">
-  <img src="https://raw.githubusercontent.com/dbt-labs/dbt-core/fa1ea14ddfb1d5ae319d5141844910dd53ab2834/docs/images/dbt-core.svg" alt="dbt logo" width="750"/>
+  <img src="https://raw.githubusercontent.com/dbt-labs/dbt-core/fa1ea14ddfb1d5ae319d5141844910dd53ab2834/etc/dbt-core.svg" alt="dbt logo" width="750"/>
 </p>
 <p align="center">
   <a href="https://github.com/dbt-labs/dbt-core/actions/workflows/main.yml">
@@ -9,7 +9,7 @@
 
 **[dbt](https://www.getdbt.com/)** enables data analysts and engineers to transform their data using the same practices that software engineers use to build applications.
 
-![architecture](https://raw.githubusercontent.com/dbt-labs/dbt-core/6c6649f9129d5d108aa3b0526f634cd8f3a9d1ed/docs/images/dbt-arch.png)
+![architecture](https://raw.githubusercontent.com/dbt-labs/dbt-core/6c6649f9129d5d108aa3b0526f634cd8f3a9d1ed/etc/dbt-arch.png)
 
 ## Understanding dbt
 
@@ -17,7 +17,7 @@ Analysts using dbt can transform their data by simply writing select statements,
 
 These select statements, or "models", form a dbt project. Models frequently build on top of one another – dbt makes it easy to [manage relationships](https://docs.getdbt.com/docs/ref) between models, and [visualize these relationships](https://docs.getdbt.com/docs/documentation), as well as assure the quality of your transformations through [testing](https://docs.getdbt.com/docs/testing).
 
-![dbt dag](https://raw.githubusercontent.com/dbt-labs/dbt-core/6c6649f9129d5d108aa3b0526f634cd8f3a9d1ed/docs/images/dbt-dag.png)
+![dbt dag](https://raw.githubusercontent.com/dbt-labs/dbt-core/6c6649f9129d5d108aa3b0526f634cd8f3a9d1ed/etc/dbt-dag.png)
 
 ## Getting started
 

core/dbt/README.md

@@ -22,6 +22,8 @@
 
 ### links.py
 
+### logger.py
+
 ### main.py
 
 ### node_types.py

core/dbt/__version__.py

@@ -1 +0,0 @@
-version = "1.12.0a1"

core/dbt/_pydantic_shim.py

@@ -1,26 +0,0 @@
-# type: ignore
-
-"""Shim to allow support for both Pydantic 1 and Pydantic 2.
-
-dbt-core must support both major versions of Pydantic because dbt-core users might be using an environment with
-either version, and we can't restrict them to one or the other. Here, we essentially import all Pydantic objects
-from version 1 that we use. Throughout the repo, we import these objects from this file instead of from Pydantic
-directly, meaning that we essentially only use Pydantic 1 in dbt-core currently, but without forcing that restriction
-on dbt users. The development environment for this repo should be pinned to Pydantic 1 to ensure devs get appropriate
-type hints.
-"""
-
-from importlib.metadata import version
-
-pydantic_version = version("pydantic")
-# Pydantic uses semantic versioning, i.e. <major>.<minor>.<patch>, and we need to know the major
-pydantic_major = pydantic_version.split(".")[0]
-
-if pydantic_major == "1":
-    from pydantic import BaseSettings  # noqa: F401
-elif pydantic_major == "2":
-    from pydantic.v1 import BaseSettings  # noqa: F401
-else:
-    raise RuntimeError(
-        f"Currently only pydantic 1 and 2 are supported, found pydantic {pydantic_version}"
-    )