Repository navigation
docs: synchronize published Engine 0.183.366 evidence - #153
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.
Update README, COMPATIBILITY and the 366 release note to describe the published component instead of an unpublished candidate. Record the exact producer, merge/tag, tested tree and original JAR SHA256, with 420 suites / 3,912 tests / zero failures/errors / one existing skip. Distinguish 21 new methods, 62 focused cases, 63 affected-class methods and 97 required identities.
Keep assembled Server/native business QA pending and Service environment private input unimplemented. README links to the detailed current release evidence rather than repeating historical release identities.
Validation: checked the published metadata and all 12 current native asset digests against the anonymous readback receipt; verified documentation facts, LF bytes, relative links, JSON examples and git diff --check. Only the three canonical documentation files changed; POMs, code, workflows, the original tag and release assets remain unchanged. No Maven rerun.