conda-build doesn't check if a mismatch between the version in the wheel filename and the version of the conda package

[skupr-anaconda]

Checklist

• I added a descriptive title
• I searched open reports and couldn't find a duplicate

What happened?

conda-build doesn't raise an error if the version of the package is 0.0.0 (the use case: a missing setuptools_scm in the host).

From build logs, see here:

 Source in /private$SRC_DIR has version 0.0.0, which satisfies requirement SQLAlchemy-JSONField==0.0.0 from file:///private$SRC_DIR

but the version must be sqlalchemy-jsonfield 1.0.1.post0.

The problem is not with 0.0.0, but with a mismatch between the version in the wheel filename and the version of the conda package.

I tried to rebuild airflow (it relies on sqlalchemy-jsonfield) and in the test step pip check says you have an incorrect version of the dependency.

If there is one thing we could change, it would be to add a check in conda-build to make sure that the version of the package produced when running pip install . matches the version of the feedstock recipe.

P.S. The issue partially related to #316 but not fully.

Conda Info

No response

Conda Config

No response

Conda list

No response

Additional Context

No response

[ifitchet]

bump

[lorepirri]

bump!

[beeankha]

After discussing with @kenodegard , we came to the agreement that this feature request, while useful and valid, seems to fall more into the "lint check" category vs a hard-coded expectation that all packages must meet. This could be a great opportunity to revisit conda-verify and to either revive that project as it's written or rework it as a conda plugin that can provide customized post-build checks.

[ifitchet]

So we are going to leave this issue open as "encouragement" for those other opportunities?