raise/test minimum protobuf version by trial-and-error, more imports

bollwyvl commented 3 years ago

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.

Notes:

partially addresses #1
- likely needs a https://github.com/conda-forge/admin-requests for 0
adds a more useful import (top-level was empty)
bumps and tests against the minimum claimed version of protobuf
- determined via trial-and-error
- hopefully this approach will work in the future for determining the required version, as the setup.py data appears to be inaccurate (at least w/r/t the upstream tarball)
adds some more URLs

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.

bollwyvl commented 3 years ago

@conda-forge-admin please rerender

bollwyvl commented 3 years ago

@conda-forge-admin please rerender

github-actions[bot] commented 3 years ago

Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you, but it looks like there was nothing to do.

bollwyvl commented 3 years ago

I think this is about as robust as i can make it at this point... will merge and proceed with the admin request...

conda-forge / grpcio-health-checking-feedstock