Repository navigation
Document Server 549 publication and scoped SBOM acceptance - #354
Merged
Merged
Conversation
chen21019
force-pushed
the
docs/server549-publication
branch
from
October 24, 2026 13:30
d7a1648 to
554ae11
Compare
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.
Document published Server v1.6.549 and its scoped 8080 acceptance. The current README now contains only the 549 release and guides; the release note records the exact image/config/source identities, 34 verified immutable assets, independent browser SBOM scan coverage and preserved 548 rollback.
The original publisher job remains failed only for the empty report upload. The documented recovery uses the same image and verified CI bytes, with deterministic gzip transport and a public recovery receipt. Browser coverage remains incomplete: all 87 npm PURLs received lookup, while six unsupported snapshots remain unknown.
The QA scope covers the retained-configuration cutover, actual-container SBOM readback, consistent backup, Chrome OIDC/TOTP, seven JSON APIs, session refresh and WebSocket frame. Earlier fixture/window failures remain disclosed; this does not claim a full permission matrix, additional manual restart or production deployment.
Validation: 16 published-install document tests and three current-document/exact-contract tests pass; diff checks pass. Changes are limited to five Markdown files, and installation examples retain numeric image tags.