Drops openssl pin

[conda-forge-linter]

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

I've rerendered the recipe as instructed in #9.

Here's a checklist to do before merging.

• Bump the build number if needed.

Fixes #9

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

[jakirkham]

@conda-forge-admin, please re-render

[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/kubo-feedstock/actions/runs/3680503032.

[bollwyvl]

Perhaps the bot will have to come back along, or otherwise be manually migrated?

[h-vetinari]

Perhaps the bot will have to come back along, or otherwise be manually migrated?

This feedstock already contains the openssl 3 migrator. :)

[jakirkham]

Given the migrator was added in PR ( #3 ) and the original bot PR ( #1 ) was closed, am guessing the bot won't come by.

Was a little surprised re-rendering didn't have an effect, but then again the CI matrix already included both openssl versions.

Edit: Sorry for the duplicative post. GitHub didn't show the new comment

[bollwyvl]

Welp, fewer pins good. Let's merge and see what happens.