Skip to content

chore: checksums for the 0.5.1 NIF artefacts - #89

Merged
rubas-agent[bot] merged 1 commit into
mainfrom
checksum-0.5.1
Nov 12, 2026
Merged

rubas-agent[bot] merged 1 commit into
mainfrom
checksum-0.5.1

Conversation

@rubas-agent

@rubas-agent rubas-agent Bot commented Nov 12, 2026

Copy link
Copy Markdown
Contributor

Before

checksum-Elixir.WhisperCpp.Native.exs lists the six v0.5.0 tarballs. v0.5.1 has its tag and all six tarballs on the release: https://github.com/rubas/whisper_cpp/releases/tag/v0.5.1

Problem

The Hex package must carry the checksums of the v0.5.1 NIFs, or mix compile fails for every user of 0.5.1.

After

The file lists the six v0.5.1 tarballs, and each checksum equals the release's SHA256SUMS. The merge starts the Publish to Hex job of release.yml, which stages 0.5.1 on hex.pm for approval.

Details
  • Generated with mix rustler_precompiled.download WhisperCpp.Native --all --no-config --ignore-unavailable --print from the v0.5.1 commit, as AGENTS.md asks.
  • Checked locally: the six lines match SHA256SUMS of the release, and mix test --include integration passes 86 of 86 on the downloaded x86_64-unknown-linux-gnu NIF.

@rubas-agent
rubas-agent Bot merged commit a80a85e into main Nov 12, 2026
1 check passed
@rubas-agent
rubas-agent Bot deleted the checksum-0.5.1 branch November 12, 2026 16:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant