document building v2.5.3 to v2.5.6 with lenient dependency verification, as two pom files were later republished to maven central with additional metadata
What changed, and why it matters
This commit only updates documentation. It explains that when building older Sparrow Wallet releases (versions 2.5.3 through 2.5.6), two dependency files on Maven Central were later republished with extra descriptive metadata, causing a harmless checksum mismatch. The documentation tells builders how to use a lenient verification mode and to confirm only those two POM files differ. There is no code change and no indication the JAR files or application behavior changed.
No immediate action required. This is a documentation-only commit. Users building v2.5.3-v2.5.6 should follow the documented lenient verification steps and confirm only the two named POM files fail checksum verification. If additional failures appear, they should be investigated and reported.
Security signals we found
Dependency checksum mismatch in recorded verification metadata
POM-only republication of two Sparrow-published artifacts (hid4java, usb4java)
Documentation instructs lenient verification for reproducible builds of older releases
Evidence from the diff
The diff adds a section to docs/reproducible.md. It notes that releases v2.5.3-v2.5.6 record dependency checksums in gradle/verification-metadata.xml. After release, com.sparrowwallet:hid4java:0.8.1 and com.sparrowwallet:usb4java:1.3.6 POMs were republished to Maven Central with additional metadata, so their POM checksums no longer match. The JARs are unchanged. The workaround is to build with ./gradlew jpackage –dependency-verification lenient and verify the dependency-verification report lists exactly those two POM failures. No source code, build logic, or dependency artifacts are modified.
Changed components
docs/reproducible.mdInspect captured patch +15 / −0
### docs/reproducible.md
@@ -91,6 +91,21 @@ cd {yourPathToSparrow}/sparrow # if you aren't already in the sparrow folder
The binaries (and installers) will be placed in the `build/jpackage` folder.
+#### Building v2.5.3 to v2.5.6
+
+These releases check the checksums of their dependencies against those recorded in `gradle/verification-metadata.xml`.
+After they were released, `com.sparrowwallet:hid4java:0.8.1` and `com.sparrowwallet:usb4java:1.3.6` were published to Maven Central with additional descriptive metadata in their POM files.
+The jar files are unchanged, but the two POM files no longer match their recorded checksums, so the build stops with a dependency verification error.
+To build these releases, run:
+
+```shell
+./gradlew jpackage --dependency-verification lenient
+```
+
+Gradle will then report verification failures without stopping the build.
+Check the report in `build/reports/dependency-verification/` lists exactly two failures, for `hid4java-0.8.1.pom` and `usb4java-1.3.6.pom`.
+Any other failure indicates a problem and should be reported.
+
### Verifying the binaries are identical
Verify the built binaries against the released binaries on https://github.com/sparrowwallet/sparrow/releases.Why this scored 18/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.