Repository navigation
Document published Server562 and designated deployment boundary - #406
Merged
Merged
Conversation
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.
Server562 is published and deployed to the designated 8080 baseline, while the current docs still describe Server561 and a 562 candidate. Align README, COMPATIBILITY, the 562 release note and the performance install example with publisher 41279691957, the 35 verified public assets and sealed cutover/restart/smoke receipts.
Keep Docker examples numeric-only, record the immutable digest in publication evidence, and distinguish baseline health from pending Core/External/Certificate/Audit/B3 business acceptance. Preserve the corrected External previews, restricted-Key discovery, sanitized permission guidance, review/footer layout, JDBC 3.5.11 and retained ServiceIndex cleanup semantics. The performance doc changes only its two version references; settings and all product/gate source remain unchanged.
Validation: four release-note renderer tests, all 16 published-install contract cases and git diff --check passed. Product tests and QA were not rerun. Required CodeQL follows the normal PR gate.