Repository navigation
Clean up retired site sources and post-release documentation - #252
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.
Change
Retired Maven Site sources still recommended 1.4.0, and completed September maintenance records were mixed with current release guidance. Remove the six unused Site files and their parity-helper special case, archive the maintenance records with corrected links, and lead MAINTAINERS.md with the latest recorded status.
Refresh the Action pin inventory, API baseline and publisher dependency documentation, verify the consumer inventory against published 1.6.0 artifacts, clarify the wrapper checksum, and add the dated Daybreak review correction. Historical evidence, release tags/assets, library code, POMs, and workflows are preserved.
Compatibility and validation
git diff --checkpasses. No local Java/browser rerun was needed for the documentation and obsolete parity-branch removal; required PR CI remains authoritative.Prepared with Codex assistance; no independent maintainer approval is claimed.