-
@ Zapstore
2025-05-18 14:32:08
Hash mismatches from Github releases are a rare but recurrent problem.
The issue is that developers sometimes re-publish releases under the exact same version. Since we index based on version, in those cases we keep a stale sha256 hash in our self-signed events.
Github does not expose hashes anywhere in their releases API. I'll see if I can mitigate this with a timestamp check.
nostr:nevent1qqs95cyjcnp3uyke5hnp855pnn4de8ynkcpphangfj88qlkget0nsegppemhxue69uhkummn9ekx7mp0qgsflweqjfr53l7lsw62gz8tx5aaygshvw0xk6dfpe8fg5z8cwhd7fgrqsqqqqqpyy007u