@@ -5,46 +5,40 @@ few manual steps.
55
66## Prepare the PR for the new release
77
8- 1 . Find the next version, using semantic versioning, depending on the changes
9- in the changelog
10- 2 . Find and replace the old version with the new version in some files:
11- - meson.build
12- - data/usr/share/gnome/help/diffuse/* /diffuse.xml
13- - data/usr/share/omf/diffuse/diffuse-* .omf
14- - utils/book2manual.xsl
15- - windows-installer/build.py
16- - windows-installer/diffuse.iss
17- - windows-installer/diffuse.new.iss
18- 3 . Update the date for the new release date in these files:
19- - data/usr/share/gnome/help/diffuse/* /diffuse.xml
20- - data/usr/share/omf/diffuse/diffuse-* .omf
21- - utils/book2manual.xsl
22- 4 . Update CHANGELOG.md
23- - Add new line under ` ## Unreleased ` following this syntax: ` ## x.y.z - YYYY-MM-DD `
24- - Copy the content of the changes for this release
25- 5 . Update AppData release notes in data/io.github.mightycreak.Diffuse.appdata.xml.in:
26- - Create a new ` <release> ` tag under ` <releases> ` , fill the ` version ` and
27- ` date ` attributes
28- - Create a new ` <description> ` tag under the new ` <release> ` tag
29- - Add a paragraph (` <p> ` ) to sum the release in one sentence (e.g.
30- highlights, ...)
31- - Paste the changes from the changelog and adapt it to HTML
32- 6 . Create new branch and PR
8+ ### Edit files
9+
10+ 1 . Find the next version, using semantic versioning (e.g. ` 1.2.3 ` ), depending on
11+ the changes in the changelog
12+ 2 . Execute ` ./new_release NEW_VERSION ` (replace ` NEW_VERSION ` with the new version)
13+ 3 . Update the AppData release notes in data/io.github.mightycreak.Diffuse.appdata.xml.in:
14+ - Look for the empty ` <p> ` tag under the new ` <release> ` tag
15+ - Add a paragraph to sum the release in one sentence (e.g. highlights, ...)
16+ - Paste the changes from CHANGELOG.md and adapt it to HTML (see other
17+ releases in the file)
18+
19+ ### Create branch, PR and merge
20+
21+ 1 . Create a new branch (e.g. ` release-1.2.3 ` )
22+ 2 . Create a new PR
23+ 3 . When everything's green: merge the PR
3324
3425## Create new release on GitHub
3526
36- 1 . When everything's green: merge the PR
37- 2 . Create a new release on GitHub's [ new release page] ( https://github.com/MightyCreak/diffuse/releases/new ) :
27+ 1 . Create a new release on GitHub's [ new release page] ( https://github.com/MightyCreak/diffuse/releases/new ) :
3828 - Choose a tag: ` v ` followed with the new version (e.g. ` v1.2.3 ` )
3929 - Release title: the tag (e.g. ` v1.2.3 ` )
4030 - Description:
4131 - For the first paragraph, paste the first paragraph from the release notes
4232 - For the second paragraph, got to [ CHANGELOG.md] ( https://github.com/MightyCreak/diffuse/blob/main/CHANGELOG.md )
4333 and copy the URL anchor to the new release, then add this sentence
44- (adapt the changelog link):
45- > For a more detailed list of changes, see the
46- > [ changelog] ( https://github.com/MightyCreak/diffuse/blob/main/CHANGELOG.md#xyz---yyyy-mm-dd ) .
47- 3 . Publish release
34+ (adapt the changelog link):
35+
36+ ``` text
37+ For a more detailed list of changes, see the
38+ [changelog](https://github.com/MightyCreak/diffuse/blob/main/CHANGELOG.md#xyz---yyyy-mm-dd).
39+ ```
40+
41+ 2. Publish release
4842
4943## Create new release on Flatpak
5044
0 commit comments