Skip to content

Commit 9aeefbd

Browse files
committed
Fix: edits from review
1 parent b86354e commit 9aeefbd

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

package-structure-code/publish-python-package-pypi-conda.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -196,5 +196,9 @@ Once your package is on the conda-forge channel, maintaining it is simple.
196196
Every time that you push a new version of your package to PyPI, it will
197197
kick off a continuous integration build that updates your package in the
198198
conda-forge repository. Once that build is complete, you will get a
199-
notification to review the update. You can merge the pull request for
200-
that update once you are happy with it.
199+
notification to review the update.
200+
201+
You can merge the pull request for that update once you are happy with it.
202+
A ready-to-merge PR usually means ensuring that your project's dependencies
203+
(known as runtime requirements) listed in the updated YAML file found in the
204+
pull request match the PyPI metadata of the new release.

0 commit comments

Comments
 (0)