Skip to content

Release 0.6 - #36

Merged
nGoline merged 1 commit into
mainfrom
release/0.6
Sep 8, 2026
Merged

nGoline merged 1 commit into
mainfrom
release/0.6

Conversation

@nGoline

@nGoline nGoline commented Sep 8, 2026

Copy link
Copy Markdown
Owner

Version bump and release notes for 0.6. Merge this, then tagging v0.6 publishes it to the closed track.

versionName 0.5 → 0.6
versionCode 7 → 8
applicationId com.ngoline.easygpg — unchanged

What is in it

The rename to Easy PGP. This is the release that carries it to testers. The notes say explicitly that nothing about how the app works has changed and that keys are untouched — an app holding private keys that suddenly renames itself is exactly the kind of thing that makes someone wonder whether they should reinstall, and the answer is no.

The obfuscation marker fix (#33). Obfuscated messages carried the marker twice at each end, which is a more distinctive pattern than a single one and so worked against the point of obfuscating. Messages sent by earlier versions still decrypt, and there is a test pinning that.

Checked before pushing

The release workflow's own guards, run locally:

  • tag v0.6 matches versionName 0.6
  • versionCode 8 > 7 at v0.5
  • whatsnew-en-US is 437 of Play's 500 characters, and check-release-notes.sh passes
  • applicationId still com.ngoline.easygpg

63 tests, lint clean.

After merging

Tag v0.6. The release runs, needs approval at the play-release gate, and lands on the closed track as a draft for you to submit.

Then in Play Console: update the listing name to Easy PGP, and point the privacy policy URL at https://easypgp.ngoline.com/privacy, which is now live.

The release that carries the rename to Easy PGP out to testers, together with
the obfuscation marker fix.

The name is the user-visible change: GPG is GnuPG, and this app implements
OpenPGP with Bouncy Castle, so the old name pointed at software it does not
contain. Nothing about how it works changed and no key material is affected —
the release notes say so, because an app that holds private keys renaming
itself is exactly the kind of thing that makes people wonder whether they
should reinstall.

versionCode 8 because 7 was consumed by the 0.5 upload.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@nGoline
nGoline merged commit 11eef4c into main Sep 8, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant