Package release

[dAnjou]

Hi,

thanks again for fixing #3 so fast!

I just looked at the conversation again, and noticed that I was using 0.2.1 which was already about outdated at the time of my report, and then you said it's fixed in 0.6.1 which is quite a jump.

So I looked at the available package release: https://crates.io/crates/ink-md/, and it's still at 0.2.1.

I'm using mise use cargo:ink-md which is pulling from there. Could you maybe publish the current version? 🙂

And, additional ask: any chance to publish to https://aquaproj.github.io/ as well? 🙏

Thanks, and no worries if it's too much of a hassle 👍

[borghei]

You caught a real drift — and worse than you thought: it wasn't just crates.io. Homebrew was stuck at 0.2.2 and Scoop at 0.1.0 too. v0.6.4 is a packaging overhaul aimed squarely at this issue.

Working right now:

• .deb / .rpm on every release (amd64 + arm64, covered by SHA256SUMS) — on your Fedora box: sudo dnf install ./ink-md-0.6.4-1.x86_64.rpm.
• For mise specifically, the ubi backend pulls the prebuilt binary straight from GitHub releases today: mise use -g ubi:borghei/ink.
• curl -fsSL https://raw.githubusercontent.com/borghei/ink/main/install.sh | sh — checksum-verified; set INK_INSTALL_DIR="$HOME/.local/bin" to skip sudo.
• Homebrew tap and Scoop bucket are current at 0.6.4 again, and cargo binstall ink-md metadata is in place.

crates.io: publishing is now wired into the release workflow so it can't silently drift again, and the catch-up publish of 0.6.4 is in motion — I'll ping this issue the moment mise use cargo:ink-md resolves to 0.6.4, and only then. (Learned my lesson in #3 about declaring victory before verifying the exact path you use 😄)

aqua: fair ask — it needs a PR to aquaproj/aqua-registry, which I'll look into. In the meantime the ubi: backend above gives you the same binaries through mise with zero wait.

[borghei]

Update as promised: crates.io is current again — ink-md 0.6.7 is live (verified via the registry API before posting this).

So mise use cargo:ink-md now installs the latest version, and plain cargo install ink-md / cargo binstall ink-md (binstall metadata is in the manifest, so it pulls prebuilt binaries instead of compiling) work too.

The release workflow also has a publish job wired in now, so crates.io stays in lockstep with GitHub releases going forward instead of drifting again.

Still parked: the aqua-registry entry — their contribution flow requires a Docker-based scaffold I can't run at the moment, so ubi:borghei/ink remains the mise-native alternative in the meantime.

[borghei]

Closing — every distribution channel you asked about is now live or in flight:

• crates.io: ink-md 0.6.7 is current, so mise use cargo:ink-md gets the latest. Publishing is wired into the release workflow so it won't drift again.
• aqua: aquaproj/aqua-registry#57715 is open with CI green — scaffolded and container-tested per their process, so aqua:borghei/ink (and mise's aqua backend) will work once the maintainer merges. Until then ubi:borghei/ink gives you the same prebuilt binaries via mise.
• Also since your report: .deb/.rpm on every release (amd64 + arm64), Homebrew and Scoop un-stuck and bumped automatically, cargo binstall ink-md pulling prebuilt binaries, and a checksum-verified install.sh.

Thanks for pushing on this — the packaging story is in a completely different place than when you filed it. I'll drop one more comment here when the aqua PR merges.