docs: 1.16.0 배포와 검증 결과 기록
Some checks failed
ci / 정본·보안·린트·타입·테스트 (push) Failing after 18s
ci / 워크스페이스 빌드 검증 (push) Has been skipped
ci / 모바일 린트·타입·Jest (push) Successful in 40s
ci / Supabase Edge Functions + Cloudflare Worker (push) Successful in 23s
ci / .NET API 서버 테스트 (push) Successful in 14s
deploy-site / deploy (push) Successful in 40s
Some checks failed
ci / 정본·보안·린트·타입·테스트 (push) Failing after 18s
ci / 워크스페이스 빌드 검증 (push) Has been skipped
ci / 모바일 린트·타입·Jest (push) Successful in 40s
ci / Supabase Edge Functions + Cloudflare Worker (push) Successful in 23s
ci / .NET API 서버 테스트 (push) Successful in 14s
deploy-site / deploy (push) Successful in 40s
This commit is contained in:
parent
7f9ec45868
commit
5ec063c744
9 changed files with 26 additions and 15 deletions
|
|
@ -40,6 +40,8 @@ Evidence root: `test-results/recovery-2026-11-01/` (already ignored by the repos
|
|||
| Android artifact | Build Tools 37 verifier and its self-test PASS. Current `.3` APK: `com.d3ro.voice`, `1.15.4-e2e.20261101.3`, code `2026110103`, 147158575 bytes, SHA-256 `937d2a0b3fb6b810516f07e91dd97ffe99d34c5885a72f21805a51e8a408027f`; installed Fold6 identity matches. `android-artifact.json`. |
|
||||
| Fold6 current runtime | Existing app brought forward without clearing data. Meetings → Recording opens `meeting-editor-modal` with title/attendees/language/template fields; rendered screenshot and UI hierarchy retained. No meeting was saved and no inference was requested. A later list-restoration assertion failed because the expected list was no longer visible; it is not counted as a navigation PASS. |
|
||||
| Isolated Android first-run auth | Created a new empty API 34 AVD `D3RORecovery20261101`, explicitly targeted `emulator-5580`, installed exact `.3` APK. Initial run failed while Android's **System UI isn't responding** dialog covered the app; XML and log retained. After choosing Wait, actual onboarding rendered; canonical fresh-auth flow **PASS, 37 s**, including persistent Login after restart. This is emulator evidence, not a new Fold6 first-run pass. Maestro also logged local heartbeat file-lock errors; those were not treated as an app diagnosis. |
|
||||
| Isolated Android signup | Same exact `.3` APK, canonical fresh-signup flow **PASS, 50 s**, including tutorial, SignUp destination, permission boundaries and Login after restart. `emulator-signup.junit.xml` and screenshots retained. Test emulator stopped by its verified AVD identity; its files remain preserved. |
|
||||
| Shipped native artifacts | Rebuilt sidecar executable **startup/health PASS** (`pid=46908`, separate port 9499), then only that child was stopped. Packaged `uiohook-napi/prebuilds/win32-x64` native binding loads and exports `start/stop/keyTap`; hooks were not started. Initial diagnostic used an incorrect export name `startHook`; that probe failure is retained separately. Real release checkpoint **12/12 artifact hashes PASS** against tag commit. |
|
||||
|
||||
## Open gates and preserved failures
|
||||
|
||||
|
|
@ -50,4 +52,11 @@ Evidence root: `test-results/recovery-2026-11-01/` (already ignored by the repos
|
|||
|
||||
## Release and final state
|
||||
|
||||
Release execution, public hashes/signature, final commit/remotes and the final clean-state check are appended after the release finishes. Until then this section is pending, not deployment proof.
|
||||
- Recovery commit: `b3519e5da72cfda3146bd00ce846caab53a0b5f7` (54 reviewed files). Release commit and immutable annotated tag `v1.16.0`: `7f9ec458682ec32cd070824968540186c6f56e51`. Both authored by **Yun Chan <yunchan@twentyoz.kr>**.
|
||||
- `node --env-file-if-exists=.env scripts/ci/release-desktop.mjs minor --with-runtime` **exit 0**. Version/metadata/typecheck gates, native packaging, rebuilt sidecar health, runtime/portable publication, canonical+mirror push and signed installer publication completed. Full transcript: `release-1.16.0.log`.
|
||||
- Windows installer: `D3RO-Voice-Setup-1.16.0-x64.exe`, **95,985,380 bytes**, SHA-256 **`e9596ee25fe03e4ebf34c526198d2f44ddc7cdd90ec354eb304216687486a7c0`**. This is a Windows release, not a macOS/mobile release or evidence that the already-running personal installation upgraded.
|
||||
- Public signed feed: [immutable 1.16.0 manifest](https://git.chanpaca.net/api/packages/yunchan/generic/d3ro-voice/1.16.0/latest.yml), [latest alias](https://git.chanpaca.net/api/packages/yunchan/generic/d3ro-voice/latest/latest.yml). Publisher verified the public Ed25519 signature. [Runtime index](https://git.chanpaca.net/api/packages/yunchan/generic/d3ro-voice/runtime-latest/runtime.json) and [portable index](https://git.chanpaca.net/api/packages/yunchan/generic/d3ro-voice/portable-latest/portable.json) are 1.16.0. Generated Scoop metadata is copied to the tracked bucket only after publication.
|
||||
- Independent public verification **PASS: seven binary assets / 437,066,850 bytes**, signed immutable/latest manifests, runtime and portable aliases. Initial checks passed installer, all three runtime parts and portable 7z. ZIP `.001` exceeded a 120 s download deadline; its separate full curl transfer measured about 230 KB/s and was stopped with bytes retained. The server confirmed HTTP 206 ranges. A 180 s range attempt also timed out; completed ranges and partial bytes were preserved and the remaining byte ranges resumed. Both ZIP SHA-256 values then matched, including the combined `.001` ranges. `public-release-verification.json` composes these checks; the original timeout logs remain alongside `public-zip-verification.json` and `public-zip-resume.log`. No failed whole-command run is relabeled as a pass.
|
||||
- Existing personal services remained healthy: STT `/health` ready with CUDA `large-v3-turbo`; Ollama `/api/version` 0.40.5. See `service-health-final.json`. The actual local 8.498 s transcription result and the new executable's separate startup proof are distinct checks.
|
||||
- Forgejo Actions inventory endpoint returned HTTP 404; no separate hosted-CI success is claimed. The local release and public artifact checks are the deployment evidence.
|
||||
- Final evidence/Scoop documentation is committed after the release tag. Final branch/remotes/clean state are recorded in `test-results/recovery-2026-11-01/final-git-state.json`; that later documentation commit does not alter the immutable release tag. The only intentionally unmerged remote branch is the April 13 historical UI branch described above.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue