Repository navigation
fix(deploy): preserve sealed per-start ordinary deployment - #873
Merged
Merged
Conversation
|
You have reached your Codex usage limits for security reviews. Please try again later. |
13 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
LMM API Pull Request
变更说明 / Summary
Ordinary deployment from a confirmed per-start writer currently fails sealed startup checks, and a new capsule path cannot inherit the prior hook seal. Add a native startup projection that validates the actual predecessor capsule and loaded persistent hook, then bind the new hook only after the exact ordinary parent proves the retained writer stopped. Arch and the standalone wrapper keep the same verified shared-PG ownership through startup and confirmation; a confirmed transaction can later restart with its own per-start owner.
The patch preserves verify-existing/no-DDL scope, exact predecessor/target paths, immutable schema and writer identity, live parent RPC/PG lock checks, shutdown/refund proof, one-shot bind intents and fresh startup checks. Foreign/same-ID/non-Go targets, stale parent state and failed bind/start proofs fail closed. No API/Web behavior, dependencies, packaging or release workflow changes are included.
与上游的关系 / Upstream relationship
上游参考 / Upstream reference: N/A; follows the native startup sealing work in #870.
关联 Issue / Related issue
No separate issue; production ordinary startup compatibility follow-up to #870.
变更类型 / Type of change
验证 / Verification
Affected native checks include complete bind fixtures, real local PostgreSQL parent/terminal restart linkage and race checks. Wrapper tests pass 11 cases; deployment entrypoints and Web shipping tests pass 18/17. Two initial tool build attempts failed linked-worktree VCS discovery; the recorded successful command pins the exact Git directory/worktree and retains vcs.modified=false. Original failed records remain preserved.
Unchanged API and Web test results are reused with immutable source-object comparisons; no full application matrix or local API/Web build was repeated. Actual-systemd optional tests remain skipped. Official signatures, native package installation and origin/browser acceptance belong to the authorized release/deployment and are not claimed by these local tests.
截图或日志 / Screenshots or logs
Source-matched local records retain exact commands, exits and stdout/stderr SHA256. Qualification source:
bc80af271b7449cea58a260a4d718a427e8065b2; all five selected records pass the standard local-release verifier. No production logs or secrets are included.提交检查 / Checklist