Repository navigation
fix(sdk): track Ledger v2 release/v2.4 source - #2017
Merged
Merged
Conversation
NumaryBot
added
risk: medium
Dav-14
marked this pull request as ready for review
November 5, 2026 13:43
NumaryBot
added
review-approved
NumaryBot
approved these changes
Nov 5, 2026
NumaryBot
left a comment
NumaryBot
left a comment
There was a problem hiding this comment.
The required automated review completed with no remaining findings.
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
Fetch
openapi.yamlthrough the GitHub contents API and refresh the Speakeasy source digests. SDK composition now follows fixes on the Ledger 2.4 branch.Evidence
LEDGER_V2_VERSIONwas pinned tov2.4.17and downloaded a release asset.After:
release/v2.4resolves and its OpenAPI document downloads successfully through the configured contents endpoint.nix develop --impure --command just pre-commit: OpenAPI composition, allvalidate-openapiinvariants, and event schema generation. Speakeasy reported 0 errors and 63 warnings; its local self-update emitted a cross-device rename diagnostic without failing validation.git diff --check; working tree clean after commit.Merge Danger
Door: two-way
Revert this commit to restore the release tag and downloader.
Blast Radius: SDK
Future generation follows a mutable release branch rather than an immutable tag. No runtime service configuration changes. No intentional API/data breaking changes or capability reductions; downstream SDK compatibility has not been separately qualified.