Nightly builds

This page explains the nightly builds of Tilde: where they are, how their version reads, how long they are kept and why they are not signed. A nightly build is the development branch, develop, as it stands. It is not a release and it may not work.

Do this first

Use a nightly build only when you want a change before its release. To use one with apt, point the source at the nightly distribution. These are the lines of Install on Debian and Ubuntu with nightly in place of stable:

sudo curl https://codeberg.org/api/packages/squidd/debian/repository.key -o /etc/apt/keyrings/forgejo-squidd.asc

echo "deb [signed-by=/etc/apt/keyrings/forgejo-squidd.asc] https://codeberg.org/api/packages/squidd/debian nightly main" | sudo tee /etc/apt/sources.list.d/tilde.list

sudo apt update && sudo apt install tilde-all

The second line replaces the stable line in tilde.list, so the source names one distribution at a time. stable and nightly hold packages of the same names, and apt installs the newest version it can see. To stop following the nightly builds, write the stable line again: apt does not install an older version by itself, so the nightly stays installed until a release newer than it arrives.

What a build is

Every night the Nightly workflow builds develop with scripts/nightly.sh. It builds the packages tilde-cli and tilde-tui for amd64 and arm64, the metapackage tilde-all, and the archives of tcli and tt for every system of Install from an archive. A night with no new commit builds nothing.

The packages go to the nightly distribution of the registry. The archives and the packages also go to a pre-release called nightly on the release page. Each night it replaces the one of the night before.

The version

The version is the next release plus a marker:

0.6.0-nightly.202611070301.g1a2b3c4

tcli --version prints it in this form. The part after nightly. is the date and time of the build in UTC (year, month, day, hour, minute) and g with the short hash of the commit.

In a package the dash is a tilde, 0.6.0~nightly.202611070301.g1a2b3c4-1, because Debian sorts a tilde before the version without it. A nightly build is newer than the last release and older than the release it leads to, so apt upgrade moves from it to that release when it comes. The version of a nightly build is the version of the next release.

How long they are kept

The registry keeps the last seven nightly versions and deletes the older ones. The pre-release nightly keeps one build.

Signature

The nightly builds are not signed with the release key. The pre-release has a SHA256SUMS and no SHA256SUMS.asc, so the steps of Check a download do not apply. With apt, the packages are checked with the key of the registry, as for a release.