Repository navigation
docs: restore scope caveats and stamp make check with the commit - #59
Conversation
The style rewrites in e051dbb and ec52311 removed a few statements that bound what the published evidence proves. No fact changed, but a reader could take candidate-stage dependency checks and local KES fixtures as proof of the final artifacts or of a real cloud backend, and the compatibility page no longer said that a timeout leaves I/O unresolved. Restore them in English and Chinese, next to the claims they qualify: - 20261026 notes: local protocol fixtures do not certify real cloud accounts or backend crash durability; a later unconditional PUT is not ordered after an unresolved request; candidate checks describe dependency compatibility only. - Server compatibility: a timeout does not prove that I/O stopped, and delayed rollback remains possible. - silo-pkg 3.15.2 notes: no new CVE fix is claimed for the SDK patches. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Signed-off-by: Feng Ruohang <rh@vonng.com>
A saved `make check` log could not be tied to the source it checked: it recorded neither the commit nor whether the tree had uncommitted or untracked files, and an untracked page is enough to change the build. Hosted CI is bound to a commit by the runner, but a local log is the only evidence for work that cannot be pushed yet. Print `git rev-parse HEAD` and `git status --short --branch` before the build. The line is informational: a dirty tree is the normal state when checking before a commit, and a failure outside a Git checkout is ignored. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Signed-off-by: Feng Ruohang <rh@vonng.com>
Deploying silo-pgsty-com with
|
| Latest commit: |
a9e9941
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://dfcd9340.silo-pgsty-com.pages.dev |
| Branch Preview URL: | https://docs-restore-scope-caveats.silo-pgsty-com.pages.dev |
|
Resolution. The scope and safety caveats removed during the documentation rewrite were restored in The documentation now states that local KES/Moto protocol fixtures do not certify real cloud accounts or backend crash durability; candidate dependency checks describe compatibility only and do not validate the final Server source; a timeout does not prove that disk or RPC I/O has stopped; delayed commits and rollbacks remain possible; a later unconditional PUT does not establish ordering against an unresolved request; and the release does not add distributed fencing or automatically repair previously inconsistent data. The related wording was reviewed and merged through site PR #59. H-06 is closed with the original evidence boundaries restored. |
|
Resolution. The site I reran This fixes the traceability gap for future local logs. Historical logs created before the change remain historical evidence and are not retroactively relabeled. Hosted release verification is separately bound to the release commit |
Summary
Two small follow-ups from a review of the 20261026 documentation.
Restore scope caveats (EN/ZH). The style rewrites in e051dbb and ec52311 dropped a few statements that bound what the published evidence proves. No fact changed, but the pages no longer said so next to the claims:
blog/release/silo-20261026: local protocol fixtures do not certify real cloud accounts or backend crash durability; a later unconditional PUT is not ordered after an unresolved request; the candidate checks describe dependency compatibility only and do not certify the final Server source.compatibility/server(20261026 upgrade checks): a timeout does not prove that I/O stopped, and delayed rollback remains possible. Added to the paragraph below the table, so the table is untouched.blog/release/pkg-3.15.2: no new CVE fix is claimed for the SDK patches.The wording follows the text that was on the site before the rewrite.
Stamp
make check. The target now printsgit rev-parse HEADandgit status --short --branchbefore the build, so a saved local log identifies the commit and any uncommitted or untracked files. It is informational only: a dirty tree does not fail the check, and a failure outside a Git checkout is ignored. The workflow is unchanged; hosted runs are already bound to a commit by the runner.Verification
make checkona9e99410f399863cc18d97e4b3289de833a65c18with a clean tree (local Hugo 0.169.0 extended; CI uses the pinned 0.168.0):all modules verifiedmaininternal link check passed: 626727 rendered internal references across 1836 HTML files🤖 Generated with Claude Code