test commit

.bumpversion.cfg

@@ -0,0 +1,37 @@
+[bumpversion]
+current_version = 1.10.0a1
+parse = (?P<major>[\d]+) # major version number
+	\.(?P<minor>[\d]+) # minor version number
+	\.(?P<patch>[\d]+) # patch version number
+	(?P<prerelease>  # optional pre-release - ex: a1, b2, rc25
+	(?P<prekind>a|b|rc) # pre-release type
+	(?P<num>[\d]+) # pre-release version number
+	)?
+	( # 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]

.changes/0.0.0.md

@@ -3,9 +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)

.changes/unreleased/Dependencies-20241112-163815.yaml

@@ -0,0 +1,6 @@
+kind: Dependencies
+body: Upgrading dbt-semantic-interfaces to 0.8.3 for custom grain support in offset windows
+time: 2024-11-12T16:38:15.351519-05:00
+custom:
+    Author: WilliamDee
+    Issue: None

.changes/unreleased/Dependencies-20241118-001113.yaml

@@ -0,0 +1,6 @@
+kind: "Dependencies"
+body: "Bump codecov/codecov-action from 4 to 5"
+time: 2024-11-18T00:11:13.00000Z
+custom:
+  Author: dependabot[bot]
+  Issue: 11009

.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-20241104-120053.yaml

@@ -0,0 +1,6 @@
+kind: Features
+body: Add new hard_deletes="new_record" mode for snapshots.
+time: 2024-11-04T12:00:53.95191-05:00
+custom:
+  Author: peterallenwebb
+  Issue: "10235"

.changes/unreleased/Features-20241121-125630.yaml

@@ -0,0 +1,6 @@
+kind: Features
+body: Add `batch` context object to model jinja context
+time: 2024-11-21T12:56:30.715473-06:00
+custom:
+  Author: QMalcolm
+  Issue: "11025"

.changes/unreleased/Features-20241206-195308.yaml

@@ -0,0 +1,7 @@
+kind: Features
+body: Ensure pre/post hooks only run on first/last batch respectively for microbatch
+  model batches
+time: 2024-12-06T19:53:08.928793-06:00
+custom:
+  Author: MichelleArk QMalcolm
+  Issue: 11094 11104

.changes/unreleased/Features-20241216-095435.yaml

@@ -0,0 +1,6 @@
+kind: Features
+body: Support "tags" in Saved Queries
+time: 2024-12-16T09:54:35.327675-08:00
+custom:
+    Author: theyostalservice
+    Issue: "11155"

.changes/unreleased/Features-20241217-171631.yaml

@@ -0,0 +1,6 @@
+kind: Features
+body: Calculate source freshness via a SQL query
+time: 2024-12-17T17:16:31.841076-08:00
+custom:
+  Author: ChenyuLInx
+  Issue: "8797"

.changes/unreleased/Features-20241218-170729.yaml

@@ -0,0 +1,6 @@
+kind: Features
+body: Add freshness definition on model for adaptive job
+time: 2024-12-18T17:07:29.55754-08:00
+custom:
+  Author: ChenyuLInx
+  Issue: "11123"

.changes/unreleased/Features-20250106-132829.yaml

@@ -0,0 +1,6 @@
+kind: Features
+body: Meta config for dimensions measures and entities
+time: 2025-01-06T13:28:29.176439-06:00
+custom:
+    Author: DevonFulcher
+    Issue: None

.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-20240822-122132.yaml

@@ -0,0 +1,6 @@
+kind: Fixes
+body: dbt retry does not respect --threads
+time: 2024-08-22T12:21:32.358066+05:30
+custom:
+    Author: donjin-master
+    Issue: "10584"

.changes/unreleased/Fixes-20241025-104339.yaml

@@ -0,0 +1,6 @@
+kind: Fixes
+body: update adapter version messages
+time: 2024-10-25T10:43:39.274723-05:00
+custom:
+  Author: dave-connors-3
+  Issue: "10230"

.changes/unreleased/Fixes-20241121-181739.yaml

@@ -0,0 +1,6 @@
+kind: Fixes
+body: Catch DbtRuntimeError for hooks
+time: 2024-11-21T18:17:39.753235Z
+custom:
+    Author: aranke
+    Issue: "11012"

.changes/unreleased/Fixes-20241128-162936.yaml

@@ -0,0 +1,6 @@
+kind: Fixes
+body: Access DBUG flag more consistently with the rest of the codebase in ManifestLoader
+time: 2024-11-28T16:29:36.236729+01:00
+custom:
+    Author: Threynaud
+    Issue: "11068"

.changes/unreleased/Fixes-20241204-100429.yaml

@@ -0,0 +1,6 @@
+kind: Fixes
+body: Improve the performance characteristics of add_test_edges()
+time: 2024-12-04T10:04:29.096231-05:00
+custom:
+  Author: peterallenwebb
+  Issue: "10950"

.changes/unreleased/Fixes-20241205-145307.yaml

@@ -0,0 +1,6 @@
+kind: Fixes
+body: Implement partial parsing for singular data test configs in yaml files
+time: 2024-12-05T14:53:07.295536-05:00
+custom:
+  Author: gshank
+  Issue: "10801"

.changes/unreleased/Fixes-20241209-113806.yaml

@@ -0,0 +1,6 @@
+kind: Fixes
+body: Fix debug log messages for microbatch batch execution information
+time: 2024-12-09T11:38:06.972743-06:00
+custom:
+  Author: MichelleArk QMalcolm
+  Issue: "11111"

.changes/unreleased/Fixes-20241209-133317.yaml

@@ -0,0 +1,6 @@
+kind: Fixes
+body: Fix running of extra "last" batch when there is only one batch
+time: 2024-12-09T13:33:17.253326-06:00
+custom:
+  Author: QMalcolm
+  Issue: "11112"

.changes/unreleased/Fixes-20241209-150711.yaml

@@ -0,0 +1,6 @@
+kind: Fixes
+body: Fix interpretation of `PartialSuccess` to result in non-zero exit code
+time: 2024-12-09T15:07:11.391313-06:00
+custom:
+  Author: QMalcolm
+  Issue: "11114"

.changes/unreleased/Fixes-20241212-113611.yaml

@@ -0,0 +1,6 @@
+kind: Fixes
+body: Warn about invalid usages of `concurrent_batches` config
+time: 2024-12-12T11:36:11.451962-06:00
+custom:
+  Author: QMalcolm
+  Issue: "11122"

.changes/unreleased/Fixes-20241216-134645.yaml

@@ -0,0 +1,6 @@
+kind: Fixes
+body: Error writing generic test at run time
+time: 2024-12-16T13:46:45.936573-05:00
+custom:
+  Author: gshank
+  Issue: "11110"

.changes/unreleased/Fixes-20241217-154848.yaml

@@ -0,0 +1,6 @@
+kind: Fixes
+body: Run check_modified_contract for state:modified
+time: 2024-12-17T15:48:48.053054-05:00
+custom:
+  Author: gshank
+  Issue: "11034"

.changes/unreleased/Fixes-20241218-112640.yaml

@@ -0,0 +1,6 @@
+kind: Fixes
+body: Fix unrendered_config for tests from dbt_project.yml
+time: 2024-12-18T11:26:40.270022-05:00
+custom:
+  Author: gshank
+  Issue: "11146"

.changes/unreleased/Fixes-20250102-140543.yaml

@@ -0,0 +1,6 @@
+kind: Fixes
+body: Make partial parsing reparse referencing nodes of newly versioned models.
+time: 2025-01-02T14:05:43.629959-05:00
+custom:
+    Author: d-cole
+    Issue: "8872"

.changes/unreleased/Fixes-20250107-173719.yaml

@@ -0,0 +1,6 @@
+kind: Fixes
+body: Ensure warning about microbatch lacking filter inputs is always fired
+time: 2025-01-07T17:37:19.373261-06:00
+custom:
+  Author: QMalcolm
+  Issue: "11159"

.changes/unreleased/Fixes-20250109-123309.yaml

@@ -0,0 +1,6 @@
+kind: Fixes
+body: Fix microbatch dbt list --output json
+time: 2025-01-09T12:33:09.958795+01:00
+custom:
+    Author: internetcoffeephone
+    Issue: 10556 11098

.changes/unreleased/Fixes-20250110-155824.yaml

@@ -0,0 +1,6 @@
+kind: Fixes
+body: Fix for custom fields in generic test config for not_null and unique tests
+time: 2025-01-10T15:58:24.479245-05:00
+custom:
+  Author: gshank
+  Issue: "11208"

.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-20241202-164715.yaml

@@ -0,0 +1,6 @@
+kind: Under the Hood
+body: Create a no-op exposure runner
+time: 2024-12-02T16:47:15.766574Z
+custom:
+    Author: aranke
+    Issue: ' '

.changes/unreleased/Under the Hood-20241205-143144.yaml

@@ -0,0 +1,7 @@
+kind: Under the Hood
+body: Improve selection peformance by optimizing the select_children() and select_parents()
+  functions.
+time: 2024-12-05T14:31:44.584216-05:00
+custom:
+  Author: peterallenwebb
+  Issue: "11099"

.changes/unreleased/Under the Hood-20250107-123955.yaml

@@ -0,0 +1,7 @@
+kind: Under the Hood
+body: Change exception type from DbtInternalException to UndefinedMacroError when
+  macro not found in 'run operation' command
+time: 2025-01-07T12:39:55.234321-05:00
+custom:
+  Author: michelleark
+  Issue: "11192"

.changes/unreleased/Under the Hood-20250107-205838.yaml

@@ -0,0 +1,6 @@
+kind: Under the Hood
+body: Create LogNodeResult event
+time: 2025-01-07T20:58:38.821036Z
+custom:
+    Author: aranke
+    Issue: ' '

.changes/unreleased/Under the Hood-20250110-202057.yaml

@@ -0,0 +1,6 @@
+kind: Under the Hood
+body: Fix error counts for exposures
+time: 2025-01-10T20:20:57.01632Z
+custom:
+    Author: aranke
+    Issue: ' '

.changes/unreleased/Under the Hood-20250117-152215.yaml

@@ -0,0 +1,6 @@
+kind: Under the Hood
+body: Misc fixes for group info in logging
+time: 2025-01-17T15:22:15.497485Z
+custom:
+    Author: aranke
+    Issue: '11218'

.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

@@ -41,26 +41,32 @@ 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 }}

.flake8

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

.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/config.yml

@@ -12,6 +12,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/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

@@ -120,7 +120,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 +188,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/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,10 +1,9 @@
 import os
+from packaging.version import Version, parse
+import requests
 import sys
 from typing import List
 
-import requests
-from packaging.version import Version, parse
-
 
 def main():
     package_name: str = os.environ["INPUT_PACKAGE_NAME"]

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

@@ -0,0 +1,19 @@
+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 apt-get --purge remove postgresql postgresql-*
+        sudo apt update -y
+        sudo apt install gnupg2 wget vim -y
+        sudo sh -c 'echo "deb https://apt.postgresql.org/pub/repos/apt $(lsb_release -cs)-pgdg main" > /etc/apt/sources.list.d/pgdg.list'
+        curl -fsSL https://www.postgresql.org/media/keys/ACCC4CF8.asc|sudo gpg --dearmor -o /etc/apt/trusted.gpg.d/postgresql.gpg
+        sudo apt update -y
+        sudo apt install postgresql-16
+        sudo apt-get -y install postgresql postgresql-contrib
+        sudo systemctl start postgresql
+        sudo systemctl enable postgresql
+        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,26 @@
+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 install postgresql@16
+        brew link postgresql@16 --force
+        brew services start postgresql@16
+        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/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/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

@@ -22,7 +22,7 @@ permissions:
 
 jobs:
   auto-response:
-    runs-on: ${{ vars.UBUNTU_LATEST }}
+    runs-on: ubuntu-latest
     steps:
       - name: Check if current date is within holiday period
         id: date-check

.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.4
         with:
           github_token: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/bot-changelog.yml

@@ -41,14 +41,14 @@ jobs:
         include:
           - label: "dependencies"
             changie_kind: "Dependencies"
-    runs-on: ${{ vars.UBUNTU_LATEST }}
+    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"

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

@@ -4,26 +4,22 @@ 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
+  workflow_dispatch:
 
 jobs:
   check-artifact-changes:
-    runs-on: ${{ vars.UBUNTU_LATEST }}
+    runs-on: ubuntu-latest
     if: ${{ !contains(github.event.pull_request.labels.*.name, 'artifact_minor_upgrade') }}
     steps:
       - name: Checkout code
-        uses: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955 # actions/checkout@v4
+        uses: actions/checkout@v4
         with:
           fetch-depth: 0
 
       - name: Check for changes in core/dbt/artifacts
         # https://github.com/marketplace/actions/paths-changes-filter
-        uses: dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36 # dorny/paths-filter@v3
+        uses: dorny/paths-filter@v3
         id: check_artifact_changes
         with:
           filters: |

.github/workflows/community-label.yml

@@ -7,6 +7,7 @@
 # **when?**
 # When a PR is opened, not in draft or moved from draft to ready for review
 
+
 name: Label community PRs
 
 on:
@@ -28,15 +29,9 @@ jobs:
     # 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]'
-      )
+      (!contains(github.event.pull_request.labels.*.name, 'community') &&
+      (github.event.action == 'opened' && github.event.pull_request.draft == false ) ||
+       github.event.action == 'ready_for_review' )
     uses: dbt-labs/actions/.github/workflows/label-community.yml@main
     with:
         github_team: 'core-group'

.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/main.yml

@@ -20,8 +20,6 @@ on:
       - "*.latest"
       - "releases/*"
   pull_request:
-  merge_group:
-    types: [checks_requested]
   workflow_dispatch:
 
 permissions: read-all
@@ -49,33 +47,27 @@ jobs:
 
     steps:
       - name: Check out the repository
-        uses: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955 # actions/checkout@v4
+        uses: actions/checkout@v4
 
       - name: Set up Python
-        uses: actions/setup-python@e797f83bcb11b83ae66e0230d6156d7c80228e7c # actions/setup-python@v6
+        uses: actions/setup-python@v5
         with:
-          python-version: "3.10"
+          python-version: '3.9'
 
       - 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
+          make dev_req
+          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 +75,17 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        python-version: ["3.10", "3.11", "3.12", "3.13"]
+        python-version: [ "3.9", "3.10", "3.11", "3.12" ]
+
+    env:
+      TOXENV: "unit"
 
     steps:
       - name: Check out the repository
-        uses: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955 # actions/checkout@v4
+        uses: actions/checkout@v4
 
       - name: Set up Python ${{ matrix.python-version }}
-        uses: actions/setup-python@e797f83bcb11b83ae66e0230d6156d7c80228e7c # actions/setup-python@v6
+        uses: actions/setup-python@v5
         with:
           python-version: ${{ matrix.python-version }}
 
@@ -98,15 +93,15 @@ 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
+        uses: nick-fields/retry@v3
         with:
           timeout_minutes: 10
           max_attempts: 3
-          command: cd core && hatch run ci:unit-tests
+          command: tox -e unit
 
       - name: Get current date
         if: always()
@@ -117,11 +112,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@v5
         with:
           token: ${{ secrets.CODECOV_TOKEN }}
           flags: unit
-          fail_ci_if_error: false
 
   integration-metadata:
     name: integration test metadata generation
@@ -146,7 +140,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.9","os":"windows-latest"' '"python-version":"3.9","os":"macos-14"' )
           INCLUDE_GROUPS="["
           for include in ${INCLUDE[@]}; do
               for group in $(seq 1 ${{ env.PYTHON_INTEGRATION_TEST_WORKERS }}); do
@@ -158,102 +152,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 +162,12 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        # already includes split group and runs mac + windows
+        python-version: [ "3.9", "3.10", "3.11", "3.12" ]
+        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 +180,20 @@ jobs:
 
     steps:
       - name: Check out the repository
-        uses: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955 # actions/checkout@v4
+        uses: actions/checkout@v4
 
       - name: Set up Python ${{ matrix.python-version }}
-        uses: actions/setup-python@e797f83bcb11b83ae66e0230d6156d7c80228e7c # actions/setup-python@v6
+        uses: actions/setup-python@v5
         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 +203,17 @@ 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
+        uses: 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 }}
+          command: 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,7 +222,7 @@ 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@v4
         if: always()
         with:
           name: logs_${{ matrix.python-version }}_${{ matrix.os }}_${{ matrix.split-group }}_${{ steps.date.outputs.date }}
@@ -328,20 +230,19 @@ jobs:
 
       - 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@v5
         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 +259,17 @@ jobs:
 
     steps:
       - name: Check out the repository
-        uses: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955 # actions/checkout@v4
+        uses: actions/checkout@v4
 
       - name: Set up Python
-        uses: actions/setup-python@e797f83bcb11b83ae66e0230d6156d7c80228e7c # actions/setup-python@v6
+        uses: actions/setup-python@v5
         with:
-          python-version: "3.10"
+          python-version: '3.9'
 
       - 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 +278,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/*.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@v4
+        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@v4
+        with:
+          ref: main
+
+      # attempts to access a previously cached runner
+      - uses: actions/cache@v4
+        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@v5
+        with:
+          python-version: "3.9"
+
+      - 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@v4
+        with:
+          ref: main
+
+      # this was built in the previous job so it will be there.
+      - name: Fetch Runner
+        uses: actions/cache@v4
+        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@v4
+        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@v4
+        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@v4
+        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@v6
+        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

@@ -31,7 +31,7 @@ env:
 
 jobs:
   aggregate-release-data:
-    runs-on: ${{ vars.UBUNTU_LATEST }}
+    runs-on: ubuntu-latest
 
     outputs:
       version_number: ${{ steps.nightly-release-version.outputs.number }}
@@ -39,14 +39,14 @@ jobs:
 
     steps:
       - name: "Checkout ${{ github.repository }} Branch ${{ env.RELEASE_BRANCH }}"
-        uses: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955 # actions/checkout@v4
+        uses: actions/checkout@v4
         with:
           ref: ${{ env.RELEASE_BRANCH }}
 
       - 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,7 +76,7 @@ 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:

.github/workflows/release.yml

@@ -72,15 +72,12 @@ defaults:
   run:
     shell: bash
 
-env:
-  MIN_HATCH_VERSION: "1.11.0"
-
 jobs:
   job-setup:
     name: Log Inputs
-    runs-on: ${{ vars.UBUNTU_LATEST }}
+    runs-on: ubuntu-latest
     outputs:
-      use_hatch: ${{ steps.use_hatch.outputs.use_hatch }}
+      starting_sha: ${{ steps.set_sha.outputs.starting_sha }}
     steps:
       - name: "[DEBUG] Print Variables"
         run: |
@@ -91,29 +88,19 @@ jobs:
           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/')
+      - name: "Checkout target branch"
+        uses: actions/checkout@v4
+        with:
+          ref: ${{ inputs.target_branch }}
 
-          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"
+      # release-prep.yml really shouldn't take in the sha but since core + all adapters
+      # depend on it now this workaround lets us not input it manually with risk of error.
+      # The changes always get merged into the head so we can't use a specific commit for
+      # releases anyways.
+      - name: "Capture sha"
+        id: set_sha
         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
+          echo "starting_sha=$(git rev-parse HEAD)" >> $GITHUB_OUTPUT
 
   bump-version-generate-changelog:
     name: Bump package version, Generate changelog
@@ -123,13 +110,12 @@ jobs:
     uses: dbt-labs/dbt-release/.github/workflows/release-prep.yml@main
 
     with:
+      sha: ${{ needs.job-setup.outputs.starting_sha }}
       version_number: ${{ inputs.version_number }}
-      hatch_directory: "core"
       target_branch: ${{ inputs.target_branch }}
       env_setup_script_path: "scripts/env-setup.sh"
       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
 
@@ -139,7 +125,7 @@ jobs:
 
     needs: [bump-version-generate-changelog]
 
-    runs-on: ${{ vars.UBUNTU_LATEST }}
+    runs-on: ubuntu-latest
 
     steps:
       - name: Print variables
@@ -157,13 +143,16 @@ jobs:
     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"
+      s3_bucket_name: "core-team-artifacts"
       package_test_command: "dbt --version"
       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
@@ -199,7 +188,7 @@ jobs:
     # 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 }}
+    runs-on: ubuntu-latest
     needs: [pypi-release]
     outputs:
       matrix: ${{ steps.determine-docker-package.outputs.matrix }}

.github/workflows/schema-check.yml

@@ -9,21 +9,15 @@
 # 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' ]
+  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
 
 # no special access is needed
 permissions: read-all
@@ -37,23 +31,22 @@ env:
 jobs:
   checking-schemas:
     name: "Post-merge schema changes required"
-    runs-on: ${{ vars.UBUNTU_LATEST }}
+    runs-on: ubuntu-latest
 
     steps:
       - name: Set up Python
-        uses: actions/setup-python@e797f83bcb11b83ae66e0230d6156d7c80228e7c # actions/setup-python@v6
+        uses: actions/setup-python@v5
         with:
-          python-version: "3.10"
+          python-version: 3.9
 
       - name: Checkout dbt repo
-        uses: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955 # actions/checkout@v4
+        uses: actions/checkout@v4
         with:
-          path: ${{ env.DBT_REPO_DIRECTORY }}
-          ref: ${{ inputs.target_branch }}
+            path: ${{ env.DBT_REPO_DIRECTORY }}
 
       - 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
+        uses: dorny/paths-filter@v3
         id: check_artifact_changes
         with:
           filters: |
@@ -69,19 +62,21 @@ jobs:
 
       - 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@v4
         with:
           repository: dbt-labs/schemas.getdbt.com
-          ref: "main"
+          ref: 'main'
           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
@@ -94,8 +89,8 @@ jobs:
           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 }}
 
       - name: Upload schema diff
-        uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # actions/upload-artifact@v4
+        uses: actions/upload-artifact@v4
         if: ${{ failure() && steps.check_artifact_changes.outputs.artifacts_changed == 'true' }}
         with:
-          name: "schema_changes.txt"
-          path: "${{ env.SCHEMA_DIFF_ARTIFACT }}"
+          name: 'schema_changes.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@v4
         with:
           persist-credentials: false
 
       - name: Setup Python
-        uses: actions/setup-python@e797f83bcb11b83ae66e0230d6156d7c80228e7c # actions/setup-python@v6
+        uses: actions/setup-python@v5
         with:
-          python-version: "3.10"
+          python-version: "3.9"
 
       - 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,11 @@ 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
+        uses: nick-fields/retry@v3
         with:
           timeout_minutes: 30
           max_attempts: 3
-          command: cd core && hatch run ci:integration-tests -- -nauto
+          command: 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,34 @@ 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.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-14'
+          - '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 +51,7 @@ defaults:
 
 jobs:
   debug:
-    runs-on: ${{ vars.UBUNTU_LATEST }}
+    runs-on: ubuntu-latest
     steps:
       - name: "[DEBUG] Output Inputs"
         run: |
@@ -81,37 +82,26 @@ jobs:
 
     steps:
       - name: "Checkout code"
-        uses: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955 # actions/checkout@v4
+        uses: actions/checkout@v4
         with:
           ref: ${{ inputs.branch }}
 
       - name: "Setup Python"
-        uses: actions/setup-python@e797f83bcb11b83ae66e0230d6156d7c80228e7c # actions/setup-python@v6
+        uses: actions/setup-python@v5
         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-14'
+        uses: ./.github/actions/setup-postgres-macos
 
       - name: "Set up postgres (windows)"
         if: inputs.os == 'windows-latest'
@@ -160,5 +150,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

.gitignore

@@ -15,7 +15,6 @@ build/
 !core/dbt/docs/build
 develop-eggs/
 dist/
-dist-*/
 downloads/
 eggs/
 .eggs/
@@ -96,7 +95,6 @@ target/
 # pycharm
 .idea/
 venv/
-.venv*/
 
 # AWS credentials
 .aws/

.pre-commit-config.yaml

@@ -1,91 +1,71 @@
 # 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/common/events/types_pb2.py|core/dbt/events/core_types_pb2.py|core/dbt/adapters/events/adapter_types_pb2.py)
 
-# Force all unspecified python hooks to run python 3.10
+# Force all unspecified python hooks to run python 3.9
 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
+    exclude: schemas/dbt/manifest/
+  - id: trailing-whitespace
+    exclude_types:
+      - "markdown"
+  - id: check-case-conflict
+- repo: https://github.com/pycqa/isort
+  # rev must match what's in dev-requirements.txt
+  rev: 5.13.2
+  hooks:
+    - id: isort
+- repo: https://github.com/psf/black
+  # rev must match what's in dev-requirements.txt
+  rev: 24.3.0
+  hooks:
+  - id: black
+  - id: black
+    alias: black-check
+    stages: [manual]
+    args:
+    - "--check"
+    - "--diff"
+- repo: https://github.com/pycqa/flake8
+  # rev must match what's in dev-requirements.txt
+  rev: 4.0.1
+  hooks:
+  - id: flake8
+  - id: flake8
+    alias: flake8-check
+    stages: [manual]
+- repo: https://github.com/pre-commit/mirrors-mypy
+  # rev must match what's in dev-requirements.txt
+  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,10 +14,14 @@ 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.
@@ -27,7 +32,7 @@ This is the docs website code. It comes from the dbt-docs repository, and is gen
 ## 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) 
+Note: dbt-postgres used to exist in dbt-core but is now in [its own repo](https://github.com/dbt-labs/dbt-postgres) 
 
 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 +40,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

@@ -9,8 +9,7 @@
 
 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)

CONTRIBUTING.md

@@ -2,39 +2,21 @@
 
 `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)
+9. [Troubleshooting Tips](#troubleshooting-tips)
 
 ## 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).
 
@@ -73,22 +55,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 +95,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,78 +128,45 @@ 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
@@ -289,9 +224,7 @@ Code can be merged into the current development branch `main` by opening a pull
 
 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:
+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:
 
 ## Troubleshooting Tips
 

Dockerfile.test

@@ -33,6 +33,9 @@ RUN apt-get update \
     python-is-python3 \
     python-dev-is-python3 \
     python3-pip \
+    python3.9 \
+    python3.9-dev \
+    python3.9-venv \
     python3.10 \
     python3.10-dev \
     python3.10-venv \
@@ -47,7 +50,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 +65,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