-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
conda-forge package #315
Comments
I am not sure how this will play out if ChiantiPy is updated |
Conda forge will automatically pick up each new release that gets uploaded to PyPI and open a PR against the chiantipy recipe repo. Releasing the new version on conda forge then is just a matter of merging that PR (provided the tests pass). E.g. the aiapy recipe repo: https://github.com/conda-forge/aiapy-feedstock |
Yes, this is an example of how the bot works: conda-forge/chiantipy-feedstock#2. Human intervention is just required when you need to make changes to the package recipe (for example: adding new dependencies). People with write access to the feedstock repository are listed at the bottom of the recipe. Currently, I'm the only maintainer but that's not ideal. I can add more maintainers to the recipe. I created the package because we want to release |
I enabled the automerge bot, so there's no need to do anything except for breaking changes (adding new dependencies, for example). |
Recently, I uploaded
ChiantiPy
to theconda-forge
channel: https://anaconda.org/conda-forge/chiantipy.I think I should have to ask you before doing it, but it's already done. Currently versions available are 0.11.0 (latest) and 0.8.4 (required by
carsus
).The text was updated successfully, but these errors were encountered: