Repository navigation
Update the NIF checksums for v0.7.0 - #100
Merged
Merged
Conversation
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.
Before
checksum-Elixir.Exmpeg.Native.exslists the v0.6.0 tarballs.Problem
The Hex package of 0.7.0 must carry the checksums of the v0.7.0 tarballs, or
RustlerPrecompiledrefuses the download.After
The file lists the three tarballs of https://github.com/rubas/exmpeg/releases/tag/v0.7.0. The values equal the release's
SHA256SUMS.The merge publishes 0.7.0: the
Publish to Hexjob ofrelease.yml(#98) runsmix hex.publish --yes, and Hex holds the release until an owner approves it on hex.pm.Details
Written by
task checksum:download, asRELEASE.mdsays. Inubuntu:24.04with the README's packages,lddfinds every library of the v0.7.0 x86_64 NIF.