Align public surface and frequent PyPI publishing - #1
Merged
ArturSepp merged 2 commits intoSep 8, 2026
Conversation
Documentation build overview
|
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.
Package documentation and public metadata had drifted from the shared registry, and routine PyPI publishing had no common traceability checks.
This change aligns the public surface, adds explicit dependency boundaries and a lowest-dependency CI job, and introduces a tag-based PyPI workflow that builds and verifies artifacts before Trusted Publishing. GitHub Release pages remain optional. Existing numerical implementations and CI matrices are preserved.
Validation: existing documentation builds pass with warnings treated as errors; workflow syntax passes actionlint; focused tooling and package-metadata tests pass. CI checks the complete branch before integration. Published artifact/source provenance gaps remain explicitly recorded rather than retagged without evidence.