Repository navigation
release: 0.1.47 — updates download in the browser instead of installing inside NOVA (Stable) - #334
Merged
Merged
Conversation
…ng inside NOVA (Stable) 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 <noreply@anthropic.com>
nofuturekid
force-pushed
the
release/v0.1.47
branch
from
November 13, 2026 15:52
efb9eae to
4461de4
Compare
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this release contains
Stable promotion of the 0.1.47 cycle (v0.1.47-beta1 and v0.1.47-beta2), ADR-0015: its own version-bump commit.
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## [0.1.47] - 2026-11-13section (ADR-0031 amendment); an empty[Unreleased]stays on top.fastlane/.../changelogs/132.txtfor the store "what's new";HANDOFF.md: v0.1.47 row, (Latest) marker moved from v0.1.46.Since the tag v0.1.47-beta2, main carries nothing but that beta's release commit (
git diff --stat v0.1.47-beta2 origin/mainis empty), so the app code is the one that was tested.Device evidence
v0.1.47-beta2 (versionCode 131) passed its device run on a real Android 9 phone on 2026-11-13, checked by an independent review:
The release text does not promise that Play Protect never asks: the scan prompt remains for every new file, and users of 0.1.46 and older still update one last time through the old installer and may see the old warning once more.
Landing
This lands by a fast-forward push of the head commit to main by the coordinator, then the release dry run and the tag on that same commit (R-MERGE, R-RELEASE). It is not merged through GitHub.
🤖 Generated with Claude Code