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) <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5
parent
44bf7ceb3d
commit
050fe84d6a
@@ -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
|
||||
|
||||
Reference in New Issue
Block a user