Skip to content

145_asdf-mise-registry-submissions.md

Latest commit

 

History

History
101 lines (90 loc) · 3.6 KB

145_asdf-mise-registry-submissions.md

File metadata and controls

101 lines (90 loc) · 3.6 KB
Raw
id 145
title Publish mdsmith via asdf and mise registry submissions
status 🔲
summary Land the asdf-plugin repo (jeduden/asdf-mdsmith) and the mise-plugins/registry entry that the multi-channel release pipeline already documents but cannot trigger from this repo. Spun out of plan/130 because both tasks ship outside this repo.
model opus

Publish mdsmith via asdf and mise

Goal

The release pipeline already attaches per-platform binaries to every vX.Y.Z GitHub release. The smoke-test job in release.yml verifies the binary works through mise use -g ubi:jeduden/mdsmith@VER. The gap left is that asdf install mdsmith and the bare mise use mdsmith@latest form do not yet resolve. Neither registry knows about us yet.

Background

mise reads our GitHub releases directly via its ubi backend. A registry entry is just the difference between ubi:jeduden/mdsmith@VER (works today) and the shorter mdsmith@VER form.

asdf is different. It needs a plugin repo that knows how to list versions and fetch the binary. Once that plugin repo exists, the asdf-vm/asdf-plugins index lets users skip the URL on asdf plugin add mdsmith.

Tasks

  1. Create the jeduden/asdf-mdsmith repo with the standard plugin layout:
  • bin/list-all calls git ls-remote --tags on this repo, strips refs/tags/, drops the ^{} deref entries, and removes the leading v so the output is plain X.Y.Z as asdf expects. No GitHub token required; works through HTTPS git.
  • bin/download curl -fLs the matching release asset.
  • bin/install verifies it against checksums.txt and places the binary as bin/mdsmith.
  • bin/list-bin-paths prints bin.
  1. Add a CI workflow on jeduden/asdf-mdsmith that runs asdf install mdsmith latest against the most recent release and asserts mdsmith version matches the resolved tag.
  2. After one successful release cycle, file a PR to asdf-vm/asdf-plugins adding mdsmith so asdf plugin add mdsmith resolves without an explicit URL.
  3. File a PR to mise-plugins/registry adding mdsmith via the ubi backend pointing at jeduden/mdsmith releases. Once merged, the shorter mise use mdsmith@latest form starts resolving on user CLIs without any code change in this repo.
  4. Update docs/guides/install.md to drop the "pending follow-up" badge from the asdf and short-mise sections once each registry PR merges.
  5. Update the release-workflow smoke-test matrix in release.yml to also exercise asdf install mdsmith X.Y.Z and the bare mise use mdsmith@X.Y.Z form, in addition to the ubi: form already covered.

Acceptance Criteria

  • jeduden/asdf-mdsmith exists with the four bin/ scripts and a green CI workflow.
  • asdf plugin add mdsmith resolves without an explicit URL after the asdf-plugins PR merges.
  • asdf install mdsmith X.Y.Z then mdsmith version prints mdsmith vX.Y.Z.
  • mise use mdsmith@X.Y.Z (no ubi:) resolves after the mise-plugins/registry PR merges, and mdsmith version prints mdsmith vX.Y.Z.
  • docs/guides/install.md no longer flags asdf or short-form mise as pending follow-ups.
  • The smoke-test matrix in release.yml runs asdf install mdsmith and bare mise use mdsmith@VER channels green on a tag.