Skip to content

Add packslip manifest to releases - #134

Merged
nnutter merged 5 commits into
masterfrom
timber
Nov 22, 2026
Merged

nnutter merged 5 commits into
masterfrom
timber

Conversation

@nnutter

@nnutter nnutter commented Nov 22, 2026

Copy link
Copy Markdown
Owner

No description provided.

Change-Id: I895fe6f77fa8b7106fa2e97e8b9d973cf080e6e7
Change-Id: I93b37680e42940995d14d52d5774c77e0c0b808c
Packslip resolves a command by its file name inside the archive. The
release archives currently name the executable after the archive, so a
packslip install cannot find the command it should put on PATH. Keep the
version in the archive's outer file name, where packslip already reads
the platform from, and use a stable executable name inside.

Change-Id: I72506de8aacf79dbfdb42186d7518298a06a01f0
Packslip gives installers a signed manifest of each release's artifacts
and commands, so users can install Timber without a per-vendor recipe.
Sign the build archives in a read-only job, then attach the bundle in
the publish job before it publishes, keeping the app token away from the
signing action. Name the build artifacts so the publish job can select
them apart from the new bundle.

Change-Id: I53e64ad532c94ee28653ade930a5bf656565bd4a
Packslip and mise's packslip backend now install Timber from the signed
release. Document both alongside the Go install, and note that the first
signed release establishes the signer until its fingerprint is recorded.

Change-Id: I51dab4f42c9ffec3e517e955c37968ca71691bde
@nnutter
nnutter merged commit 1fbfbf1 into master Nov 22, 2026
3 checks passed
@nnutter
nnutter deleted the timber branch November 22, 2026 16:49
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