Bump to v2.3.1 - Githubissues

conda-forge / cramjam-feedstock

A conda-smithy repository for cramjam.

BSD 3-Clause "New" or "Revised" License

0 stars 6 forks source link

Bump to v2.3.1 #16

Closed milesgranger closed 3 years ago

milesgranger commented 3 years ago

https://github.com/milesgranger/pyrus-cramjam/releases/tag/v2.3.1

Checklist

[ ] Used a personal 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.

conda-forge-linter commented 3 years ago

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

It appears you are making a pull request from a branch in your feedstock and not a fork. This procedure will generate a separate build for each push to the branch and is thus not allowed. See our documentation for more details.

Please close this pull request and remake it from a fork of this feedstock.

Have a great day!

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.

github-actions[bot] commented 3 years ago

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

I considered the following status checks when analyzing this PR:

linter: passed
drone: failed
travis: passed
azure: passed

Thus the PR was not passing and not merged.