After a PyPi release update the conda-forge package. For this do the following on a local checkout of the package feedstock
- create a new branch
- conda smithy rerender
- update the sha256 in the
meta.yaml
- update version number
Afterwards upload the new branch to your own fork of the feedstock and generate a PR. Once all tests pass merge the PR and the package will be published.
Don't. We don't have the man power to update all the dependencies we need in the channel ourselves. Relying on conda-forge is more reliant.