Followup to PR #12. Embarrassingly I must have somehow got lost in the various Azure builds, and didn't notice that I used an invalid version string for conda recipes. This PR updates the version string for the nightly builds to satisfy both conda and setuptools requirements:
I went with X.X.X.devYYYYMMDD, but I'm open to other options that satisfy the requirements. Note that X.X.X corresponds to the latest version in the conda recipe. It's possible to instead use the current version string in the upstream Git repo, but I'm trying to avoid prematurely optimizing this nightly build pipeline.
Followup to PR #12. Embarrassingly I must have somehow got lost in the various Azure builds, and didn't notice that I used an invalid version string for conda recipes. This PR updates the version string for the nightly builds to satisfy both conda and setuptools requirements:
I went with X.X.X.devYYYYMMDD, but I'm open to other options that satisfy the requirements. Note that X.X.X corresponds to the latest version in the conda recipe. It's possible to instead use the current version string in the upstream Git repo, but I'm trying to avoid prematurely optimizing this nightly build pipeline.
Here are the relevant Azure logs from my fork:
1.2.1.dev20230417