Repository navigation
ci(release): Publish a signed packslip - #659
Merged
Merged
Conversation
Add a job that signs a packslip for each release with the workflow's
OIDC identity and uploads it as a release asset. It lists every
archive's digest and the timoni executable inside it, links the
provenance the goreleaser job already attested, and declares the shell
completions (`timoni completion {shell}`) and the `skills/timoni`
agent skill, so installers such as mise can verify the download and
install completions and the skill matching the installed version.
It runs as its own job so a signing failure cannot block the module
push or the SLSA provenance.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Jeff Dickey <216188+jdx@users.noreply.github.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Jeff Dickey <216188+jdx@users.noreply.github.com>
This was referenced Sep 27, 2026
Owner
Author
|
thanks! |
jdx
added a commit
to jdx/mise
that referenced
this pull request
Sep 28, 2026
Timoni and Worktrunk now publish signed packslips with their releases. `mise use timoni@0.35.0` and `mise use worktrunk@0.80.0` can install from the release manifests, verifying the workflow signature and artifact digest while also receiving the completions and version-matched skills declared by each project. The `packslip:` backend takes priority starting with Timoni 0.35.0 and Worktrunk 0.80.0. Earlier versions remain installable through their existing Aqua (and, where configured, asdf or Cargo) backends. `mise ls-remote` lists versions from the preferred backend, so older releases can be listed with `mise ls-remote aqua:stefanprodan/timoni` or `mise ls-remote aqua:max-sixty/worktrunk`. The registry declares the `timoni`, `wt`, and `git-wt` executable names so lazy install shims can select the right tool. Validated both signed releases with `mise ls-remote packslip:…` and an explicit `mise exec packslip:…@version`: `timoni --version` returned `timoni version 0.35.0`, and `wt --version` returned `wt v0.80.0`. The installed releases contain the declared executables. `mise run lint-fix` passed. Tracks #13712. Upstream release PRs: stefanprodan/timoni#659 and max-sixty/worktrunk#4301. *AI-assisted — Tool: Codex; model: OpenAI/unavailable; version: unavailable.* <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Added Packslip registry support for Timoni version 0.35.0 or later and Worktrunk version 0.80.0 or later. * Registered `timoni` as a Timoni binary, and `git-wt` and `wt` as Worktrunk binaries. * Existing Aqua support for Timoni and Aqua and Cargo support for Worktrunk remain available. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
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.
This adds a
packslipjob to the release workflow. After GoReleaser publishes a release, the job signs a packslip and uploads it as one more release asset,packslip.sigstore.json. A packslip is a signed inventory of the release: the digest of each archive, thetimoniexecutable inside it, and the extra files that ship with this version.What this gets you and your users
stefanprodan/timoni's own release workflow (keyless Sigstore signing through GitHub OIDC), then checks each archive's digest and size against it before unpacking anything. mise also remembers the signer, so a release that turns up signed by a different workflow or key is not installed until the user explicitly decides to trust it. There's no signing key for you to store or rotate. It builds on the cosign signatures and attestations your release already produces: the packslip links that provenance, and installers check it by default instead of needing per-tool setup.timoni completionfor the exact version they have installed, with nothing to add to their shell rc files.timoniskill ships with each release, pinned to the release commit, so an agent working with a given timoni release reads the skill written for that release, not whatever is on the default branch.mise skills lsshows it, andmise skills synclinks it into a project's agent directory.Once a release ships a packslip, I'll switch mise's registry entry for timoni to use it, so users get all of this from a plain
mise use timoniwith nothing to change on their end. Other installers can check the same file withpackslip verify.What it declares:
timoni_*_{darwin,linux}_*.tar.gzandtimoni_*_windows_*.zip(six archives). It leaves out the checksums file, the source tarball and the SBOM.bin: timoni(packslip recordstimoni.exefor the Windows zips)attest: link: the existingactions/atteststep already attests every archive through the checksums file, so the packslip links that provenance and doesn't add a second attestation. The new job only needscontents: writeandid-token: write.It runs as a separate job that
needs: [goreleaser]and pulls the archives from the release. If signing fails, the module push and the SLSA provenance job still run.How I checked it, against v0.34.0:
packslip create(1.4.0, the pinned version) with the same bin and resources, a throwaway key, and the provenance URLs the action would add. All six archives got the right os/arch and bin path, and the static Linux builds carry no libc requirement, so musl hosts such as Alpine can use them. Every archive's provenance URL resolves to the existing SLSA attestation fromrelease.yaml.packslip verifypassed with all six artifacts checked.skills/timoni/SKILL.mdis present at the v0.34.0 commit.timoni completion bash|zsh|fish|powershellprints a script for each shell, and it works with an empty environment. The bash, zsh and fish output passes a syntax check.actionlintreports nothing new, andzizmorreports nothing on the new job.Maintainers don't need to do anything besides merge. The first packslip will show up on the next release.
I maintain packslip and mise, and I'm happy to change anything here or drop it if you'd rather not have it.
AI-assisted — Tool: Claude Code; model: anthropic/claude-opus-5-5; version: unavailable.
🤖 Generated with Claude Code