Skip to content

ci: restructure release workflows to unblock PyPI trusted publishing#234

Draft
MikeGoldsmith wants to merge 2 commits into
open-telemetry:mainfrom
MikeGoldsmith:mike/release-fix-trusted-publishing
Draft

ci: restructure release workflows to unblock PyPI trusted publishing#234
MikeGoldsmith wants to merge 2 commits into
open-telemetry:mainfrom
MikeGoldsmith:mike/release-fix-trusted-publishing

Conversation

@MikeGoldsmith

@MikeGoldsmith MikeGoldsmith commented Jul 9, 2026

Copy link
Copy Markdown
Member

Releases fail at pypa/gh-action-pypi-publish because it runs from a reusable workflow, which PyPI trusted publishing doesn't support (warehouse#11096).

This PR moves the publish step into a job defined directly in each top-level release workflow. The rest of the release logic stays DRY via two reusable workflows (_release-build.yml, _release-finalize.yml). Prepare workflows are renamed and consolidated at the same time.

Follow-up (not in this PR): register two new trusted publishers per PyPI project (release-package.yml and release-all.yml, environment pypi). See the updated RELEASING.md table.

@MikeGoldsmith MikeGoldsmith added the Skip Changelog PR does not require a changelog entry label Jul 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Skip Changelog PR does not require a changelog entry

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant