You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/source/make_a_release.rst
+46-8Lines changed: 46 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -161,43 +161,81 @@ PyPI: Step-by-step
161
161
Conda: Step-by-step
162
162
-------------------
163
163
164
+
.. warning::
165
+
166
+
Publishing on conda requires you to have corresponding package version uploaded on
167
+
`PyPI`_. So you have to do the PypI and Github release before you do the conda release.
168
+
164
169
In order to release a new version on conda-forge, follow the steps below:
165
170
166
-
1. Clone feedstock
171
+
1. Choose the next release version number (that matches with the pypi version that you already published)
172
+
173
+
.. code::
174
+
175
+
$ release=X.Y.Z
176
+
177
+
2. Fork pynwb-feedstock
178
+
179
+
First step is to fork `pynwb-feedstock <https://github.com/conda-forge/pynwb-feedstock>`_ repository.
180
+
This is the recommended `best practice <https://conda-forge.org/docs/conda-forge_gotchas.html#using-a-fork-vs-a-branch-when-updating-a-recipe>`_ by conda.
0 commit comments