Fix setting the release flag in build

jakelishman commented 3 years ago

The first version of this release didn't set the new CI_QUTIP_RELEASE environment variable during the build process, and consequently the distributed version of QuTiP reported its version as 4.6.0+nogit. pip versions were correct since those wheels were built on GitHub Actions the correct way.

See qutip/qutip#1465

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

conda-forge-linter commented 3 years ago

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

jakelishman commented 3 years ago

Rerendered locally, but since this is ~an hour after the last build, naturally there have been no modifications to conda-forge-pinning and nothing actually changed.

conda-forge / qutip-feedstock

Fix setting the release flag in build #65