From 050fe84d6a6981f0dafdd2eee665e106c3b55280 Mon Sep 17 00:00:00 2001 From: TCFDONMEZ Date: Thu, 8 Oct 2026 14:43:49 +0300 Subject: [PATCH] Release 2.2.37 with cloud sync configured The published APK carries the Vercel origin and the write-only ingest token. Verified against the signed artifact: the origin and token are present, and no MongoDB URI, host or password appears anywhere in the dex. Co-Authored-By: Claude Opus 5 (1M context) --- CHANGELOG.md | 15 +++++++++++++++ FatihsMG4-unstable-2.2.37.apk.sha256 | 1 + app/build.gradle | 4 ++-- 3 files changed, 18 insertions(+), 2 deletions(-) create mode 100644 FatihsMG4-unstable-2.2.37.apk.sha256 diff --git a/CHANGELOG.md b/CHANGELOG.md index 39cd547..cb02362 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,20 @@ # Changelog +## 2.2.37 + +### Added + +- Cloud sync is configured. The build carries the API origin and a write-only ingest + token, so daily consumption and completed DC charging sessions reach MongoDB, and + whatever queued up while offline is uploaded once connectivity returns. + +### Changed + +- The consumption API moved from a standalone Express service to a Next.js app on Vercel, + which also serves a dashboard for reading the history back. The token in this APK opens + the write endpoints only — reading needs a password the APK does not contain, and the + MongoDB URI remains server-side and has never been in a build. + ## 2.2.36 ### Changed diff --git a/FatihsMG4-unstable-2.2.37.apk.sha256 b/FatihsMG4-unstable-2.2.37.apk.sha256 new file mode 100644 index 0000000..305d5c5 --- /dev/null +++ b/FatihsMG4-unstable-2.2.37.apk.sha256 @@ -0,0 +1 @@ +2d9fbd26a5afa6b0aaf21519204f825b32b45dd7e7165918c0685669cbd9b9bd FatihsMG4-unstable-2.2.37.apk diff --git a/app/build.gradle b/app/build.gradle index c5bdef7..441ece2 100644 --- a/app/build.gradle +++ b/app/build.gradle @@ -34,8 +34,8 @@ android { applicationId "com.evsuite.abrp" minSdk 27 targetSdk 36 - versionCode 53 - versionName "2.2.36" + versionCode 54 + versionName "2.2.37" // MongoDB credentials never ship in the APK. The app only talks to the small // authenticated API in server/, which owns the database connection.