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: .github/workflows/README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ To be completed.
20
20
## Publish To PyPi
21
21
22
22
This workflow publishes the `micropython-europi` and `micropython-europi-contrib` distributions to the public PyPi
23
-
repositories. These distributions are described by the [`software/firmware/setup.py`](/software/firmware/setup.py) and [`software/setup.py`](/software/setup.py) files respectively.
23
+
repositories. These distributions are described by the [`software/firmware/setup.py`](/software/firmware/setup.py) and [`software/setup.py`](/software/setup.py) files respectively.
24
24
25
25
### test.pypi.org
26
26
@@ -31,14 +31,14 @@ exercise the release process. Most of these will fail silently as a specific ver
31
31
32
32
Pushes to the main [pypi.org](https://pypi.org/project/micropython-europi/#history) occur with each new tag.
33
33
34
-
###Release process
34
+
## Release process
35
35
36
36
1. Decide which version number to release.
37
37
1. Update [`software/firmware/version.py`](/software/firmware/version.py) with the new version number.
38
38
1. Commit and push to `main`.
39
39
1. Verify that the new release was pushed to [test.pypi.org](https://test.pypi.org/project/micropython-europi/#history). If it was not, look for errors associated with the commit on the [actions tab](https://github.com/Allen-Synthesis/EuroPi/actions). Commit new changes until a successful release is created.
40
-
1. Tag the release locally using `git tag -a <version_number> -m 'message'`, for example `git tag -a 0.0.1 -m 'release v0.0.1'`
41
-
1. Push the tag to the remote repository with `git push origin <version_number>`, for example `git push origin 0.0.1`.
40
+
1. Tag the release locally using `git tag -a v<version_number> -m 'message'`, for example `git tag -a v0.0.1 -m 'release v0.0.1'`
41
+
1. Push the tag to the remote repository with `git push origin <version_number>`, for example `git push origin v0.0.1`.
42
42
1. Verify that the new release was pushed to [pypi.org](https://pypi.org/project/micropython-europi/#history) and is installable.
43
43
1. Update the generated [GitHub Release](https://github.com/Allen-Synthesis/EuroPi/releases) with a description of the changes and publish.
0 commit comments