By: Tom Sydney Kerckhove <syd@cs-syd.eu>
Release promql and promql-gen to Hackage The same shape as opt-env-conf: a release-to-hackage input, a package that is what a release of this is, and a nix-ci.nix saying which package to deploy and which secret it needs. The release set is named by what it leaves out rather than by what it takes in, so a package added later is released unless somebody says otherwise. The other way round, a new one stays unreleased until somebody remembers a list in the flake, and nothing says they forgot. What it leaves out is promql-e2e, which is the harness that asks a Prometheus whether the other two are right. That is this repository's own business. The two that are released get what Hackage wants and did not have: a licence file, a changelog, the repository, and a copyright line. MIT, which is what validity, autodocodec and safe-coloured-text are, and what both package.yaml files already claimed without a file to back it.
Total
8s
Created Started Finished
| Time to Start | Worker time | Duration | Time to finish | Idle | |
|---|---|---|---|---|---|
| Config | 0s | 0s | 0s | 0s | 0s |
| Eval | 0s | 7s | 7s | 8s | 0s |
| Build | 7s | 0s | 0s | 7s | 0s |
| Suite | 0s | 8s | 8s | 8s | 0s |