Update release candidate branch to 3.2.0rc0

conda-forge / iris-feedstock

A conda-smithy repository for iris.

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

0 stars 17 forks source link

Update release candidate branch to 3.2.0rc0 #78

Closed lbdreyer closed 2 years ago

lbdreyer commented 2 years ago

To create this I took a copy of the recipe from master, updated it to v3.2.0rc0.

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] 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.

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.

lbdreyer commented 2 years ago

@conda-forge-admin, please rerender

bjlittle commented 2 years ago

@conda-grayskull show requirements

conda-grayskull commented 2 years ago

Working on your request...

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.

I do have some suggestions for making it better though...

For recipe:

Jinja2 variable references are suggested to take a {{<one space><variable name><one space>}} form. See lines [17].

lbdreyer commented 2 years ago

Thanks for the review @bjlittle ! I believe I have addressed your comments now.

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.

lbdreyer commented 2 years ago

@conda-forge-admin, please rerender

lbdreyer commented 2 years ago

@bjlittle This should now be good to go. I finally figured out why it was failing. It turns out I had the build script line "python -m pip install ..." in the wrong place. Do you mind having another look at this?

bjlittle commented 2 years ago

@lbdreyer Awesome, thanks :partying_face: