Bumped up version to trigger build on Windows

[jezdez]

Checklist

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

[conda-forge-linter]

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.

[jezdez]

@conda-forge-admin, please rerender

[github-actions]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/conda-feedstock/actions/runs/3601833942.

[mbargull]

We can just restart the jobs with the failing uploads on Azure.

[jezdez]

We can just restart the jobs with the failing uploads on Azure.

Gotcha, wasn't sure what the right approach was, thanks for letting me know.

[mbargull]

I just restarted the builds.
It's kind of odd how/why that happened, though.
It is again a problem that the temporary directory wasn't accessible. In the past we encountered this for feedstocks that used Go builds. Apparently it's not just a Go-related thing 🤷 🤔

[jakirkham]

Ah ok. Still working my way through notifications. Saw this issue as well, but it looks like this happened with the restarted builds. Trying to restart again.