Record final quality and Play status
This commit is contained in:
parent
b7a18b0649
commit
72fd99e09a
|
|
@ -33,6 +33,20 @@ results from product limits and unknown production properties.
|
|||
`org.whoneedhelp.mobile` version `0.1.3 (4)`: installer Google Play, signing
|
||||
identity from the protected Play App Signing set, verified production App Link
|
||||
resolving to `MainActivity`, and no browser OAuth callback claimed by the app.
|
||||
- The complete isolated quality and security pipeline passed on the current
|
||||
source after the discovery-rollup concurrency and exact test-evidence release
|
||||
changes. ExUnit reported 498 passing tests. The release, migration, rollback,
|
||||
Compose, Helm, dependency and image-security gates also passed, and the final
|
||||
production image scan reported zero detected vulnerabilities. The systemd
|
||||
unit completed in 3 minutes 13.747 seconds with a 371.4 MiB memory peak and
|
||||
2 MiB swap peak. Exact cleanup left no run-scoped container, network, volume
|
||||
or temporary image.
|
||||
- A read-only Play Console dashboard inspection showed the application still in
|
||||
Draft state with Production inactive. Closed testing showed zero of five setup
|
||||
tasks complete and zero testers opted in. The console requires a published
|
||||
closed-testing release, at least 12 opted-in testers and at least 14 days of
|
||||
qualifying closed testing before the production-access application becomes
|
||||
available.
|
||||
- A read-only Firebase asset inventory for Google Cloud project
|
||||
`who-need-help-staging` showed only the base service-usage, logging, billing and
|
||||
project resources; no staging Firebase Android application or FCM service
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user