Rebuild for ipopt31413

[regro-cf-autotick-bot]

This PR has been triggered in an effort to update ipopt31413.

Notes and instructions for merging this PR:

1. Please merge the PR only after the tests have passed.
2. Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.

---

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. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/6805420106, please use this URL for debugging.}

[conda-forge-webservices[bot]]

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:

• It looks like the 'papilo' output doesn't have any tests.
• License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

[AntoinePrv]

I see

RuntimeError: SHA256 mismatch: 'be4f978be7f8f97371ddcdac7a60af69a4fea5f975090fe35f1ae4308db692d3' != '820b1f446809e42ddd8beed197facfb01255ba38157b3c55790edb628b16a07b'

@fschloesser @matbesancon do you change the artifacts uploaded to scipopt.org? It's not advisable to do so, please prefer using post releases when fixing non-library related issues. For instance PEP440 style 8.0.4.post1.

[matbesancon]

normally that shouldn't happen.cc @ju-manns

[ju-manns]

@AntoinePrv The tarball download has not changed since the last release. I am not sure, why the hashes are not matching but they must have already mismatched at the end of last release. Should we just update the hash in the feedstock repo?

[AntoinePrv]

@ju-manns sure we can update the hashes. Perhaps if someone could have a quick look at the tarball on the website (sha256=be4f978be7f8f97371ddcdac7a60af69a4fea5f975090fe35f1ae4308db692d3) see that there isn't anything unexpected.

[ju-manns]

I checked the tarball, it looks normal. I am also creating the PR for scip 8.1.0. Should I update the 8.0.4 hash before / meanwhile?

[regro-cf-autotick-bot]

Due to the bot-rerun label I'm closing this PR. I will make another one as appropriate. This was generated by https://github.com/regro/cf-scripts/actions/runs/6935583580