fix(mycelium): update stale md5 checksum for v0.6.1 asset#31
Open
ashraffouda wants to merge 1 commit into
Open
fix(mycelium): update stale md5 checksum for v0.6.1 asset#31ashraffouda wants to merge 1 commit into
ashraffouda wants to merge 1 commit into
Conversation
The mycelium package build fails with 'checksum mismatch': the v0.6.1 release asset was re-uploaded upstream and its md5 no longer matches the pinned value. Update to the current asset md5 (db532d4d7e0d975ee7e8128bdc9ad8b9, sha256 cfc50c3e...ad6). Pre-existing, unrelated to the repo-rename migration. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
7 tasks
This file contains hidden or 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
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.
mycelium / builderfails with[-] checksum mismatch. Themycelium v0.6.1release asset was re-uploaded upstream, so its md5 no longer matches the pinnedMYCELIUM_CHECKSUM.160f367228ff6a8a933ff0a55209d010db532d4d7e0d975ee7e8128bdc9ad8b9(sha256cfc50c3e57b29991209e7233585c484cc2552e8e1abd512c6727f94d30fb1ad6, 7393527 bytes)Pre-existing, unrelated to the repo-rename migration.