Skip to content

Ci/pin harvest content - #42

Merged
jaanisoe merged 2 commits into
mainfrom
ci/pin-harvest-content
Oct 9, 2026
Merged

jaanisoe merged 2 commits into
mainfrom
ci/pin-harvest-content

Conversation

@jaanisoe

@jaanisoe jaanisoe commented Oct 9, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

With push-to-registry the attest action also writes an org-level artifact
metadata storage record, which needs a permission the image job does not
have and came back "no artifacts found": two warnings on every release.
The record is unused, provenance is the attestation itself, so skip it
rather than widen the token. The comment that blamed download-artifact
for the warnings was wrong and is gone.
The two userportal extension tags fired on every userportal release,
twice in three weeks, and both times nothing here had to change. Watch
the facts instead: the deployed profile files by hash and the dcat
fork's upstream base against the conformance requirements, resolved at
whatever tag the userportal's own ckan/Dockerfile names.

Replace the gdi-metadata README-phrase pin with content drift of the
vendored shapes: `drift` takes a set filter and distinct exit codes, and
the pins leg runs it for gdi-metadata, fatal under PINS_STRICT.

A rebuilt base image is a note in the weekly job and fatal only under
BASE_IMAGE_STRICT, which release and pins-strict set; image-scan already
fails on a fixable CVE in the pinned base.

One classify_fetch_failure beside curl_to decides gone, rate-limited or
unreachable for every fetch site, so a 404 counts as drift everywhere.
@jaanisoe
jaanisoe merged commit b9f7640 into main Oct 9, 2026
27 checks passed
@jaanisoe
jaanisoe deleted the ci/pin-harvest-content branch October 9, 2026 08:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant