Is this your first time submitting an issue in dbt-athena?
[X] I have searched the existing issues, and I could not find an existing issue for this feature
Describe your request/question
We want dbt-athena-community to be the same package as dbt-athena for every version, down to the patch/pre-release/etc. There is no easy way to enforce this since we can't point one package to another package's version file (seemingly a hatch or setuptools limitation). And we certainly can't have calculated versions in the build dependencies in dbt-athena-community. The next best thing is to add a pre-commit check that ensures the versions are all set to the same thing. This includes:
We are comfortable bumping the version manually for now as this overlap is a temporary solution for providing backwards compatibility as dbt-athena-community users migrate to dbt-athena.
Is this your first time submitting an issue in dbt-athena?
Describe your request/question
We want
dbt-athena-communityto be the same package asdbt-athenafor every version, down to the patch/pre-release/etc. There is no easy way to enforce this since we can't point one package to another package's version file (seemingly ahatchorsetuptoolslimitation). And we certainly can't have calculated versions in the build dependencies indbt-athena-community. The next best thing is to add apre-commitcheck that ensures the versions are all set to the same thing. This includes:dbt-athena/dbt/athena/__version__.py::versiondbt-athena-community/pyproject.toml::project.versiondbt-athena-community/pyproject.toml::project.dependencies.dbt-athenaWe are comfortable bumping the version manually for now as this overlap is a temporary solution for providing backwards compatibility as
dbt-athena-communityusers migrate todbt-athena.Anything else?
No response