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: release_checklist.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,8 +4,9 @@
4
4
* don't write release notes for unfinished or non-documented features(except in special cases)
5
5
* Update version.nim with the new version, following [calendar versioning](https://calver.org/): `YY.OM.<build>`:
6
6
e.g. the first build for a month can be `25.03.1`, the next one `25.03.2` etc
7
+
* Update Info.plist with the new version following the same format.
7
8
* Open a pull request with the changes
8
-
* Check if CI builds and upload correctly the artifacts. Test the artifacts: if needed, one can
9
+
* Check if CI builds and upload the artifacts correctly. Test the artifacts: if needed, one can
9
10
fix/change things and push again
10
11
* When it's all tested or ready, you can merge the pull request which will automatically push a tag and release
11
12
* Once the release is ready, activate the option to make a GitHub discussion for the release, when publishing and publish!
@@ -22,7 +23,7 @@
22
23
- Update the version field
23
24
- Commit the file. GitHub actions will automatically build and deploy the package to the AUR
24
25
- Updating gentoo packages:
25
-
- Navigate to the ebuild which can be found as `gentoo/dev-debug/codetracer/codetracer-<version>.ebuild`
26
+
- Navigate to the ebuild which can be found as `gentoo/dev-debug/codetracer-bin/codetracer-bin-<version>.ebuild`
26
27
- To update the package simply rename the file so that the version portion of it matches the new version
27
28
- GitHub actions in [metacraft-desktop-packages](https://github.com/metacraft-labs/metacraft-desktop-packages) will push an update of the ebuild to [metacraft-overlay](https://github.com/metacraft-labs/metacraft-overlay)
28
29
- In [metacraft-overlay](https://github.com/metacraft-labs/metacraft-overlay), GitHub actions will start building the package. The first CI build will be updating the `Manifest` file found in the same directory as the ebuild
0 commit comments