Bump version to 6.2.3 and update changelog

AGENTS.md

@@ -20,6 +20,15 @@ Amber is a single-module Android app (`:app`, package `com.greenart7c3.nostrsign
 
 Required order when pushing: `ktlintCheck` → `test` → build (mirrored by the hooks, but run them directly; do not rely on hooks).
 
+## Releases / version bumps
+
+When asked to "bump the version" / cut a release, do **all** of the following in a single change — never omit the verification block:
+
+1. Bump `versionCode` (+1) and `versionName` (new `X.Y.Z`) in `app/build.gradle.kts` (`defaultConfig`). These are the only places the version lives.
+2. Prepend a new `## Amber X.Y.Z` block at the top of `CHANGELOG.md`, summarizing the non-merge commits since the previous `vX.Y.Z` tag (`git log vX.Y.Z..HEAD --no-merges`), grouped as user-facing bullets. End the block with the standard "Download it with …" line (update the `releases/tag/vX.Y.Z` URL) and the "If you like my work …" donation line.
+3. **Always include the `## Verifying the release` block immediately after the donation line** (before the next `## Amber` heading). Copy it verbatim from the previous release entry and only change the `manifest-vX.Y.Z.txt` / `manifest-vX.Y.Z.txt.sig` filenames to the new version. Do **not** change the `gpg --recv-keys` key id, the `gpg: Signature made Fri 13 Sep 2024 …` block, or the surrounding prose — those are key-specific, not release-specific. This block must be part of the version-bump commit, not a follow-up.
+4. Do not commit unless explicitly asked (per the global rule). Do not edit `build.sh` — it takes the version as an argument.
+
 ## Product flavors (dimension `version`)
 
 | Flavor | Notes |

CHANGELOG.md

@@ -1,3 +1,53 @@
+## Amber 6.2.3
+
+- Add a configurable profile fetch interval setting with never/always options
+- Show a profile picture in the account switch bottom sheet
+- Scope profile subscriptions by the current account, driven by composables
+- Add error handling to bunker permission parsing
+- Trim the shipped languages to the curated set of locales
+- Set the benchmark build app name to "Amber Benchmark"
+- Fix a StrictMode DiskReadViolation in Coil onSuccess logging
+- Load the account off the main thread to fix a StrictMode keystore violation
+- Read account name and picture off the main thread in the account switch sheet
+- Avoid eager KeyPair() on the main thread in the login/signup screens
+- Fix the settings section header contrast in the light theme
+- Fix an unescaped apostrophe in the Turkish profile fetch interval string
+- Update translations
+
+Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.2.3)
+
+If you like my work consider making a [donation](https://greenart7c3.com)
+
+## Verifying the release
+
+In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:
+
+``` bash
+gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
+```
+
+Once you have his PGP key you can verify the release (assuming `manifest-v6.2.3.txt` and `manifest-v6.2.3.txt.sig` are in the current directory) with:
+
+``` bash
+gpg --verify manifest-v6.2.3.txt.sig manifest-v6.2.3.txt
+```
+
+You should see the following if the verification was successful:
+
+``` bash
+gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
+gpg:                using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
+gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
+```
+
+That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:
+
+``` bash
+cat manifest-v6.2.3.txt
+```
+
+One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.
+
 ## Amber 6.2.2
 
 - Show native app icons and NIP-46 client metadata on the request screens and app list

app/build.gradle.kts

@@ -15,8 +15,8 @@ android {
     defaultConfig {
         applicationId = "com.greenart7c3.nostrsigner"
         minSdk = 26
-        versionCode = 195
-        versionName = "6.2.2"
+        versionCode = 196
+        versionName = "6.2.3"
 
         buildConfigField("boolean", "IS_FDROID_BUILD", "false")