ci(release): PyPI Trusted Publishing (OIDC) release workflow#37
Merged
Conversation
Tag-triggered (`v*`) workflow that builds all 17 workspace packages (`uv build --all-packages`) and publishes them to PyPI via OIDC Trusted Publishing — no API token. A packaged-wheel smoke gate installs the freshly-built dists and asserts the public API + rebranded defaults before the publish job runs; publish is gated on the `pypi` GitHub environment (manual approve). Requires one-time setup (documented in the workflow header): a `pypi` environment + a Trusted Publisher entry per PyPI project (Owner=Scaffoldic, Repo=forgesight, Workflow=release.yml, Env=pypi). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
What
Adds
.github/workflows/release.ymlso future versions auto-publish to PyPI from a tag — no API token, via PyPI Trusted Publishing (OIDC). Modeled onagentforge-py's release workflow, adapted for ForgeSight's 17-packageuvworkspace.Flow
uv build --all-packages→ all 17 wheels + sdists as an artifactForgeSightMiddlewarepresent, oldAgentForgeMiddlewaregone,prometheus prefix=forgesight,datadog service=forgesight,clickhouse table=forgesight_records) — catches packaging bugs before publishpypa/gh-action-pypi-publishwithid-token: write(OIDC, no password),skip-existing, gated on thepypiGitHub environment (manual approve)Triggers on
v*tag push (sogh release create vX.Y.Zpublishes) +workflow_dispatchfor re-runs.pypiGitHub Environment (Settings → Environments), ideally with required reviewers.Scaffoldic, Repoforgesight, Workflowrelease.yml, Environmentpypi.Until that's configured, the publish job will 403. The existing manual
twine upload+PYPI_TOKENpath (launch/) keeps working in the meantime.🤖 Generated with Claude Code