Repository navigation
Finalize 1.1.0 release authorization and Central installation guide - #48
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.
Summary
Authorization and package evidence
The explicit project-owner authorization was given by Shawn Chen on 2026-11-19 and is quoted in docs/release-readiness.md. It is not represented as a legal opinion or legal review.
All four downloaded native snapshot JARs contain license information, engine-third-party.tsv and a CycloneDX SBOM. Every bundled inventory matches the committed 26.11.1 inventory SHA-256 8183a651f5e7f454b5048f99e9cca4ae487594cebbc181c94ac8c432496973ce. These checks establish presence and consistency, not an independent legal determination. Stable artifacts still require their own post-upload inspection.
Validation / CI
Remaining before stable publication
Safety
This PR neither publishes 1.1.0 nor claims it is already available. Merging this documentation does not trigger Central publishing. Remote tag push and resulting release upload, and final Portal Publish, still require their own explicit confirmations. autoPublish=false remains unchanged.
Note
Document 1.1.0 release readiness and Central installation guide
Macroscope summarized cf4d208.