github-actions[bot] on gh-pages
deploy: 2b0815f9c4dfd0f744e7816… (compare)
pyro-ppl-feedstock
which depends on pytorch
. Yesterday there was a new release of both packages and pyro-ppl
depends on the latest release of pytorch, which is not yet on conda-forge (it is available on the pytorch
channel). I updated the feedstock but I'm wondering if it will be available, given that the build fails?
pytorch-cpu-feedstock
and I am not eager to become a maintainer there...but I can open a PR
importlib-metadata
actually empty for >3.7
?build_platform: {osx_arm64: osx_64}
from conda-forge.yml
right? Just making sure I don't miss a step since I'm "un-migrating."
rc
branch, adding pyscaffold_rc as the channel target in recipe/conda_build_config.yaml
, making an empty commit and corresponding pull request to request a rerender. Was I on the right track? Should I keep or delete this branch?