Repository navigation
v0.0.15
runnerd 0.0.15
Before you upgrade
Nothing to migrate: the job history stays at version 13. A config with a Discord target cannot go back to 0.0.14,
which refuses it; remove those targets first. Upgrading has the steps.
New
- Discord notifications.
kind = "discord"in[[notify.targets]]posts failures, lost jobs, runners that cannot
start, new insights and the digest to a channel's webhook as one embed, with mentions off so a job name cannot ping
anyone. Each target kind (webhook, ntfy, Discord) is now its own sender behind one interface
(ADR 0064).
Fixed
- The budget said "27.25G of 46G free" while a job waited because the host had 6.52G to spare. When the host leaves
the slice less thanMemoryMax, the free figure is now what the host leaves, and the bar marks the rest held by
the host. While the slice is past 90% under measured admission, or the host stalls, nothing shows as free and the
bar says why. The host line in status, the TUI and the dashboard ends with what is free.
Download runnerd 0.0.15
| File | Platform | Checksum |
|---|---|---|
| runnerd-aarch64-unknown-linux-musl.tar.xz | ARM64 MUSL Linux | checksum |
| runnerd-x86_64-unknown-linux-musl.tar.xz | x64 MUSL Linux | checksum |
Verifying GitHub Artifact Attestations
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
gh attestation verify <file-path of downloaded artifact> --repo ayagmar/runnerdYou can also download the attestation from GitHub and verify against that directly:
gh attestation verify <file-path of downloaded artifact> --bundle <file-path of downloaded attestation> --repo ayagmar/runnerdrunnerd-cli 0.0.15
Download runnerd-cli 0.0.15
| File | Platform | Checksum |
|---|---|---|
| runnerd-cli-aarch64-unknown-linux-musl.tar.xz | ARM64 MUSL Linux | checksum |
| runnerd-cli-x86_64-unknown-linux-musl.tar.xz | x64 MUSL Linux | checksum |
Verifying GitHub Artifact Attestations
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
gh attestation verify <file-path of downloaded artifact> --repo ayagmar/runnerdYou can also download the attestation from GitHub and verify against that directly:
gh attestation verify <file-path of downloaded artifact> --bundle <file-path of downloaded attestation> --repo ayagmar/runnerd