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
- Summarize only the most important changes from the draft release [kept on GitHub](https://github.com/TeamNewPipe/NewPipe/releases) (it contains all merged pull requests)
80
81
- Make sure the file size is **at most 500 bytes**, in order to **fit [F-Droid's changelog size limit](https://f-droid.org/en/docs/All_About_Descriptions_Graphics_and_Screenshots/#fastlane-structure) (!)**
82
+
- Tip: removing the newline at the end of the file saves 1 byte ;-)
81
83
- Commit the file on the `dev` branch (try to stick to the provided commit message template)
-`git commit -m "Add changelog for vX.X.X (NEW_VERSION_CODE)"`
@@ -99,6 +101,7 @@ Now there should be two new commits (the Weblate and changelog ones) on your loc
99
101
## Creating the release branch
100
102
101
103
- Create a new branch starting from `dev`, named `release-X.X.X`, and switch to it
104
+
-`git checkout dev`
102
105
-`git checkout -b release-X.X.X`
103
106
- Edit the [`app/build.gradle`](https://github.com/TeamNewPipe/NewPipe/blob/dev/app/build.gradle) file to update the extractor
104
107
- Set the NewPipeExtractor dependency version to a suitable one (usually [the last commit in the NewPipeExtractor repo](https://github.com/TeamNewPipe/NewPipeExtractor/commits/dev))
@@ -122,7 +125,7 @@ Now there should be two new commits (the Weblate and changelog ones) on your loc
122
125
- The PR title should be "Release vX.X.X (NEW_VERSION_CODE)"
123
126
- Remove the entire PR template, and instead put these two lines in the description (the `ISSUE_NUMBER` will be replaced later):
124
127
```md
125
-
Do not report regressions here, but rather in the corresponding issue: #ISSUE_NUMBER
128
+
Do **not** report regressions here, but rather in the corresponding issue: #ISSUE_NUMBER
126
129
The changelog is also there.
127
130
```
128
131
- Once you have created the PR, note down its number (from now on called `PR_NUMBER`)
@@ -135,15 +138,26 @@ The changelog is also there.
135
138
- Click [here](https://github.com/TeamNewPipe/NewPipe/issues/new) to open one without a template
136
139
- The issue title should be "Release vX.X.X (please TEST!)"
137
140
- The issue should have some sections, in the same order as provided below, with `##` before titles
138
-
- The `## Testing for regressions` section should contain the following lines; more information about how to obtain the APK are given at [Testing APKs](testing-apks)
141
+
- The `## Testing for regressions` section should contain the following lines; more information about how to obtain the APK are given at [Testing APKs](#testing-apks)
139
142
```md
140
143
Debug APK (built by our CI in #PR_NUMBER): ...
141
-
Please report **only regressions** (i.e. new issues) here, not issues that were already present in the previous release!
144
+
Please report **only regressions** (i.e. new issues) here, not issues that were already present in previous releases!
142
145
```
143
146
- An optional `## TODO` section should contain a list of things that still need to be done before releasing, for example regressions that need to be fixed, or a reminder to merge the Weblate changelogs before releasing (use `- [ ]` to create checkbox lists)
144
-
- The `## NewPipeExtractor version` should contain a link to the NewPipeExtractor release this new NewPipe version will ship with (i.e. the one set in [Creating the release branch](#creating-the-release-branch))
145
-
- Copy the draft Markdown changelog [kept on GitHub](https://github.com/TeamNewPipe/NewPipe/releases) (you finalized it earlier in [Create a changelog](#create-a-changelog)) to the clipboard and paste it under the `## App changelog` section
147
+
- The `## NewPipeExtractor version` section should contain a link to the NewPipeExtractor release this new NewPipe version will ship with (i.e. the one set in [Creating the release branch](#creating-the-release-branch)); choose one of these lines as a template
148
+
```md
149
+
This version of NewPipe will ship with [NewPipeExtractor version NPE_VERSION](https://github.com/TeamNewPipe/NewPipeExtractor/releases/tag/NPE_VERSION)
150
+
This version of NewPipe will ship with [NewPipeExtractor commit FIRST_7_DIGITS_OF_NPE_COMMIT](https://github.com/TeamNewPipe/NewPipeExtractor/commit/NPE_COMMIT)
151
+
```
152
+
- Create the `App changelog` section using the template below. Copy the draft Markdown changelog [kept on GitHub](https://github.com/TeamNewPipe/NewPipe/releases) (you finalized it earlier in [Create a changelog](#create-a-changelog)) to the clipboard and paste it where specified below (make sure to leave a newline above, otherwise Markdown breaks):
- Once you have created the issue, pin it using the "Pin issue" button on the right
160
+
- Update the `ISSUE_NUMBER` in the pull request description
147
161
-*Check out [#8230](https://github.com/TeamNewPipe/NewPipe/issues/8230) for reference*
148
162
149
163
## Testing APKs
@@ -159,9 +173,11 @@ Sometimes it might be needed to also provide a release APK. In this case follow
159
173
160
174
- Make sure you are on the `release-X.X.X` branch
161
175
- Build the **release** APK yourself in Android Studio and sign it with your keys
176
+
-*Temporarily* edit the `app/build.gradle` file and add `System.properties.put("packageSuffix", "vX_X_X")` at the top of the `android -> buildTypes -> release` block, which ensures that the application has a different package name than the official one
177
+
- Build and sign an APK via "Build -> Generate Signed Bundle / APK..."
162
178
- Make sure it installs correctly on your device
163
179
- Use this naming scheme: `NewPipe_vX.X.X_RC1_release.apk`
164
-
- Add a line to the `## Testing for regressions` section, of this form: `Debug APK (built and signed by @YOUR_GITHUB_USERNAME): ...`
180
+
- Add a line to the `## Testing for regressions` section, of this form: `Release APK (built and signed by @YOUR_GITHUB_USERNAME): ...`
0 commit comments