Update requirements - Githubissues

ianthomas23 commented 2 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.

Fixes issue #31.

Dependencies were out of sync with github repo, and I have turned off the automerge so changes are checked manually on a new release.

Also added ianthomas23 and thuydotm as maintainers.

conda-forge-linter commented 2 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.

scottyhq commented 2 years ago

thanks for this @ianthomas23 , looks good to me, but I suppose you need a maintainer to approve before merging?

ianthomas23 commented 2 years ago

@scottyhq I do, but I should be able to action this tomorrow.

conda-forge / xarray-spatial-feedstock