This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Reason given by maintainers: this is only use to testing
zenpy-release-poc
⚠️ This is NOT a real package. Do not
pip installit. It is a throwaway proof-of-concept published to real PyPI only to test a release automation workflow. It does nothing useful and will not be maintained or updated for actual use.
Minimal proof-of-concept for the release-automation approach proposed for facetoe/zenpy#692: a GitHub Actions workflow that publishes to PyPI via Trusted Publishing (OIDC) whenever a GitHub Release is published.
Not a real package - just enough source (zenpy_release_poc/, a setup.py
build like zenpy's, and one CLI entry point) to exercise the workflow.
Note: this targets production PyPI, not Test PyPI. A successful run
permanently claims the zenpy-release-poc project name and publishes real,
unremovable files (PyPI does not allow re-uploading or deleting individual
release files, only yanking a version). Test PyPI's publishing settings
page was unreliable when this was tried, hence the switch - re-point
publish.yml's pending-publisher target back to test.pypi.org and add
repository-url: https://test.pypi.org/legacy/ to the publish step if you
want to retry there instead.
Try it
- Push this repo to
hassaku63/zenpy-release-pocon GitHub. - On PyPI, add a pending publisher at
https://pypi.org/manage/account/publishing/ :
- PyPI project name:
zenpy-release-poc - Owner:
hassaku63 - Repository:
zenpy-release-poc - Workflow:
publish.yml - Environment: (leave blank)
- PyPI project name:
- Tag the commit
0.1.0(must matchzenpy_release_poc/__version__) and push the tag. - Create a GitHub Release from that tag and publish it.
- Watch the Actions run - it should build and upload to https://pypi.org/project/zenpy-release-poc/ with no secrets stored in the repo.
Local sanity check
pip install -e .
zenpy-release-poc --version
zenpy-release-poc
Metadata
Release files for zenpy-release-poc 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| zenpy_release_poc-0.1.4.tar.gz | 3.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| zenpy_release_poc-0.1.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.4 kB
Release files / zenpy_release_poc-0.1.4.tar.gz
| Download URL | zenpy_release_poc-0.1.4.tar.gz |
|---|---|
| Size | 3.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d587452f7497aa0ba2fb4b4dafa3b1e81766851747c8115f6a2d661bebf6c111
|
|
BLAKE2b-256 checksum How to use checksums |
30d4ba1f53fc2863364cd16684ca65f53023facf0f5a1cf514776cca1d1ee960
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 2, 2026.
Transparency logRelease files / zenpy_release_poc-0.1.4-py3-none-any.whl
| Download URL | zenpy_release_poc-0.1.4-py3-none-any.whl |
|---|---|
| Size | 4.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c404781445acb57aa57a8fe86a63e58b1cc229d0ad4c3f0759b24f840e33fa56
|
|
BLAKE2b-256 checksum How to use checksums |
31c88d411d6b3b4bb0aac52c9eb03b08fcc5db922ad69cbbee7e228295c0767b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 2, 2026.
Transparency log