Add missing metadata for jackson-base pom 2.12.1 #5839
Merged
Conversation
This file contains 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
Problem: When merging bisq-network#5824, the absence of this entry caused a build failure at dependency verification time against JDK11 and JDK15 on Ubuntu-latest [1]. It may also cause failures on other JDK/OS combinations, but the GitHub workflow was aborted before those failures couldhave occurred. In any case, this omission did not create build failures on any of the local development machines that tested the aforementioned PR. Reasons for this discrepancy are unknown. Solution: manually fetch the pom from [2], run `sha256sum` on it locally and commit the result to the verification metadata file. [1]: https://github.com/bisq-network/bisq/runs/4249640611?check_suite_focus=true#step:6:33 [2]: https://repo1.maven.org/maven2/com/fasterxml/jackson/jackson-base/2.11.1/jackson-base-2.11.1.pom
cbeams
force-pushed
the
add-jackson-pom-checksum
branch
from
87cf050 to
ea629de
Compare
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.
Problem: When merging #5824, the absence of this entry caused a build
failure at dependency verification time against JDK11 and JDK15 on
Ubuntu-latest 1. It may also cause failures on other JDK/OS
combinations, but the GitHub workflow was aborted before those failures
couldhave occurred. In any case, this omission did not create build
failures on any of the local development machines that tested the
aforementioned PR. Reasons for this discrepancy are unknown.
Solution: manually fetch the pom from 2, run
sha256sumon it locallyand commit the result to the verification metadata file.