Repository navigation
ci: publish PyPI releases directly instead of via Speakeasy - #1127
Draft
LukasParke wants to merge 2 commits into
Draft
LukasParke wants to merge 2 commits into
LukasParke wants to merge 2 commits into
Conversation
Replace speakeasy-api/sdk-generation-action's sdk-publish.yaml reusable workflow with an in-repo job that reads releaseVersion from gen.lock, publishes (skipping versions already released), and creates the v<version> GitHub release. Generation still uses Speakeasy. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
LukasParke
force-pushed
the
chore/first-party-publish
branch
from
October 22, 2026 23:07
8ca8652 to
3848852
Compare
This branch has not been deployed
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
Replaces
speakeasy-api/sdk-generation-action/.github/workflows/sdk-publish.yaml@v15with a workflow in this repo that publishesopenrouterto PyPI and creates the GitHub release itself.When
.speakeasy/gen.lockchanges onmain, the job:releaseVersionfromgen.lockand checks it matchespyproject.toml.scripts/publish.sh:scripts/prepare_readme.py,uv build,uv publish, usingPYPI_TOKEN.v<version>GitHub release, unless it already exists.What changes compared with Speakeasy's publish workflow
name:(openrouter-web'ssdk-publish-health.yamllooks this file up by name), triggers, thev<version>tag on the merge commit, the<lang> - v<version> - <UTC timestamp>release title, and release notes built fromgen.lock'sreleaseNotes.gen.lock'sreleaseVersiondoesn't match the package manifest. It no longer runs Speakeasy's Docker action, and the publish job doesn't needSPEAKEASY_API_KEY.Publishing Completedmarker Speakeasy appended to release notes, and thepublishedtag Speakeasy added in its registry for the source and code samples. Themainregistry tag is still applied bytagging.yaml. If any Speakeasy docs or code-sample setup depends onpublished, that needs a separatespeakeasy tagstep.Generation (
sdk_generation*.yaml) and registry tagging (tagging.yaml) still usespeakeasy-api/sdk-generation-action. This PR only changes publishing.Testing
actionlintpasses.gen.lock(1.3.75). The PyPI check returns 200 for 1.3.75 and 404 for an unpublished version.uv run python scripts/prepare_readme.py && uv buildbuildsopenrouter-1.3.75as an sdist and a wheel.workflow_dispatchshould skip both steps because 1.3.75 is already published.Follow-up (optional)
id-token: writeis granted.uv publishuses PyPI trusted publishing automatically once this repo and workflow are added as a trusted publisher on PyPI andUV_PUBLISH_TOKENis removed.🤖 Generated with Claude Code