release v4.7.6 - Githubissues

conda-forge / qutip-feedstock

A conda-smithy repository for qutip.

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

0 stars 14 forks source link

release v4.7.6 #93

Closed ajgpitch closed 6 months ago

ajgpitch commented 6 months ago

Checklist

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

Increase countstat stability. Exclude scipy 1.13 from in the requirements

conda-forge-webservices[bot] commented 6 months 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.

hodgestar commented 6 months ago

Since we now need to maintain both 5.0.X and 4.7.X, I think we need to have a branch for each -- see, for example, https://github.com/conda-forge/django-feedstock/branches. Probably 5.0.X should stay as the main branch and a new branch, 4.7.X should be created for 4.7 releases.

ajgpitch commented 6 months ago

@hodgestar Yes, that makes sense. It wasn't feeling right. Should I not merge this then?

hodgestar commented 6 months ago

@hodgestar Yes, that makes sense. It wasn't feeling right. Should I not merge this then?

Perhaps the easiest is to create a new branch from main called 4.7.X and then close this PR and open a new PR from this branch into the new one.