File tree Expand file tree Collapse file tree 1 file changed +11
-7
lines changed
Expand file tree Collapse file tree 1 file changed +11
-7
lines changed Original file line number Diff line number Diff line change @@ -211,13 +211,17 @@ When a new version of allms is ready to be released, do the following operations
211211 2 . ` git push origin <NEW-VERSION> `
212212
2132133 . ** Publish package to PyPI** :
214- 1 . Go to _ Actions_ → _ Manual Publish To PyPI _ ;
215- 2 . Select "master" as branch and click _ Run workflow_ ;
214+ 1 . Go to _ Actions_ → _ Release _ ;
215+ 2 . Select _ tags _ → ` <NEW_VERSION> ` and click _ Run workflow_ ;
216216 3 . If successful, you will find the package under # TODO: open-source.
217217
2182184 . ** Make a GitHub release** :
219- 1 . Go to _ Releases_ → _ Draft a new release_ ;
220- 2 . Select the recently created tag in _ Choose a tag_ window;
221- 3 . Copy/paste all the content present in the CHANGELOG under the version you are about to release;
222- 4 . Upload ` allms-<NEW-VERSION>.whl ` and ` allms-<NEW-VERSION>.tar.gz ` as assets;
223- 5 . Click ` Publish release ` .
219+ 1 . Build package locally with command:
220+ ``` bash
221+ make build-package
222+ ```
223+ This will create two files in the ` dist` directory: ` allms-< NEW-VERSION> .whl` and ` allms-< NEW-VERSION> .tar.gz` ;
224+ 2. Go to _Releases_ → _Draft a new release_;
225+ 3. Select the recently created tag in _Choose a tag_ window;
226+ 4. Upload ` allms-< NEW-VERSION> .whl` and ` allms-< NEW-VERSION> .tar.gz` as assets;
227+ 5. Click ` Publish release` .
You can’t perform that action at this time.
0 commit comments