Repository navigation
chore: bump Speakeasy to 1.803.2 and Go to 1.26.10 - #1060
Merged
Merged
Conversation
Contributor
|
I'll fix CI failures and address comments from users with write access that start with 'Devin'.
Original prompt from Christine
|
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
christineschen
marked this pull request as ready for review
October 28, 2026 19:30
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
Bumps
speakeasyVersion1.787.0 → 1.803.2 and regenerates. The main reason is Speakeasy 1.803.0's fix that keeps spaces in Mintlify per-tag page titles (APIKeys→API Keys). Since 1.803.1, Speakeasy generates Go SDKs that require Go 1.26.10, so this PR also raises the module minimum.Breaking change (call out in release notes):
components.BatchListTimestampis removed and theListBatchesCreatedAfter/CreatedBeforeparams are now untyped. Code that referencescomponents.BatchListTimestampwon't compile. The new CLI treats the spec's non-uniqueoneOfas any. We're accepting this to match the TypeScript SDK; the Python SDK has the same change in OpenRouterTeam/python-sdk#1164.Go version (consumer-facing):
go.mod(go 1.25.10→go 1.26.10). I bumpedgo.workand everyexamples/*/go.modby hand; otherwise the workspace doesn't load.README.md,OVERVIEW.md, andexamples/README.md. The README line sits inside the generated[requirements]section, and the regen itself left it at 1.25, so a later regen may revert it.go-version-file: go.mod, and the devcontainer is already on Go 1.26.GOTOOLCHAIN=local. Worth a release-notes line.Other generated behavior changes:
*sdkerrors.ResponseValidationErrorinstead of the raw decode error. It wraps the original error (Unwrap), soerrors.Isanderrors.Ason the cause still work.stream.WithCancel).UnmarshalJSONmethods restore the previous value when decoding fails.ajson0.8.0 → 0.9.6; the unusedtestifyrequire is dropped.Verified locally with Go 1.26.10:
go build ./...,go test ./..., and all 8 examples build.go vetreports "unreachable code" warnings, but main has the same warnings and CI doesn't run vet.Link to Devin session: https://openrouter.devinenterprise.com/sessions/bc8bb271041644498372880d927279ed
Open in Devin Desktop: https://openrouter.devinenterprise.com/desktop/session/bc8bb271041644498372880d927279ed?variant=devin
Requested by: @christineschen