v0.7.05 build 365
2026-08-03 v0.7.05 build 365
- CHG: updated SHAs.
- CHG: updated
android\app\build.gradle.ktstobase.archivesName.set("cfg_pia_wg") // this sets the name of the .AAB output file. - CHG: removed postscript from in-app LICENSE display.
- DOC: updated CHANGELOG format.
- DOC: added how to upgrade dependency versions in BUILDING.md "4.1.2. When to regenerate lockfiles"
- REL: updated dependencies:
dartssh22.22.5 &jni1.0.3 - REL: tagged for release.
2026-08-03 v0.7.04 build 364
- REL: renamed app from cfg_pia_wireguard -> cfg_pia_wg (must use underscores, cannot use hyphens)
- update
pubspec.yaml-> name: cfg_pia_wg - search and replace in .dart files -> "import 'package:cfg_pia_wg/"
- update
android/settings.gradle.kts-> rootProject.name = "cfg_pia_wg" - check tests run and app compiles
- update
.github\workflows\release.yml-> mv build/app/outputs/bundle/release/cfg_pia_wg-release.aab - update
scripts\build.ps1-
$TARGET_APK = "build/cfg_pia_wg-v$ {VERSION}_release.apk" -
$APK_RELEASE = "build/cfg_pia_wg-v$ {VERSION}_release.apk" - $AAB_RELEASE = "build/app/outputs/bundle/release/cfg_pia_wg-release.aab"
-
- update
scripts\build.sh- TARGET_APK="build/cfg_pia_wg-v${VERSION}_release.apk"
- APK_RELEASE="build/cfg_pia_wg-v${VERSION}_release.apk"
- AAB_RELEASE="build/app/outputs/bundle/release/cfg_pia_wg-release.aab"
- save and exit VS Code, check tests run and app compiles with .\scripts\build all
- check app builds on GitHub dev branch
- update
- FIX: can't paste into password fields, and can't "q"uit debug running in any screen showing password fields, also causing screen
D/EGL_emulation(24795): app_time_stats: avg=499.58ms min=498.77ms max=500.27ms count=3count to increment; revert build 363 changes tolib\widgets\common_fields.dartandlib\watchdog_dialog.dart. Tested and now operating correctly: can "q"uit debugger, no incrementing count and can paste.
2026-08-03 v0.7.03 build 363
- FIX: Disabled ability to copy a password when the field is revealed. (Didn't check could paste, which is now broken when testing build 364, reverted changes in build 364)
2026-08-03 v0.7.02 build 362
- DOC: Update readme with the new name of the command-line tool -
cfg-pia-wg. - FIX: Updated
pubspec.yaml- app name was showing incorrectly in launchers, updated from "Configure PIA WireGuard" to "cfg-pia-wg". - DOC: Spellcheck ARCHITECTURE, CHANGELOG, and README.md.
- DOC: Replace ipv4.icanhazip.com in architecture.md, now using ping targets.
- DOC: Add to README.md that screenshots are disabled.
- DOC: Update security.md hotlink for reporting an issue, fix US spellings, remove Inactivity session self-destruct.
- CHG: Router IP address, 192.168.1.1 by default (matches SVG examples) and retained when entered.
- DOC: Add copies of all Claude plans to repo.
- GUI: Display the quad 9 default DNS addresses next to the Cloudflare ones in generate.
- GUI: Suggested DNS address help text is truncated.
- BLD: Added a warning to understand what the build optimisation script does before use.
- DOC: clarified README.md reason for
JFFSpartition enablement for storage of the watchdog script and settings between reboots. - REL: Drop debug and release builds from Actions workflows, update README.md to account for this
- DOC: added TOC and section numbering to TESTING.md
- ARC: per TESTING.md, the architecture only deploys
/jffs/scripts/services-startand/jffs/scripts/watchdog_wgcN.shto NVRAM. Other files are written to volatile storage:/tmp/watchdog_wgcN.log,/tmp/watchdog_last_ping_success_wgcN, and/tmp/watchdog_backoff_wgcN. This reduces NVRAM write wear. The watchdog log is not persistent and is rotated at midnight to reduce volatile storage. - DOC: added note to test that VPN is active after a firmware update (JFFS may be recreated by flashing process).
- GUI: enlarge WireGuard Configuration prompt for PIA credentials so that you can see the example DNS addresses; display is truncated.
- DOC: Update privacy.html to note that URLs in About screen go to locations on the Internet.
- INF: log message "kernel: jffs2: warning: (27325) jffs2_sum_write_data: Summary too big (-32 data, -877 pad) in eraseblock at 00280000", only seen once. No activity from app or script around that time. Checked deployed artifact sizes: 8,346 bytes (watchdog script), 205 bytes (services-start), 2,719 bytes (pia_ca.rsa.4096.crt), 181 bytes (cron entries) -> 11,451 bytes total used by app (typical). Web searches show that this can be ignored: created during NVRAM housekeeping. Likely occurred as a result of extensive app testing.
- ARC: check all non-critical data written to tmp, not JFFS