Update for v5.1.2 - Githubissues

conda-forge / pymc-feedstock

A conda-smithy repository for pymc.

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

1 stars 12 forks source link

Closed michaelosthege closed 1 year ago

michaelosthege commented 1 year ago

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-webservices[bot] commented 1 year 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.

michaelosthege commented 1 year ago

@conda-forge-admin, please rerender

github-actions[bot] commented 1 year ago

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

I tried to rerender for you, but it looks like there was nothing to do.

twiecki commented 1 year ago

Any idea why this wasn't auto-triggered? @maresb

maresb commented 1 year ago

No, I don't understand why this wasn't auto-triggered. I would have expected it, since it's already been several days since the PyPI release.

Looking into recent auto-tick bot-bot logs, I see

2023-03-21 19:23:53,858 INFO     conda_forge_tick.auto_tick ||     node|curr|new|attempts: pymc|5.1.1|5.1.2|6.000000

so it looks like conda-forge is aware of the new version. I'm not sure where to find the logs corresponding to these 6 "attempts".

@ocefpaf, do you have any ideas for how to troubleshoot this?