Repository navigation
deploy: release qualified questionnaire, forum, cases and GLM-5.3 changes - #194
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 24d8fe52ae
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| x-runtime: &runtime | ||
| image: accel.way2api.fun/ghcr.io/lingxi-org/lingxiloop-server:c132e9f20b3df1873792618ed3f3bfe8be2be00e | ||
| image: accel.way2api.fun/ghcr.io/lingxi-org/lingxiloop-server:b76c4cc00f545ddbca27bced6628e1ed191e6777 |
There was a problem hiding this comment.
Back up migrations 0044–0045 before rolling out the image
On the normal rollout from the currently pinned c132e9f image, production is at migration 0043, while this b76c4cc image adds 0044 and 0045. However, trigger-komodo-rollout.mjs calls prepareForumRollout(), which returns immediately for every schema version >=40 before reaching its backup/restore block, so the subsequent App A deployment can run both new migrations without a fresh snapshot-consistent backup. Update the preflight gate to back up and verify the current database before advancing to schema 45.
Useful? React with 👍 / 👎.
|
Release gate update: final source CI/image run 39243667498 completed successfully. The published This PR's deployment-contract CI 39244666912 also passed. Its integration/publish/deploy jobs were correctly outside PR deployment-only scope and are not counted as executed tests. The source run above supplies integration and image qualification. Backup/isolated restore, current readiness, migration compatibility, zero active leases and the existing ordered rollout path have been verified. Proceeding with the authorized normal merge and rollout; production completion will be reported only after the terminal update and actual-service checks. |
|
Final release receipt: workflow39245993469 succeeded and Komodo reached Issues183/184/186/187 are closed with individual evidence comments. Historical153/155/157/161 remain open with their specific incomplete acceptance boundaries; PR185 and the forum scope record121 were also updated. The independent final-image Web+Worker idle soak started2026-10-19 11:47:53UTC and has durable remote running receipts. It is not yet a24h pass. An external watch stays silent while evidence is fresh/running, reports terminal/failure/stale or blocked evidence, then pauses itself to avoid repeated notices. This idle scope cannot replace production load/provider/Worker–SPA fault acceptance or certify a subsequent release. This release session is now handing off; it will not initiate another production rollout. |
Released the reviewed questionnaire recovery, forum layout, organization case library, provider handling and exact GLM-5.3-Flash changes from PRs #185, #188, #192, #191, #190 and #189. Web/API and Worker image pins now use product source
b76c4cc00f545ddbca27bced6628e1ed191e6777with official@lyyzka/lingxios@3.5.3.Production release 39245993469 completed successfully on merge
b2013edc7685d86e131c5c7f011078fdf2d3e008. The signed Komodo procedure reachedComplete / success=true. Post-release checks verified actual image identities, Web/API and Worker readiness, runtime 3.5.3/schema12/protocol11, product migrations 44/45, exactzai-org/GLM-5.3-Flash, the bounded 180000ms request window and derived pricing. Embedding/image model settings and provider address remained unchanged. Public health, dependencies and version endpoints returned 200 with sourceb76c4cc0. These are short deployment checks, not durability qualification.The immutable image index is
sha256:bd2bed74188b2893849c6e5478cc210e68efd7db91558f856143d06640508c24; registry linux/amd64 config issha256:b76be4097d93f5c46f0eed497983fdd887e7bdc3205fc3f97eb205aed84318e1. Final source CI/image run 39243667498 passed: integration 281 pass / 0 fail / 21 gated skips; server 107/107, selector 2/2 and web 88/88. Deployment contracts passed 22/22. Skipped jobs are not counted as execution.The checked-in acceptance snapshot preserves exact source/package provenance, browser screenshots and earlier attempt results. Questionnaire专项: 66 integration, 107 server, 92 web and 8 browser passes. Cases: 52 owning, 1 isolated live fixture and 2 browser passes; forum: 10 integration and 4 browser passes, all zero skipped. Provider matrix retains its original 13/14 and separate unchanged-threshold 1/1 deadline rerun. The controlled real-model run passed with four successful calls; usage × tariff USD 0.00405601 is not a provider debit receipt.
Historical issues #153, #155, #157 and #161 remain open for their documented durability and full Worker–SPA acceptance. The incomplete 3.5.1 soak remains incomplete. The snapshot intentionally records the predeployment moment; this PR and linked release workflow provide the subsequent deployment receipt.