Repository navigation
build: prepare watchpost-cli trusted publishing - #5
Merged
Merged
Conversation
Avoid the occupied watchpost registry name while preserving the CLI and import module. Add manual, environment-approved TestPyPI and PyPI publishing with source-ref gates, separate build/upload permissions, and verified artifacts. Keep actual uploads separate from tag and GitHub Release creation.
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
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.
Summary
watchpost-cli:watchpostis occupied by an unrelated project on PyPI and TestPyPI. Keep the repository, CLI command, and import module unchanged.publish.yml, a manual-only Trusted Publishing workflow. Tags and GitHub Releases do not trigger registry uploads.Publishing boundaries
main; PyPI requires a tag matching the package version. Both require commits reachable from main.id-token: write. Build has read-only source access. No stored PyPI API token.Verification
twine check --strict.Docker/act and independent reviewer tools were unavailable. OIDC/publishing end-to-end verification is deliberately pending the first approved TestPyPI run.
Maintainer action
Add a pending GitHub publisher on each registry: project
watchpost-cli, ownerejames-dev, repositorywatchpost, workflowpublish.yml, environmenttestpypiorpypirespectively. Do not create an API token. Seedocs/publishing.md.