Skip to content

ci(release): Publish a signed packslip - #659

Merged
stefanprodan merged 2 commits into
stefanprodan:mainfrom
jdx:packslip
Sep 28, 2026
Merged

stefanprodan merged 2 commits into
stefanprodan:mainfrom
jdx:packslip

Conversation

@jdx

@jdx jdx commented Sep 27, 2026 •

Copy link
Copy Markdown

This adds a packslip job 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, the timoni executable inside it, and the extra files that ship with this version.

What this gets you and your users

  • Better security. Installers such as mise and aqua find timoni's downloads through a registry entry someone else wrote, and at best compare them to a checksum file hosted on the same release. With a packslip, an installer first checks that the manifest was signed by 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.
  • Direct control over how timoni is installed. The manifest comes from your release workflow, so you decide which archives exist for which platforms, where the executable sits in each, and what ships with it. Installers no longer depend on third-party registry entries that infer all of that from asset names and drift when a name or platform changes.
  • Completions that just work. Users get bash, zsh, fish and PowerShell completions from timoni completion for the exact version they have installed, with nothing to add to their shell rc files.
  • Your agent skill, matched to the version. The timoni skill 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 ls shows it, and mise skills sync links 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 timoni with nothing to change on their end. Other installers can check the same file with packslip verify.

What it declares:

  • Artifacts: timoni_*_{darwin,linux}_*.tar.gz and timoni_*_windows_*.zip (six archives). It leaves out the checksums file, the source tarball and the SBOM.
  • bin: timoni (packslip records timoni.exe for the Windows zips)
  • Resources:
    completion/bash,zsh,fish,powershell=exec:timoni completion {shell}
    skill/timoni=repo:skills/timoni
    
  • attest: link: the existing actions/attest step 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 needs contents: write and id-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:

  • I downloaded that release's assets using the same patterns, then ran 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 from release.yaml. packslip verify passed with all six artifacts checked.
  • skills/timoni/SKILL.md is present at the v0.34.0 commit.
  • The released timoni completion bash|zsh|fish|powershell prints a script for each shell, and it works with an empty environment. The bash, zsh and fish output passes a syntax check.
  • actionlint reports nothing new, and zizmor reports 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

jdx and others added 2 commits September 27, 2026 08:31
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>
@stefanprodan stefanprodan added the area/ci Internal CI related issues and pull requests label Sep 28, 2026

@stefanprodan stefanprodan left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Thanks @jdx 🏅

@stefanprodan
stefanprodan merged commit 0257dfd into stefanprodan:main Sep 28, 2026
4 checks passed
@stefanprodan

Copy link
Copy Markdown
Owner

@jdx I've released Timoni v0.35.0 with the packslip, you can now switch mise to it. Thanks!

@jdx

jdx commented Sep 28, 2026

Copy link
Copy Markdown
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 -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/ci Internal CI related issues and pull requests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants