Build warnings: the image ships its apt state, and actions/checkout@v3 targets Node 20

[eliasbakken]

The v1.1.0 tag build (run 35377526264) carries a set of annotations on every variant. None of them are new: RC8's tag build (run 35123137990) shows exactly the same warnings at the same counts, which is expected since v1.1.0 is RC8's commit. Nothing here affected the release - this is about the next one.

Two are worth fixing. Two are informational and are listed only so nobody has to work that out again.

1. The image ships its build-time apt state

Eight of the warnings, all of this shape, on every variant:

WARNING: SDCARD /var/lib/apt/lists dir is not empty before 'apt-get update' :: <rootfs>/var/lib/apt/lists (18 files)
WARNING: SDCARD /var/cache/apt dir is not empty before 'apt-get update' :: <rootfs>/var/cache/apt (27 files)
...
SDCARD /var/lib/apt/lists is not empty /var/lib/apt/lists :: 18 files
SDCARD /var/cache/apt is not empty /var/cache/apt :: 27 files

The last two are reported at the end of the build, so the finished rootfs still holds the package indexes and apt cache from build time.

trim_image.sh already removes srcpkgcache.bin (~46 MB) and stops it being regenerated - but it runs first, before anything is installed, and nothing tidies up after the 15 apt-get update / apt-get install calls that follow it in install_components. The cost:

• image size - package indexes for trixie are tens of MB, plus whatever is left in the cache;
• stale indexes on first boot - an apt install before an apt update resolves against lists from build day.

Fix: a last step in the build that runs apt-get clean and rm -rf /var/lib/apt/lists/*. pkgcache.bin is regenerated on the first apt run, as trim_image.sh already notes, so nothing on the board depends on it being there. Worth measuring the actual saving on one image before and after.

2. actions/checkout@v3 targets Node 20

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v3.

Harmless today because GitHub forces it onto Node 24, but it will fail once Node 20 support is removed outright. Fix: bump to actions/checkout@v5. Reflash has the same warning, plus actions/setup-node@v3, and wants the same bump.

3. Informational: the rootfs no longer fits in tmpfs

Rootfs post-tweaks size is larger than estimated tmpfs size 4205MiB > 2300MiB

For fluidd, mainsail and octoprint - not barebone - Armbian builds the rootfs on disk instead of in RAM. That affects build time only, not the image, and may be part of why those variants take 27-35 minutes against barebone's 7. A possible build-speed optimisation, not a defect.

4. Informational: Armbian skipping a package on trixie

Not-installing software-properties-common For distro 'Debian' release 'trixie'

Armbian leaving out a package that does not apply to trixie. Nothing to do.