Closed jGaboardi closed 4 years ago
i think the answer to 1 is yes, i'd expect the condabot to still keep pinging recipe maintiners each time a new pypi release gets pushed. 2 would be pretty interesting though. That would remove the need to double check the dependency changes each time (which can be a real pain)
p.s., the only stuff i'm tinkering with now is very geosnap-specific, so we should probably start copying over the base logic to the submod template
It would be super neat to have that as a jobs.<job_id>.needs
following the PyPI publishing in the same workflow.
should we close this given the new auto-merge functionality in conda-forge?
Yup!
@knaaptime Awesome job the last few days getting the PyPI upload GHA working. I am curious how this will affect the re-up of
conda-forge
versioning. Specifically, (1) will theconda-forge
bot continue making automated PRs if the feedstock version doesn't match the PyPI version; and (2) will (could?) a new GHA be created to accomplish this.