[bot-automerge] proj.4 v8.1.0

[regro-cf-autotick-bot]

It is very likely that the current package version for this feedstock is out of date. Notes for merging this PR:

1. Feel free to push to the bot's branch to update this PR if needed.
2. The bot will almost always only open one PR per version. Checklist before merging this PR:
   • [ ] Dependencies have been updated if changed: see upstream
   • [ ] Tests have passed
   • [ ] Updated license if changed and license_file is packaged

Note that the bot will stop issuing PRs if more than 3 Version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.

NEW: If you want these PRs to be merged automatically, make an issue with code>@conda-forge-admin,</codeplease add bot automerge in the title and merge the resulting PR. This command will add our new bot automerge feature to your feedstock!

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase code>@<space/conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. If you would like a local version of this bot, you might consider using rever. Rever is a tool for automating software releases and forms the backbone of the bot's conda-forge PRing capability. Rever is both conda (conda install -c conda-forge rever) and pip (pip install re-ver) installable. Finally, feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/autotick-bot/actions/runs/988311615, please use this URL for debugging}

Dependency Analysis

Please note that this analysis is highly experimental. The aim here is to make maintenance easier by inspecting the package's dependencies. Importantly this analysis does not support optional dependencies, please double check those before making changes. If you do not want hinting of this kind ever please add bot: inspection: false to your conda-forge.yml. If you encounter issues with this feature please ping the bot team conda-forge/bot.

Analysis of the source code shows no discrepancy between the library's imports and the package's stated requirements in the meta.yaml.

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

[github-actions[bot]]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• drone: passed
• travis: passed
• azure: passed

Thus the PR was passing and merged! Have a great day!

[xylar]

@ocefpaf, do we actually want the auto-merge bot on here? It seems like it got activated automatically somehow and we probably don't want it. We wanted to use #106 for this update instead.

[ocefpaf]

@ocefpaf, do we actually want the auto-merge bot on here? It seems like it got activated automatically somehow and we probably don't want it. We wanted to use #106 for this update instead.

I'll send a PR to remove it. It is harmless in most cases but proj is a key package and we probably don't want it automerging all the time.

[xylar]

It is harmless in most cases but proj is a key package and we probably don't want it automerging all the time.

It seems like it can be harmful in quite a few circumstances. For example, if a dependency changed but not in a way that breaks any tests, this would be harmful. The main way that would happen is if the version constraints are too loose but the latest version happens to work. This will create a build that erroneously gets picked by the solver when it shouldn't, even if you create a later build with correct version constraints.

proj doesn't have any version constraints like that, so maybe it would have been fine in cases other than this one where we wanted to change the build approach at a clean break.