[Feature] Constraints file for key dependencies in the dbt ecosystem of packages

[colin-rogers-dbt]

Is this your first time submitting a feature request?

• I have read the expectations for open source contributors
• I have searched the existing issues, and I could not find an existing issue for this feature
• I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature

All dbt-* components (i.e. core, plugins, adapters, dbt-extractor etc.) exist in the same python environment, sharing the same dependencies. This means that in order for someone to install and run these in the same virtual environment we need to be able to have compatible dependencies. It also means the developers of dbt components should choose dependency ranges that are going to be compatible with the broader ecosystem without knowing what those ranges should be ahead of time.

To solve this we could maintain a common package dependencies constraints file which we suggest package maintainers adhere to (or at least test compatibility against). Some examples of packages that would be helpful to include: Pydantic, mashumaro, json-schema, agate, numpy.
Note these aren't necessarily direct dependencies of dbt-core, dbt-common or dbt-adapters but common dependencies used by adapters and plugins.

Describe alternatives you've considered

No response

Who will this benefit?

No response

Are you interested in contributing this feature?

No response

Anything else?

No response

[github-actions]

This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days.

[github-actions]

Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment to notify the maintainers.