Bump `lightning-block-sync` version number to fix SemVer CI
What the developer wrote
Authored by Elias Rohrer
Bump `lightning-block-sync` version number to fix SemVer CI
PR #4175 made the first breaking API change in `lightning-block-sync`
since v0.2 without bumping the version number. Here we bump the version
number, allowing our SemVer CI check to be happy again.
What changed, and why it matters
This commit only changes a package version number in a configuration file (from 0.2.0+git to 0.3.0+git) to satisfy an automated SemVer compatibility check. It does not change any code, fix any bug, or alter any behavior.
No security action needed. This is a routine versioning/metadata change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit bumps the version of the lightning-block-sync crate in Cargo.toml from 0.2.0+git to 0.3.0+git. The commit message explains this was needed because a prior pull request introduced a breaking API change without incrementing the version number, causing the project’s SemVer CI check to fail. The diff contains no source code changes.
Changed components
lightning-block-sync/Cargo.tomlInspect captured patch +1 / −1
diff --git a/lightning-block-sync/Cargo.toml b/lightning-block-sync/Cargo.toml
index 51b19e3..97f1999 100644
--- a/lightning-block-sync/Cargo.toml
+++ b/lightning-block-sync/Cargo.toml
@@ -1,6 +1,6 @@
[package]
name = "lightning-block-sync"
-version = "0.2.0+git"
+version = "0.3.0+git"
authors = ["Jeffrey Czyz", "Matt Corallo"]
license = "MIT OR Apache-2.0"
repository = "https://github.com/lightningdevkit/rust-lightning"
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.