Repository navigation
ci: validate release artifacts and guard GitHub publication - #62
Merged
Merged
Conversation
added 12 commits
October 10, 2026 01:34
Add guarded GitHub-first release preparation and artifact integrity checks. Keep PyPI publication disabled. Assisted-by: OpenAI Codex
Assisted-by: OpenAI Codex
Include prepared release notes in strict documentation navigation. Assisted-by: OpenAI Codex
Use LF checkouts, POSIX Git paths, byte-exact fixtures and platform CPU identification. Preserve existing assertions and scope fingerprints. Assisted-by: OpenAI Codex
Mock release mutation while checking exact assets and commit targeting. Assisted-by: OpenAI Codex
Keep missing benchmark metadata distinct from platforms without affinity support. Assisted-by: OpenAI Codex
Refuse mismatched remote tags and atomically create missing refs only in authorized publication mode. Assisted-by: OpenAI Codex
Continue independent artifact checks while keeping failed suites a hard candidate gate. Assisted-by: OpenAI Codex
Preserve documentation coverage and exact package-content checks across locales. Assisted-by: OpenAI Codex
Keep isolated Windows documentation checks independent of the console locale. Assisted-by: OpenAI Codex
Assisted-by: OpenAI Codex
Assisted-by: OpenAI Codex
AlexMarinescu
changed the title
AlexMarinescu
marked this pull request as ready for review
October 10, 2026 02:04
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.
Summary
Prepare GitHub-first gem 1.0.0 release automation with a 15-job CPython 3.10–3.14 Linux, macOS and Windows matrix. Publication remains separately authorized and disabled by default.
Changes
Runtime mathematics, packaging metadata, dependencies and reference assertions are unchanged.
Verification
At implementation commit
0e085b4bfd532935bb1267bb3eae95f04de3ed15, all five Linux and all five macOS jobs passed 4,036 tests each. All five Windows jobs passed 4,035 and failed the same strict showcase JSON comparison: a generated value of0.8660254037844389differs from the committed0.8660254037844387. Zero expected failures and zero skips on every platform. The assertion remains intact; this Windows reference blocker prevents release approval.All 15 jobs passed wheel and sdist installation, metadata, mathematical smoke tests, 268 API declarations and 43 executable documentation examples: 30 isolated installations. Five local interpreter suites also passed all 4,036 tests. Strict MkDocs/site checks, workflow policy checks and Actionlint passed. Final commit adds the verification report only.
Hosted package results · Documentation results · Verification report
Real protected master dispatch remains unexecuted; server protection configuration requires maintainer verification. PyPI authority remains unverified and blocks PyPI only. No tags, releases, package uploads or Wiki writes were performed.
Assisted by OpenAI Codex.