Finalize GuideCheck 2.0.0 release metadata - #4
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
GuideCheck 2.0.0 becomes the current released profile across its version constants, normative profile status, release notes, public pages, and operator documentation. Version/date checks enforce the release identity while preserving the frozen legacy 0.7.1 and strict 1.0.0 report contracts and anchored self-guide bytes.
The corrected implementation is already merged in PR #3 and issue #2 is completed. This change finalizes the owner-approved publication tranche. The POSIX JSON CLI contract remains experimental and independently selected.
Validation: full repository suite, deterministic verifier UI checks, version/date consistency, and isolated installed-wheel consumer. After exact-head CI, the approved sequence is normal merge, production identity/compatibility verification, signed
v2.0.0tag, existing release workflow, then independent asset/signature and downloaded-source verification. Delivery procedure:docs/release-2.0.0.md.