Deployments blocked by an expired dependency in the build image

Several services could not deploy at all: their pipelines failed at the first stage, so nothing downstream ever ran.

Cause

The shared build image is based on a Debian release whose security repository metadata expired on 2026-09-07. A step that installs a required library was written so that the expiry caused the install to be skipped silently rather than reported. The job then failed much later with an unrelated-looking error that pointed nowhere near the real cause.

Fix

The install step no longer treats the expired metadata as fatal - the library it needs is published in a repository that still resolves. Applied across every affected service.

Follow-up

This is a correct fix but a temporary one: the underlying build image is end-of-life and is being replaced separately. Tracked on its own.