Skip to content

ci: configure verified PyPI releases - #16

Merged
nkavian merged 1 commit into
inflowpayai:mainfrom
nkavian:ci/pypi-release
Oct 2, 2026
Merged

nkavian merged 1 commit into
inflowpayai:mainfrom
nkavian:ci/pypi-release

Conversation

@nkavian

@nkavian nkavian commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Add a manual release workflow with a safe dry-run default and a main-only publishing job.
  • Verify repository gates, shared conformance, Node interoperability, and the exact distribution files before upload.
  • Publish through PyPI Trusted Publishing, attest artifacts, verify the registry wheel, and create the immutable tag and GitHub release.
  • Reject conflicting published files and retain verified artifacts for failed-job recovery.
  • Document the exact publisher settings and release steps.

Verification

  • Full local repository gates passed with 874 tests.
  • Candidate wheel/source build, isolated consumers, and the read-only PyPI conflict check passed.
  • The PR runs the release verification job without publishing.

No package, tag, or release has been published. The PyPI pending publisher still requires owner configuration.

@nkavian
nkavian merged commit 14d679c into inflowpayai:main Oct 2, 2026
15 checks passed
@nkavian
nkavian deleted the ci/pypi-release branch October 2, 2026 03:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant