Skip to content

Publish tested patchling distributions on main - #37

Draft
mikkel wants to merge 4 commits into
mainfrom
ci/publish-pypi-on-main
Draft

mikkel wants to merge 4 commits into
mainfrom
ci/publish-pypi-on-main

Conversation

@mikkel

@mikkel mikkel commented Nov 18, 2026

Copy link
Copy Markdown
Member

The workflow builds and checks the wheel and sdist, runs the offline test suite, and checks the exact installed version on PyPI. It uploads the tested artifacts from the canonical default branch through a separate Trusted Publishing job. Published versions are skipped.

Local distribution build and strict Twine check passed. The offline suite passed 263 tests and skipped two opt-in tests.

Before merging, register owner 255BITS, repository patchling-py, workflow publish.yml, environment pypi in the existing patchling PyPI project settings. The GitHub pypi environment must allow main.

0.9.5 is declared on main and absent from PyPI. Merging after publisher setup can publish 0.9.5 immediately.

…fy-patchling-pypi-with-current-main

* commit 'f7a3a16a41793b38dbe50ab39da0e5e91967bb00':
  Verify Patchling Python documentation on merge (#39)
  Publish a GitHub prerelease for each main merge [skip ci]

This branch has not been deployed

No deployments
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