Move upper bounds back to 2.0 (#11024)

* quick test

* add changelog

* Update .changes/unreleased/Under the Hood-20241121-105350.yaml

* pin dev req

* bump protobuf

.changes/unreleased/Under the Hood-20241121-105350.yaml

@@ -0,0 +1,6 @@
+kind: Under the Hood
+body: Pin dbt-common and dbt-adapters with upper bound of 2.0.
+time: 2024-11-21T10:53:50.051757-06:00
+custom:
+  Author: emmyoop
+  Issue: "11024"

core/setup.py

@@ -61,7 +61,7 @@
         # with major versions in each new minor version of dbt-core.
         "click>=8.0.2,<9.0",
         "networkx>=2.3,<4.0",
-        "protobuf>=4.0.0,<5",
+        "protobuf>=5.0,<6.0",
         "requests<3.0.0",  # should match dbt-common
         # ----
         # These packages are major-version-0. Keep upper bounds on upcoming minor versions (which could have breaking changes)
@@ -75,8 +75,8 @@
         "minimal-snowplow-tracker>=0.0.2,<0.1",
         "dbt-semantic-interfaces>=0.5.1,<0.6",
         # Minor versions for these are expected to be backwards-compatible
-        "dbt-common>=1.0.4,<1.11.0",
-        "dbt-adapters>=1.1.1,<1.7.1",
+        "dbt-common>=1.0.4,<2.0",
+        "dbt-adapters>=1.1.1,<2.0",
         # ----
         # Expect compatibility with all new versions of these packages, so lower bounds only.
         "packaging>20.9",

dev-requirements.txt

@@ -1,7 +1,8 @@
-# We hardcode these two dependencies to ensure that we are testing against the correct versions of
-# released code to ensure we don't introduce any breaking changes
-dbt-tests-adapter<=1.10.2
-dbt-postgres<=1.9.0
+# These point to main to catch any regressions before they are released to OSS
+git+https://github.com/dbt-labs/dbt-adapters.git@main
+git+https://github.com/dbt-labs/dbt-adapters.git@main#subdirectory=dbt-tests-adapter
+git+https://github.com/dbt-labs/dbt-common.git@main
+git+https://github.com/dbt-labs/dbt-postgres.git@main
 #
 black>=24.3.0,<25.0
 bumpversion