Changelog

Evaluation jobs are faster.

The job that works out what your flake has to build now uses nix-ci-eval, a tool written for exactly that job. On a flake with a few dozen outputs it finishes in roughly a third less time. Flakes with only a handful of outputs were already quick and stay about the same.

Changelog entries now say who they are for, and the ones that only concern whoever runs the NixCI instance are marked as such.

Most entries are about NixCI as you use it. Some are about running the instance itself, and those now carry an Admin tag next to their version, so you can tell at a glance which entries are yours to care about.

26-07.4

Admin

NixCI sends less alert mail about things that are not faults.

A user revoking the access they granted is reported as a warning rather than an error, one failed worker to leader call raises one alert rather than two, and the log derived alerting rules are labelled as never resolving, so that the resolved mail they used to send every time their window slid past the line that fired them can be dropped.

Fixed: a worker's per-job credential could be written to the server logs.

Each build gets its own short-lived key that the worker uses to report progress back to NixCI. When a request carrying that key failed, the whole request was written to the server logs to help diagnose it, and the key went with it.

The keys involved were scoped to a single build and are no longer valid. Server logs are kept for 15 days and are not public. Nothing else was affected, and no action is needed on your side.

Request headers written to the logs are now filtered against the same list that already covered cookies and login tokens, on requests NixCI sends as well as the ones it receives.

Revoking the access you granted NixCI on GitHub, GitLab or Codeberg is no longer treated as a failure.

When you revoke that access, the stored token stops working. NixCI already handled this correctly by deleting the token, but it also recorded the token refresh as a failed background job. Revoking access is your decision to make, so nothing about it counts as a failure any more.

NixCI now has a changelog, and this is its first entry.

Every change to NixCI gets an entry here from now on, so you can see what shipped without having to ask. Each entry has a version number like 26-07.1: a two-digit year, a month, and a counter that starts again each month.