Repository navigation
Record verified 1.6.0 publication and resume development - #250
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
1 participant
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.
Change
Java Encoder 1.6.0 is published and its downloaded artifacts have been verified. Record the immutable release source, signatures, bundle and publication evidence; remove pending-publication notices and resume development at 1.6.1-SNAPSHOT with SCM HEAD and the 1.6.0 API baseline.
Compatibility and validation
No library implementation changes. Published dependencies and support guidance remain at 1.6.0. All 13 Central payloads and 13 signatures match retained release files; all 32 GitHub assets match. Focused Sol review recommends MERGE. Postpublication clean reactor and required CI will be checked before merge.
Material AI assistance: Codex prepared and reviewed this housekeeping; model reviews supplement maintainer controls. The operator authorized the existing audit-visible PR review bypass, with CI still required.