Pin Speakeasy version to 1.795.1 - #141
Merged
Merged
Conversation
Speakeasy CLI 1.795.2 fails registry tagging during publish with "err_unauthorized: unauthorized -- bearer token missing" (403), which blocks the PyPI release job. 1.795.1 promotes tags successfully with the same API key, so pin to it until the regression is fixed upstream. Co-authored-by: Cursor <cursoragent@cursor.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
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
Publish SDK is broken on Speakeasy CLI
1.795.2. TheCreate Github Releasejob creates the release, then fails on registry tagging:Because that job fails, every downstream job (including
Publish Python SDK) is skipped — GitHub releasev0.5.0exists, but PyPI is still on0.4.0.The API key is fine: SDK generation on
1.795.2pulled the bundle from the registry the same day, andcribl_control_plane_sdk_pythonpromoted tags successfully on1.795.1using the same org secrets and the same pinned action SHA. The only difference between the passing and failing runs is the CLI patch version.Pinning to
1.795.1until the regression is resolved upstream.Update Speakeasyisworkflow_dispatchonly, so this pin will not be reverted automatically.Test plan
Publish SDKviaworkflow_dispatchand confirmtag promotereportsSUCCESS Tags successfully addedPublish Python SDKruns andcribl-mgmt-plane0.5.0lands on PyPINote: GitHub release
v0.5.0and its tag already exist, so a full re-run may need them deleted first (or publish0.5.0to PyPI manually from thev0.5.0tag).Made with Cursor