Bump Breez.Sdk.Spark: 0.23.0 -> 0.25.0 - #80
Closed
github-actions[bot] wants to merge 1 commit into
Closed
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
chore/breez-sdk-0.25.0
branch
from
September 22, 2026 10:42
4f1026f to
30aa0a8
Compare
2 of 3 tasks
Owner
|
Superseded by #85, which bumped Breez.Sdk.Spark straight from 0.23.0 to 0.26.0 and is merged for the 1.2.0 release. |
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
1 participant
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.
Bumps
Breez.Sdk.Sparkfrom0.23.0to0.25.0, a version upstream has publisheda GitHub Release for — tag-only NuGet pushes are deliberately not proposed (see
.github/workflows/breez-sdk-update.yml).Upstream release notes: https://github.com/breez/spark-sdk/releases/tag/0.25.0
The SDK is pre-1.0 with no stability promise between releases: read the notes (when they
exist) and the API-surface diff before merging, per the pinning comment on the
PackageReference. CI on this PR — including the live and funded regtest suites — is the
merge gate, not a substitute for that read.