Skip to content

Align PyPI workflow identity #49

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
askmy-stack merged 1 commit into from
Aug 12, 2026
Merged

Align PyPI workflow identity #49

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion .github/workflows/publish.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,6 @@ permissions:
jobs:
publish:
runs-on: ubuntu-latest
environment: pypi
steps:
- uses: actions/checkout@v7
- uses: actions/setup-python@v7
Expand Down
7 changes: 5 additions & 2 deletions docs/publishing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,8 +11,11 @@ No long-lived PyPI API token is stored in the repository.
- Owner: `askmy-stack`
- Repository: `tool-semantics`
- Workflow: `publish.yml`
- Environment: `pypi`
3. In GitHub, create an Environment named `pypi` (optional protection rules).
- Environment: leave blank

The workflow intentionally has no GitHub Environment. If an environment is added
later, add the same environment name to PyPI's trusted-publisher configuration
first; otherwise PyPI will reject the environment-scoped OIDC identity.

## Release steps

Expand Down