chore: bump signet-sdk to 0.17.0#274
Draft
Evalir wants to merge 3 commits into
Draft
Conversation
Pre-emptive bump to consume the upcoming 0.17.0 release of signet-sdk, which renames the BundleKey cursor field globalBundleScoreKey to targetBlockNumber (init4tech/signet-sdk#231). The builder does not paginate GET /bundles directly, but signet-sdk crates are pinned together so they all bump in lockstep. signet-bundle dev-dep aligned to the same release. node-components git deps are on a separate version cycle and unchanged. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Evalir
force-pushed
the
evalir/bump-signet-sdk-0.17
branch
from
87843f7 to
5551012
Compare
prestwich
approved these changes
May 11, 2026
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
2 participants
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
Pre-emptive bump of the published signet-sdk crates from
0.16.0-rc.17→0.17.0so the builder picks up the upcoming SDK release in lockstep.The 0.17.0 release renames the
BundleKeycursor fieldglobalBundleScoreKey→targetBlockNumber(init4tech/signet-sdk#231). The builder doesn't paginateGET /bundlesdirectly, so this is purely a recompile against the new types — no business-logic changes here.signet-bundledev-dep aligned to the same release. Thesignet-block-processor/signet-genesisgit deps fromnode-componentsare on a separate cycle and intentionally untouched.Closes ENG-2235
Related
Merge prerequisite
CI will fail until signet-sdk
0.17.0is published to crates.io. Keep this in draft until then.Test plan
make fmtmake clippymake test(All pending the upstream publish.)