Skip to content

Release v6.4.0

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 07 Aug 10:24
v6.4.0
65fea7d
This commit was signed with the committer’s verified signature. The key has expired.
greenart7c3 greenart7c3
GPG key ID: 885822EED3A26A6D
Expired
Verified
Learn about vigilant mode.

Amber 6.4.0

  • Redesign the multi-request approval screen with explicit Approve/Deny toggles per request and per group, replacing the select-and-confirm flow, with proper error responses for denied bunker requests
  • Add support for 113 more event kinds with localized labels across all shipped locales, including the Concord kinds, NIP-51 git repository bookmarks and NIP-53 room presence
  • Add light/dark Compose previews for the multi-event approval screens
  • Ignore platform finalizer-watchdog TimeoutExceptions in crash reports
  • Fix a NegativeArraySizeException crash in relay subscriptions by guarding shared maps for concurrent access
  • Translate the new approval strings (approve, confirm, remember my choice for) in all supported locales
  • Update translations

Download it with Zapstore, Obtainium, f-droid or download it directly in the releases page

If you like my work consider making a donation

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:

gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D

Once you have his PGP key you can verify the release (assuming manifest-v6.4.0.txt and manifest-v6.4.0.txt.sig are in the current directory) with:

gpg --verify manifest-v6.4.0.txt.sig manifest-v6.4.0.txt

You should see the following if the verification was successful:

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:

cat manifest-v6.4.0.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.

Older versions

Release notes for previous versions live in docs/changelogs.

Assets 15
Loading