root/geo
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(release): update desktop-client version to 0.1.11 and document July 12 release audit
Desktop Client Build / Resolve Build Metadata (push) Successful in 26s
Details
Desktop Client Build / Build Desktop Client (push) Successful in 25m23s
Details
Desktop Client Build / Publish Client Artifacts to NAS (push) Failing after 50s
Details

Browse Source
This commit is contained in:
liangxu
2026-07-12 17:01:23 +08:00
parent e68db14802
commit 75c9be5eb3
4 changed files with 55 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
progress.deploy-39.md
+15
View File
@@ -41,3 +41,18 @@
- Completed final verification: 11 Deployments and 6 StatefulSets Ready, migration clean, six HTTP checks at 200, release Pod restarts zero, unexpected log candidates zero, stale zero-replica ReplicaSets zero, nine release image refs present, and no old geo-rankly refs remain.
- Cleared the two naturally repopulated `geo:cache:*` keys as the last runtime action and immediately verified cache count zero while 270 refresh and 25 desktop keys remained intact.
- Repacked the source snapshot without macOS extended attributes and verified both incoming and rollback checksums. Stored rollback instructions and the old prompt merge patch under the timestamped release directory.
## 2026-07-12
- Started an incremental deployment audit from clean HEAD `e68db14` against the stored July 10 production snapshot.
- Verified and extracted the prior source snapshot. The first comparison command did not run because a zsh special variable shadowed PATH; the retry will use a safe loop variable.
- Confirmed the prior deployed application tree equals `04c89c6`. The July 12 deployable server delta is frontend-only; no SQL migration or backend runtime rollout is required.
- Release tests passed: full Go suite, admin-web Vitest (3/3), and desktop-client Vitest (207/207 across 30 files).
- Admin-web production build, desktop-client typecheck, and desktop-client build all passed. A concurrently running signed desktop packaging process is being left untouched and is outside the k3s rollout.
- Built the frontend directly to a linux/amd64 Docker archive tagged `workspace-e68db14-20260712150344`; tag, architecture, AIAccounts chunk, and SHA checks passed. A zsh diagnostic-variable error interrupted only the final source-commit printout.
- Confirmed the source archive emits the expected commit, but pipefail treated gzip's expected early-reader SIGPIPE as an error; final verification will use a temporary uncompressed tar instead of that pipeline.
- Finished release artifact verification: frontend Docker archive and Git source archive both pass SHA-256, platform is linux/amd64, the expected AIAccounts chunk is present, and all frontend build inputs stayed unchanged during the build.
- Captured an 18 MB frontend-only rollback set on 39, uploaded the 100 MB incoming release, and independently verified both archive checksums on the target.
- Imported the release frontend image. The new Pod initially could not create its sandbox because the node's pause image had been deleted and Docker Hub timed out; restored a checksummed linux/amd64 `rancher/mirrored-pause:3.6`, after which the Pod became Ready with zero restarts and the old Pod terminated.
- Verified the new frontend: root, `/ai-accounts`, and the 14.9 KB AIAccounts chunk all return 200; frontend log candidates and restarts are zero, tenant readiness is 200, and schema remains `20260710183000|false`.
- Completed July 12 cleanup and final verification: 11 Deployments and 6 StatefulSets Ready, one stale frontend ReplicaSet removed, no unreferenced geo-rankly image refs found, pause image retained, and release/rollback checksums pass.
- Cleared exactly two `geo:cache:*` keys as the last application-affecting step; cache remains zero while 265 refresh and 42 desktop runtime keys were preserved. Desktop-client publishing was not touched after the user's instruction.