From 4461de4ab94ec4727109a3c227e6839c7e512dda Mon Sep 17 00:00:00 2001 From: Thomas Kroll Date: Fri, 13 Nov 2026 16:41:05 +0100 Subject: [PATCH] =?UTF-8?q?release:=200.1.47=20=E2=80=94=20updates=20downl?= =?UTF-8?q?oad=20in=20the=20browser=20instead=20of=20installing=20inside?= =?UTF-8?q?=20NOVA=20(Stable)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Promotes the 0.1.47 cycle (beta1 and beta2) to stable (ADR-0015: its own commit). v0.1.47-beta2 passed its device run on a real Android 9 phone on 2026-11-13; main carries nothing but its release commit since that tag. - app/build.gradle.kts: versionCode 131 -> 132, versionName 0.1.47 - CHANGELOG.md: the 0.1.47-beta1 and 0.1.47-beta2 sections become the single stable 0.1.47 section (ADR-0031 amendment); the empty [Unreleased] heading stays above it - fastlane changelog 132.txt for the store "what's new" - HANDOFF.md: v0.1.47 row, (Latest) marker moved from v0.1.46 Co-Authored-By: Claude Sonnet 5.5 --- CHANGELOG.md | 37 +++++++++---------- HANDOFF.md | 3 +- README.md | 2 +- app/build.gradle.kts | 4 +- .../metadata/android/en-US/changelogs/132.txt | 2 + site/index.html | 2 +- 6 files changed, 25 insertions(+), 25 deletions(-) create mode 100644 fastlane/metadata/android/en-US/changelogs/132.txt diff --git a/CHANGELOG.md b/CHANGELOG.md index ae2bac76..313db90e 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -15,26 +15,9 @@ release version + date and opens a fresh `[Unreleased]`. ## [Unreleased] -## [0.1.47-beta2] - 2026-11-13 +## [0.1.47] - 2026-11-13 -Beta: the second beta of the 0.1.47 cycle. The "Update available" notice on the Overview and the update line in Settings now always show the same latest version, and Settings shows the progress of a check again. Please press "Check now" in Settings and look at whether the notice and Settings agree, then open the update sheet from the notice and check that the "Release page" row, "Later" and "Download" work. As in 0.1.47-beta1, NOVA no longer installs updates itself and "Download" opens the release file in your browser; if you run 0.1.47-beta1, this beta reaches you as a browser download. - -### Fixed - -- **The "Update available" notice and Settings now always show the same - version** — after "Check now" in Settings the Overview notice could still - offer an older release (for example the stable v0.1.46 while Settings offered - the newer beta v0.1.47-beta1), and reopening Settings could show the older - release again. NOVA now keeps one latest-version result that the notice, the - update sheet and Settings all show. It follows the "Include pre-releases" - switch: turning it off never leaves a beta on screen, and turning it on offers - the newest beta again as soon as the check is done. A check that fails keeps - the version found before, and Settings says that the check failed. When - several releases are newer than yours, the newest one is offered (#331). - -## [0.1.47-beta1] - 2026-11-13 - -Beta: NOVA no longer installs updates itself. It still tells you when a new version is out and shows the release notes, but "Download" now opens the release file in your browser. Please open the update sheet that opens from the "Update available" notice and look at the "Download" and "Release page" buttons, and tell us whether the download and the install from the downloaded file work for you. This beta itself is still installed by the old installer of 0.1.46, so Google Play Protect may show its warning one last time; from this version on, the next update arrives as a browser download. +NOVA no longer installs updates itself. It still tells you when a new version is out and shows the release notes, the file size and its SHA-256; "Download" now lets your browser download the release file, and you install it by opening the downloaded file. The "Update available" notice and Settings now always show the same latest version. The 0.1.47 betas confirmed this on a real phone: the download and the install from the downloaded file work, and Google Play Protect offered a scan of the new file and then rated it as seeming safe. Play Protect can still offer to scan every new file before it installs; that is expected. If you update from 0.1.46 or older, that one last update still goes through the old installer and can show the old warning once more. ### Added @@ -50,13 +33,27 @@ Beta: NOVA no longer installs updates itself. It still tells you when a new vers the new APK; you install it by opening the downloaded file, and Android may ask you once to allow your browser or file manager to install apps. NOVA no longer asks for, or holds, the permission to install apps itself. Why: on a real phone - Google Play Protect stopped every current NOVA build with "Harmful app blocked" + Google Play Protect stopped every earlier NOVA build with "Harmful app blocked" (you could only continue through "More details > Install anyway"), while a build of this version without that permission was rated "This app seems safe". Play Protect may still offer to scan each new version before it installs; that is expected. Versions up to 0.1.46 still install updates themselves, so the update to this version can show the warning one last time (#306, #307). +### Fixed + +- **The "Update available" notice and Settings now always show the same + version** — after "Check now" in Settings the Overview notice could still + offer an older release (for example the stable v0.1.46 while Settings offered + a newer pre-release), and reopening Settings could show the older release + again. NOVA now keeps one latest-version result that the notice, the update + sheet and Settings all show. It follows the "Include pre-releases" switch: + turning it off never leaves a beta on screen, and turning it on offers the + newest beta again as soon as the check is done. A check that fails keeps the + version found before, and Settings says that the check failed. Settings shows + the progress of a check again. When several releases are newer than yours, the + newest one is offered (#331). + ## [0.1.46] - 2026-11-13 Adding a self-signed server now asks about its certificate only once, and the Overview shows dashes instead of zeros when it has no data. The 0.1.46 beta confirmed this on a real phone: the trust question appears once, the Overview shows dashes while offline, Uptime is a duration and disk rows have no dangling separator. diff --git a/HANDOFF.md b/HANDOFF.md index faa551d1..9c9eb0a0 100644 --- a/HANDOFF.md +++ b/HANDOFF.md @@ -79,9 +79,10 @@ Native Android client for Unraid NAS servers (Kotlin + Jetpack Compose, Apollo G | v0.1.45-beta1 | pre-release | Beta: live values on the Overview and the container numbers recover by themselves after a dropped or silent connection to the server (new WebSocket transport, own resubscribing loop, 15 s ping); #245 | | **v0.1.45** | **release** | Stable promotion of the 0.1.45 cycle (beta1): live values on the Overview and the container numbers recover by themselves after a dropped or silent connection to the server; #245 | | v0.1.46-beta1 | pre-release | Beta: the certificate trust question is asked only once when a self-signed server is added; the Overview shows dashes instead of zeros when offline, Uptime as a duration, no dangling separator in disk rows; #292, #303, #304, #305 | -| **v0.1.46** | **release** | Stable promotion of the 0.1.46 cycle (beta1): the certificate trust question is asked only once when a self-signed server is added; the Overview shows dashes instead of zeros when offline, Uptime as a duration, no dangling separator in disk rows; #292, #303, #304, #305 **(Latest)** | +| **v0.1.46** | **release** | Stable promotion of the 0.1.46 cycle (beta1): the certificate trust question is asked only once when a self-signed server is added; the Overview shows dashes instead of zeros when offline, Uptime as a duration, no dangling separator in disk rows; #292, #303, #304, #305 | | v0.1.47-beta1 | pre-release | Beta: NOVA no longer installs updates itself; the update check stays and "Download" opens the release file in the browser (ADR-0046); the Google Play Protect notice is documented; #306, #307, #312 | | v0.1.47-beta2 | pre-release | Beta: the update notice on the Overview and the Settings line show the same latest version, Settings shows the progress of a check again; #331, #332 | +| **v0.1.47** | **release** | Stable promotion of the 0.1.47 cycle (beta1, beta2): NOVA no longer installs updates itself, "Download" opens the release file in the browser (ADR-0046); notice and Settings show the same latest version; Play Protect notice documented; #306, #307, #312, #331 **(Latest)** | ## Stack diff --git a/README.md b/README.md index 99b8e261..7839ecdd 100644 --- a/README.md +++ b/README.md @@ -99,7 +99,7 @@ This is Google's rating of the file, not a finding about what NOVA does; Google - **SHA-256 of the file:** the release page lists it next to the APK; compare it with `sha256sum NOVA-v….apk`. - **Signing certificate:** `apksigner verify --print-certs NOVA-v….apk` should show the SHA-256 digest `9f86baa17c1208004d9284e99597f77276c77301b06340b10075c793152b6824`. -**From the next version on**, NOVA no longer installs updates itself and no longer asks for the permission to install apps. **Download** in the update sheet lets your browser download the file; you open it to install. Android will still ask once to scan each new file ("App scan recommended"), because Play Protect does not know it yet; that is expected. We cannot promise that no warning appears, since Google's rating can change. +**From version 0.1.47 on**, NOVA no longer installs updates itself and no longer asks for the permission to install apps. **Download** in the update sheet lets your browser download the file; you open it to install. Android will still ask once to scan each new file ("App scan recommended"), because Play Protect does not know it yet; that is expected. We cannot promise that no warning appears, since Google's rating can change. **F-Droid** is the channel without any such prompt we have seen, but it has stable releases only, gets updates later, and is signed with a different key. Switching between the GitHub APK and F-Droid means uninstalling first, which removes your saved servers and API keys. diff --git a/app/build.gradle.kts b/app/build.gradle.kts index 11f15a0f..bd002953 100644 --- a/app/build.gradle.kts +++ b/app/build.gradle.kts @@ -16,8 +16,8 @@ android { applicationId = "io.github.nofuturekid.nova" minSdk = 26 targetSdk = 36 - versionCode = 131 - versionName = "0.1.47-beta2" + versionCode = 132 + versionName = "0.1.47" vectorDrawables { useSupportLibrary = true } } diff --git a/fastlane/metadata/android/en-US/changelogs/132.txt b/fastlane/metadata/android/en-US/changelogs/132.txt new file mode 100644 index 00000000..1f2431fb --- /dev/null +++ b/fastlane/metadata/android/en-US/changelogs/132.txt @@ -0,0 +1,2 @@ +Nothing changes for the F-Droid version in this release: F-Droid keeps NOVA up to date for you, as before. +The version from GitHub no longer installs its own updates. It shows the new version with its release notes, size and SHA-256, and Download lets your browser download the file. Its update notice and Settings now always show the same latest version. diff --git a/site/index.html b/site/index.html index e1931ee4..b1bb118c 100644 --- a/site/index.html +++ b/site/index.html @@ -323,7 +323,7 @@

Google Play Protect

- From the next version on, NOVA no longer installs + From version 0.1.47 on, NOVA no longer installs updates itself and no longer asks for the permission to install apps. Download in the update sheet lets your browser download the file, and you open it to install. Android will still