Skip to content

v2.0.4

Choose a tag to compare

View all tags
@github-actions github-actions released this 22 Oct 13:50
· 26 commits to main since this release
v2.0.4
992b3d5
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

⚠️ Behaviour change: merged images now need --force to remove

updex features disable --now and updex catalog remove now refuse to remove an image that systemd-sysext has merged, unless you pass --force (#445, fixes #444).

This was always the documented behaviour, but updex did not detect merged images on most hosts. It only looked at a legacy CurrentSymlink (which updex itself removes on install) and /run/extensions (a search directory, not merged state). On those hosts the commands unmerged, deleted the image, and refreshed at once.

updex now reads the merged state that systemd-sysext records in each hierarchy (/usr/.systemd-sysext/, /opt/.systemd-sysext/):

  • systemd 258 and later: origin gives the merged file, so the refusal names the version.
  • Older systemd: extensions gives the name only, so the refusal shows version unknown.
  • If that metadata cannot be read, the guard fails closed: the component shows merge state unknown and the command needs --force.
  • Nothing changes when the image is not merged.

Migration

  • Scripts or automation that run features disable --now or catalog remove on a host with the image merged must add --force. Without it, the command now exits with an error and changes nothing.
  • With --force, the image is removed; the merged copy stays active until the next reboot or systemd-sysext refresh, as documented.
  • Plain features disable (without --now) is unchanged.
  • SDK callers: GetActiveVersion / GetActiveVersionAt use the new signal; the new sysext.GetActiveVersionWith(t, sysext.ActiveStatePaths{...}) takes explicit paths, and RuntimePaths.SysextHierarchies (default /usr, /opt) sets them per client. GetActiveVersionIn keeps its old behaviour. See ADR-0015.

SDK: legacy sysext runners are refused for real installs

A ClientConfig.SysextRunner that implements only the original 4-method sysext.SysextRunner (no LinkToSysextAt) now gets updex.ErrLegacySysextRunner (test with errors.Is) from any non-dry-run operation that links an image — CatalogAdd, EnableFeature{Now: true}, and updates — before anything is changed (#405). Previously it silently linked into the package-global sysext.SysextDir, ignoring RuntimePaths.SysextLinkDir. Dry runs still work with any runner. The interface is unchanged; add LinkToSysextAt to make a custom runner usable. The CLI is not affected.

Dependency updates

  • github.com/frostyard/std v0.2.2 → v0.3.0 (#442): reporters stop writing after the first write error instead of retrying each event; nil writers become io.Discard. Output on a healthy writer is unchanged.
  • github.com/ProtonMail/go-crypto 1.4.1 → 1.5.2 (#430)
  • github.com/klauspost/compress 1.19.2 → 1.20.1 (#429)
  • github.com/ulikunitz/xz 0.5.16 → 0.5.17 (#422)

Build and CI (no change to the shipped binary)

  • make ci now runs the docs-integrity gate (#403).
  • Release-config check warns instead of failing on Dependabot PRs without GORELEASER_KEY; push and merge-queue runs still require it (#443).
  • Node 20 (EOL) → 24 LTS for tooling (#408).
  • Actions: codecov/codecov-action 7.1.1 (#424), actions/setup-node 7.1.0 (#437), goreleaser/goreleaser-action 7.3.0 (#436), jdx/mise-action 5.1.2 (#435).

Full Changelog: v2.0.3...v2.0.4

Assets 11
Loading