release: pisama 0.6.3 documentation metadata repair - #24
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
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.
Fresh published-package rubric 1.8.0 audit found only D1 for pisama: docs.pisama.ai returns 410 (acquirer 53/59, technical 5/5). This patch release changes Documentation to the canonical README and carries the merged hosted onboarding guide. Version and source fallback move together to 0.6.3; no behavioral API change. Local gates: 196 tests passed, Ruff and mypy passed; isolated sdist/wheel builds and Twine passed. Both artifacts contain MIT license text/metadata, hosted guide and corrected documentation URL, with the retired URL absent from metadata. PyPI 0.6.3 was absent when preparation began. No release or registry publication yet. Merge requires normal protected checks; publication will use the existing release-triggered trusted-publisher workflow, followed by exact artifact/provenance and fresh audit verification.