Open FabriceSalvaire opened 4 years ago
conda-forge is designed to package a library and test that the package functions correctly, i.e. nothing has gone wrong in the packaging process. It isn't intended to serve as the primary CI for the project's development.
However, there is a bot that will automatically create a PR to this repo any time a new git tag is pushed to the PySpice repo. (For example, see #3, which was automatically opened.) To test your repo, you could just push a tag like v1.4.3beta0
, which (I think) will eventually trigger an automatic PR to this feedstock repo.
Otherwise, it is assumed that each project has its own CI setup, and that conda-forge infrastructure is only used during the packaging process, after each new release.
FWIW, it is possible to re-purpose conda-forge's CI scripts for a personal repo. The instructions are given here: https://conda-forge.org/docs/user/ci-skeleton.html
I have never tried this myself.
on PyPI, I think the answer is we cannot, i.e. yank a release and bump ...