xopen v0.8.4

[rhpvorderman]

Checklist

• [ ] Used a 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 code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• [ ] Ensured the license file is being packaged.

Retry from autotick.

[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.

[rhpvorderman]

Strange. I can merge it on my own PC into master. Why does the merging not work all of a sudden?

[marcelm]

I think we are not supposed to use branches on the main feedstock repo for PRs. It seems you just published version 0.8.4 to anaconda.org already ...

Oh well, no harm done ... Should we just merge this now? Or will that trigger another deploy?

[rhpvorderman]

I think we are not supposed to use branches on the main feedstock repo for PRs. It seems you just published version 0.8.4 to anaconda.org already ...

Whoops! Did not realize that. Sorry!

Oh well, no harm done ... Should we just merge this now? Or will that trigger another deploy?

I think it won't build unless the build number has changed right? I will merge so master is correct. If anything breaks I will make a new PR with an increased build number.

[rhpvorderman]

I just realized that it might have autobuild because I had the keyword release in the branch name.

[marcelm]

I think "release" in the branch name does not matter if I interpret the docs correctly.

[rhpvorderman]

Thanks. Next time I will open a separate branch on my own fork.