Files
cozystack/packages/system
Aleksei Sviridkin 8dfbaa1d66 fix(kubevirt-cdi-operator): pin the vendored CDI release
This package decides which CDI the platform runs, but its update
recipe took the version from GitHub's releases/latest redirect. Any
refresh, including one done for an unrelated reason, could move the
deployed CDI and its seven image tags without anyone choosing a
release, and the diff carried no version line to review. That version
is becoming load-bearing for behaviour, not only for images: logic
that enumerates CDI's DataVolume phases is correct against one
release.

The release is now named in the Makefile, the asset is checked
against a digest before anything is written, and a refresh that fails
partway leaves the vendored manifest untouched. The digest guards
against an asset replaced under its tag; it is not an authenticity
check.

A test target ties the pin to the tree: helm-unittest reads only the
vendored file, so a pin moved without re-running update would
otherwise leave every assertion green against the old release. The
suite also holds the two local patches and the namespace rewrite that
every refresh has to reapply.

The pinned release is the one already vendored, and update reproduces
templates/ byte for byte.

Assisted-by: LLM
Signed-off-by: Aleksei Sviridkin <f@lex.la>
2026-09-22 23:45:58 +03:00
..
2026-03-25 15:57:25 +05:00
2026-02-10 20:19:03 +01:00