Repository navigation
This package is not available on PyPI #2
Description
Activity
The package metadata is present in
pyproject.toml, but this repository has no published release or tag yet. The existing publish workflow runs when a GitHub release is published and requires the repositoryPYPI_API_TOKENsecret. Eric Greer (@integrii), please publish the initial release (v0.1.0) once PyPI credentials are configured, or confirm that the README should be changed to remove thepip installinstructions.Update: v0.1.0 was published on GitHub, but the package is still not available on PyPI. The Publish workflow run 33161389524 failed during PyPI upload because the workflow did not grant
id-token: writefor trusted publishing; thekuberhealthy-clientPyPI endpoints currently return 404. The README install instruction is therefore still not usable. Eric Greer (@integrii), please confirm whether to configure PyPI trusted publishing (and workflow permissions), providePYPI_API_TOKEN, or remove the install instruction. No code work is being started pending that direction.Thanks for reporting this. We published the initial v0.1.0 GitHub release, but the package-publish workflow failed because GitHub Actions did not grant its PyPI OIDC token.
A workflow fix was committed as 5281813, but the release bot cannot push workflow-file changes without the required GitHub Actions workflow permission. PyPI publication remains blocked until that permission is granted or the fix is applied; we will update this issue when
pip install kuberhealthy-clientsucceeds.Release status: v0.1.0 is published on GitHub, but
kuberhealthy-clientis still absent from PyPI because Publish run 33161389524 failed to obtain the OIDC token. Fix commit 5281813 adds the requiredid-token: writeandcontents: writepermissions, but it is not onmain. Please apply that fix and configure PyPI trusted publishing orPYPI_API_TOKEN; then rerun the release publish workflow. The README install command should remain until publication is verified.Status update (2026-09-09): v0.1.0 remains published on GitHub but unavailable on PyPI; the latest Publish workflow failed at the publish step. Next step: configure PyPI trusted publishing/OIDC or a repository token and verify the workflow permission before rerunning.
Release verification: v0.1.0 and its GitHub Release/tag are present, but Publish workflow run 33161389524 failed at the PyPI publish step. PyPI currently returns 404 for kuberhealthy-client. Configure and verify PyPI trusted publishing (OIDC) or a valid
PYPI_API_TOKEN, then rerun the existing failed workflow; no new tag or release is needed.Update: PR #3 is now merged at
5373ad2, and the post-merge Build workflow passed. The v0.1.0 publish recovery is still pending PyPI credentials/trusted publishing;kuberhealthy-clientremains unavailable on PyPI. Release Manager is tracking the recovery and will update this issue after publication is verified.Update: Recovery release v0.1.0-recovery.1 triggered Publish run 34905805077, which failed because PYPI_API_TOKEN is not configured; the publish action received no password and no OIDC token. The workflow on main is in place. Next step: configure the repository PyPI token secret and rerun the recovery release, or configure PyPI trusted publishing with id-token: write. kuberhealthy-client remains unavailable on PyPI.
Release update: PR #4 enables PyPI trusted publishing with
id-token: writeand removes the unavailable token credential; build and DCO checks pass. It remains open pendingkuberhealthy-clienttrusted-publisher configuration and maintainer approval. After merge/configuration, rerun the v0.1.0 recovery publish against the merged workflow; no semver version bump is appropriate while the package metadata remains 0.1.0.Update: PR #4 merged at
e8b6e571. The trusted-publishing workflow is now onmain; Release Manager will rerun the v0.1.0 recovery publish and verifykuberhealthy-clienton PyPI. No version bump is planned.Update (2026-09-14): PR #4 merged at
e8b6e57and the v0.1.1 GitHub Release/tag was published. Build run 34908560562 passed, but Publish run 34908560535 failed at PyPI withinvalid-publisher. The OIDC claims identifyrepo:kuberhealthy/python:ref:refs/tags/v0.1.1and.github/workflows/publish.yml; PyPI has no matching trusted publisher, andkuberhealthy-clientremains unavailable. Next step: configure the matching PyPI trusted publisher, rerun the v0.1.1 publish, and verify the package.Release update: the merged trusted-publishing workflow was exercised by v0.1.1, but Publish run 34908560535 failed with PyPI
invalid-publisherforrepo:kuberhealthy/python:ref:refs/tags/v0.1.1. Configure the matchingkuberhealthy-clientPyPI trusted publisher for.github/workflows/publish.yml, rerun the failed workflow, and verify the package. No new release/tag is needed.Release status: the webhook’s requested
v0.1.0recovery no longer matches repository state.main, package metadata, and the existing release/tag arev0.1.1ate8b6e571; PyPI remains 404. The existingv0.1.1publish run failed with PyPIinvalid-publisher, and rerun is currently denied because the bot lacks Actions write permission. Configure the matchingkuberhealthy-clienttrusted publisher and grant Actions write access, then rerun the existing workflow; no duplicate tag or release should be created.Release recovery was retried with the merged trusted-publishing workflow.\n\n- Existing GitHub tag/release: v0.1.1 at e8b6e57.\n- Build run 34907751901 passed.\n- Retry run 34911290344 reached PyPI and failed with invalid-publisher for repo:kuberhealthy/python and .github/workflows/publish.yml.\n- kuberhealthy-client remains unavailable on PyPI (HTTP 404).\n\nConfigure the PyPI trusted publisher for owner kuberhealthy, repository python, workflow .github/workflows/publish.yml, with no environment, then rerun the Publish workflow. No additional semver tag or release was created.
README mention user need to call
pip install kuberhealthy-clientwhat's not true, that library is not avail on pypi.org. Change README or upload the package there