build for 1.12.1 has reran and changed SHA1 signature

[gilandose]

https://jitpack.io/com/github/everit-org/json-schema/1.12.1/build.log 2021-03-19

this looks like it has ran in the past couple of days and is causing issues with resolvers as the sha is not matching the cached version anymore

wrong checksum: ~/.cache/coursier/v1/https/jitpack.io/com/github/everit-org/json-schema/org.everit.json.schema/1.12.1/org.everit.json.schema-1.12.1.jar (expected SHA-1 4da1b89bb0a0ffb25a228c04d837b425158a80ba in /root/.cache/coursier/v1/https/jitpack.io/com/github/everit-org/json-schema/org.everit.json.schema/1.12.1/org.everit.json.schema-1.12.1.jar.sha1, got 85da07827b689184f893154dd8c8ab3691f9ec3b)

[erosb]

Extremely odd. I think nobody worked on the library that day.

[o0oxid]

The actual checksum of the file is '85da07827b689184f893154dd8c8ab3691f9ec3b', it's unclear where expected '4da1b89bb0a0ffb25a228c04d837b425158a80ba' check sum came from.

curl -s 'https://jitpack.io/com/github/everit-org/json-schema/org.everit.json.schema/1.12.1/org.everit.json.schema-1.12.1.jar' | shasum
85da07827b689184f893154dd8c8ab3691f9ec3b  -

[makkkino]

+1
Same here

[totalslacker]

Note that if you run curl -s 'https://jitpack.io/com/github/everit-org/json-schema/org.everit.json.schema/1.12.1/org.everit.json.schema-1.12.1.jar' | shasum multiple times it will tend to flip flop between the two hashes. Perhaps the new build wasn't replicated across all mirrors?