Skip to content

ci: open an issue when :testing stops publishing - #1132

Merged
hivecommons-hive[bot] merged 10 commits into
mainfrom
ci/testing-freshness-alarm
Nov 8, 2026
Merged

hivecommons-hive[bot] merged 10 commits into
mainfrom
ci/testing-freshness-alarm

Conversation

@hanthor

@hanthor hanthor commented Nov 6, 2026 •

Copy link
Copy Markdown
Member

:testing moves only when post-testing-e2e promotes it. A broken gate therefore freezes the tag while every build stays green: from 2026-10-30 to 11-06 a missing provenance attestation stopped every promotion, and nothing said so.

What this adds

  • testing-freshness.yml: runs every six hours with permissions: {} at the top level. The job gets only contents: read, actions: read and issues: write.
  • scripts/testing-freshness.py: finds the newest post-testing-e2e run whose promote-to-testing job actually ran "Move :testing to the tested digests".
    • If that is older than 36 hours, or no such run exists in the last 60, it opens one issue labelled kind/bug, area/ci and priority/critical-urgent for the hive. The issue shows when the tag last moved and the newest run's failed jobs.
    • Later runs refresh the same issue (found by a body marker) and close it once the tag moves again.
  • It deliberately does not use the image's created field. That is SOURCE_DATE_EPOCH (the last build-input commit), not the promotion time.

Verification

  • tests/test_testing_freshness.py covers finding the last real promotion (a green run whose move step was skipped doesn't count), in-progress runs, no promotion in the window (stale), the threshold edges and the week-long freeze.
  • actionlint, just check and pre-commit pass.
  • A dry run against the live repo during the freeze reported "No promotion found in the last 60 post-testing-e2e runs" and listed the failed LUKS jobs.

Permission

issues: write on a scheduled github.token job is the maintainer-approved scope: the job's entire purpose is to file and close this one issue. It pushes nothing and uses no secrets.

@github-actions github-actions Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 6, 2026
@github-actions

github-actions Bot commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hanthor

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@hivecommons-hive

hivecommons-hive Bot commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor
bce9d6c

ℹ️ Sentinel notice — informational; author is trusted (owner), merge is not blocked

Hive flagged this PR (author @hanthor, head bce9d6cf1f23) because it matches behaviors that can override security controls, escalate privileges or damage the codebase. This is a heuristic, not an accusation — a maintainer should confirm the change is intended before it merges.

  • sensitive_path — changes 1 sensitive path(s) (Touches a sensitive path (OWNERS, workflows, policies, hive config, security docs, …))
    • .github/workflows/testing-freshness.yml

Hive did not add the sentinel-alert label because this author is trusted. The finding remains recorded for audit and the dashboard Security tab; set sentinel.trusted_authors_block: true to require the blocking label for trusted authors too.

@hivecommons-hive hivecommons-hive Bot added author/clanker A contributor's own hive authored this PR under their login no-dco A commit is missing Signed-off-by — run `git rebase --signoff` role/trusted Author is trusted for unattended merge (trusted-author role or registry/claim tier in require_tiers) stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Nov 6, 2026

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One verified problem with the freshness signal; otherwise the mechanism reads correctly.

created is the last build-input commit time, not the promotion time (scripts/testing-freshness.py:51-57)

The script treats the image config's Created as "when :testing was published". It is not. Every image build runs podman build --source-date-epoch <epoch> where the epoch is git log -1 --format=%ct -- Containerfile packages system_files scripts config .gitmodules docs/agent (Justfile:469-471, same in build-ghcr at Justfile:509-514, via scripts/podman-epoch-args.sh). Podman ≥ 5.5 writes that epoch into the config's created, which is what skopeo inspect reports.

Checked against the live tag: ghcr.io/projectbluefin/utah:testing config created is 2026-10-30T10:14:07Z; the promotion that produced it ran at 10:49 (run 41043543296), and the org.opencontainers.image.created label says 10-29 21:09. All three differ because none is "when the tag moved".

Consequence: the check fires on a quiet weekend. A Friday-evening commit to build inputs, then daily green post-testing-e2e promotions over Saturday/Sunday, still leaves created at Friday — by Sunday morning every flavor is >36 h "stale" and a priority/critical-urgent issue opens while nothing is wrong. The reverse also holds: a promotion that re-tags an image built from a fresh commit after a long freeze reads "fresh" even if the gate had been broken for days before.

Suggested fix: measure what the issue is actually about — the time of the last post-testing-e2e run that reached promote-to-testing — via gh run list --workflow post-testing-e2e.yml --status success (the job already has actions: read). The registry created can stay as a secondary column in the table, but should not be the staleness decision. tests/test_testing_freshness.py exercises stale() with synthetic datetimes, so it would not catch this; a test asserting the signal source would.

Smaller note

open_issue() searches in:body "utah:testing-freshness" and then filters by the HTML-comment marker. If GitHub's search index does not match text inside HTML comments, the search returns nothing and a new issue is opened every 6 h. I could not verify either way from here — flagging it as an open question, not a defect; searching on the title prefix would avoid depending on it.

Verified fine

  • New workflow: permissions: {} at top, job scoped to contents: read, issues: write, actions: read; persist-credentials: false; pinned checkout SHA. ubuntu-26.04 is already used by build.yml and image-baselines.yml.
  • scripts/flavors.py images returns [{"image": "utah"}, …] for all four flavors, which is what images() reads.
  • Labels kind/bug, area/ci, priority/critical-urgent all exist in the repo, so gh issue create --label will not fail.
  • RFC 3339 nanosecond trimming in parse_created is correct and tested.

Since this adds a scheduled workflow with issues: write, a repository approver should confirm the automation is wanted — the author is one, so I expect that is settled.

Confidence: 3/5 (needs attention) — 1 high finding

— hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88

@hivecommons-hive hivecommons-hive Bot added stage/072-returned-to-contributor Contributor PR: CI red, changes requested or conflicting; diagnosis posted, author must act and removed stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Nov 6, 2026
@hivecommons-hive

Copy link
Copy Markdown
Contributor

@hanthor this PR is back in your court (stage/072-returned-to-contributor). The hive will not merge it until the head changes.

Review asks:

  • the review swarm requested changes

Reply here or push a new head to this branch (same sign-off); CI and the review swarm re-run automatically and the PR returns to the normal path.

Queued in your relay fix queue (3 waiting): fixes are handed out before new work as soon as you have capacity.

hanthor added a commit that referenced this pull request Nov 6, 2026
…created date

Review on #1132: the image config's created is SOURCE_DATE_EPOCH (last build-input commit), so a quiet weekend of green promotions would read as stale and a promotion after a long freeze as fresh. The check now finds the newest post-testing-e2e run whose promote-to-testing job ran the 'Move :testing to the tested digests' step, and treats none in the last 60 runs as stale.

Assisted-by: Claude Opus via omp
hanthor added a commit that referenced this pull request Nov 6, 2026
…created date

Review on #1132: the image config's created is SOURCE_DATE_EPOCH (last build-input commit), so a quiet weekend of green promotions would read as stale and a promotion after a long freeze as fresh. The check now finds the newest post-testing-e2e run whose promote-to-testing job ran the 'Move :testing to the tested digests' step, and treats none in the last 60 runs as stale.

Assisted-by: Claude Opus via omp
@hanthor
hanthor force-pushed the ci/testing-freshness-alarm branch from c788e1e to f82398f Compare November 6, 2026 19:40
@hivecommons-hive hivecommons-hive Bot added stage/050-review-pending Review swarm requested; awaiting a verdict for the current head and removed stage/072-returned-to-contributor Contributor PR: CI red, changes requested or conflicting; diagnosis posted, author must act labels Nov 6, 2026
hanthor and others added 3 commits November 6, 2026 20:43
:testing advances only when post-testing-e2e promotes it. A broken gate
therefore freezes the tag while every build stays green: from 2026-10-30 to
11-06 a missing provenance attestation stopped every promotion, and nothing
said so.

testing-freshness.yml runs every six hours. scripts/testing-freshness.py reads
each flavor's :testing creation time from the registry (skopeo inspect). When
any flavor is older than 36 hours (or its tag is unreadable), it opens one
issue labelled kind/bug, area/ci and priority/critical-urgent for the hive to
pick up. The issue body carries a per-flavor table and the latest
post-testing-e2e run with its failed jobs. Later runs refresh the same issue,
found by a body marker, and close it once every flavor is fresh again.

A dry run against the live registry flags all four flavors as stale (created
2026-10-30, 175 h ago) and names the latest e2e run's failed jobs.

Assisted-by: Claude Opus via omp
Signed-off-by: James Reilly <jreilly1821@gmail.com>
…created date

Review on #1132: the image config's created is SOURCE_DATE_EPOCH (last build-input commit), so a quiet weekend of green promotions would read as stale and a promotion after a long freeze as fresh. The check now finds the newest post-testing-e2e run whose promote-to-testing job ran the 'Move :testing to the tested digests' step, and treats none in the last 60 runs as stale.

Assisted-by: Claude Opus via omp
Signed-off-by: James Reilly <jreilly1821@gmail.com>
…thout search

The alarm still judges :testing by the completion time of the "Move :testing
to the tested digests" step in post-testing-e2e's promote-to-testing job, the
only writer of the tag. Nothing on the image can carry that time: the move is
skopeo copy --preserve-digests, and the config's created is SOURCE_DATE_EPOCH.

- Scan runs started within the threshold plus a day of slack, paginated,
  instead of the newest 60: a busy queue can no longer push a recent
  promotion out of view, and a freeze costs a bounded number of API calls.
- Find the open alarm issue through the REST issues listing (label area/ci
  plus the body marker). gh issue list --label/--search goes through issue
  search, whose index lag or HTML-comment handling could open duplicates.
- Run issue edit/close/create through a text helper: gh issue edit prints a
  URL, which the JSON helper would have failed to parse.
- Tests pin the job and step names to post-testing-e2e.yml, cover a run
  that promoted but failed a later job, a failed promote job, and the
  issue lookup.

Assisted-by: Claude Opus via GitHub Copilot
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: James Reilly <jreilly1821@gmail.com>
@hanthor
hanthor force-pushed the ci/testing-freshness-alarm branch from f82398f to 16a950d Compare November 6, 2026 20:45
@hanthor

hanthor commented Nov 6, 2026

Copy link
Copy Markdown
Member Author

New head 16a950d4, rebased on main with all three commits signed off. It addresses the review.

Freshness signal is now the promotion time. The script no longer uses the image's created. It reads post-testing-e2e runs through the Actions API, which needs only the job's existing actions: read. It uses the completed_at of the "Move :testing to the tested digests" step in the newest run whose promote-to-testing job ran that step. That job is the only writer of :testing. I chose the step over the alternatives for these reasons:

  • A promotion label or annotation on the image can't work. The move is skopeo copy --preserve-digests, so the promoted image is byte-identical to the tested one and can't record when it was promoted.
  • gh run list --status success is wrong in both directions. A run can move the tag and still fail a later job (testsuite/documentation), so it would look stale. A run can also pass while the ratchet holds the tag (the move step is skipped), so it would look fresh.

The script scans runs started within the threshold plus 24 h of slack, with pagination, instead of a fixed count. The concurrency group allows one pending run behind one running run, and recent runs finished within 2.5 h of being created. If no run in the window moved the tag, that counts as stale, never fresh. A new test checks that the job and step names still exist in post-testing-e2e.yml, so renaming either fails CI instead of silently raising the alarm.

Open question about search and HTML comments: the script no longer depends on search. It finds its issue through the REST issues listing (repos/…/issues?labels=area/ci) and filters by the body marker in Python. gh issue list --label would also have used issue search under the hood. While doing this I found and fixed a bug: gh issue edit prints a URL, which the JSON helper would have crashed on, so edit/close/create now use a plain-text helper.

Checks run: just check passes (1306 tests) and pre-commit run --all-files passes. Live dry runs on this head:

  • With the default 36 h threshold, it reports "No post-testing-e2e run started since 2026-11-04 08:37 UTC moved the tag". That is correct, because the tag has been frozen since 10-30.
  • With --max-age-hours 200, it reports ":testing last moved 2026-10-30 11:49 UTC; fresh", which matches promotion run 41043543296.

@hivecommons-hive hivecommons-hive Bot added dco All commits are DCO signed-off and removed no-dco A commit is missing Signed-off-by — run `git rebase --signoff` labels Nov 6, 2026

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Read the diff against the tree at 16a950d before the body. The mechanism in this head is sound; the PR body describes the previous one.

PR body is out of date. It says the script "reads each flavor's :testing creation time from the registry (skopeo inspect)" with a per-flavor table and "6 tests". The code on this head does none of that: scripts/testing-freshness.py:70-88 takes the completed_at of the "Move :testing to the tested digests" step in the newest completed post-testing-e2e run whose promote-to-testing job succeeded, and tests/test_testing_freshness.py has 12 tests (all pass locally). The new approach is the right one (the earlier review explained why created is SOURCE_DATE_EPOCH), and docs/skills/ci-workflows/references/iso-e2e.md already describes it correctly — only the body lags. Worth refreshing before merge since the squash message will carry it.

Verified against the tree:

  • post-testing-e2e.yml:373 defines promote-to-testing, :418 the step name, :429 the skopeo copy --all --preserve-digests … :testing write, matching PROMOTE_JOB / MOVE_STEP; SignalSourceTests pins all three so a rename fails CI.
  • tests/run_suite.py discovers every tests/test_*.py, so just test in build.yml runs the new file without wiring.
  • Labels kind/bug, area/ci, priority/critical-urgent exist, so gh issue create --label will not fail. open_issue() goes through the REST listing with select(.pull_request == null) and the body marker, not search — the open question from the earlier review is resolved.
  • is_stale(None, …) → True: no promotion in the 36 h + 24 h window reads as stale, never fresh.
  • Workflow: top-level permissions: {}, job scoped to contents: read, issues: write, actions: read, persist-credentials: false, checkout pinned by SHA, ubuntu-26.04 already used by 13 other workflows here.

Trust note for the record: this adds a scheduled workflow with issues: write on GITHUB_TOKEN. The author is an OWNERS approver and has already /approved, so I take that decision as made.

Confidence: 5/5 (safe)

— hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88

@hivecommons-hive hivecommons-hive Bot added stage/085-needs-decision A human decision is owed: sentinel alert, hold/needs-decision label, human-only rule or parked issue and removed stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Nov 7, 2026
@hivecommons-hive

hivecommons-hive Bot commented Nov 7, 2026 •

Copy link
Copy Markdown
Contributor

Needs a decision, not a merge:

  • the reviewer swarm returned requires_human @f8814f9
  • the review found: the security review withheld approval: Delta is merge-of-main only; workflow file unchanged. Previous finding (issues: write on github.token, line 30) still present. Verdict unchanged: requires_human.
  • reviewer summary: security requires human: Delta is merge-of-main only; workflow file unchanged. Previous finding (issues: write on github.token, line 30) still present. Verdict unchanged: requires_human.
  • the PR edits CI workflow / action files: awaiting owner approval — a hive owner / trusted merger's GitHub Approve review on the current head (or a /hive decision approve reply, typed on the PR or from the dashboard) releases the fence and the hive merges it; approval on an earlier head does not count, so re-approve after a push

Head: verdict requires_human @f8814f9, 20/20 checks green, soak 30m0s elapsed.

What to do: a trusted merger approves this head (f8814f9) with a GitHub Approve review (or a /hive decision approve reply, typed here or from the dashboard), which releases the CI workflow-file fence and settles the reviewer's requires_human verdict, and the hive merges the PR once the other gates clear; approval on an earlier head does not count, and a /hive approve reply does not release the fence.

Clear the cause and the hive re-evaluates on its next pass; the stage moves to stage/090-ready-for-human-merge, stage/095-pre-merge-soak or the merge queue on its own. Approval does not bypass CI, hold labels or other merge gates.

Updated 2026-11-07 16:35 UTC.

@hanthor

hanthor commented Nov 7, 2026

Copy link
Copy Markdown
Member Author

/hive decision approve

Owner approval for the workflow-file fence. The new workflow has permissions: {} at the top level, and the job gets only contents: read, issues: write and actions: read. It reads post-testing-e2e runs and opens or closes one issue; it pushes nothing and needs no secrets.

@hivecommons-hive hivecommons-hive Bot added the stage/050-review-pending Review swarm requested; awaiting a verdict for the current head label Nov 7, 2026
@hivecommons-hive

Copy link
Copy Markdown
Contributor

@hanthor approved head f8814f90cc65, which edits CI workflow / action files. Head 88f2ea9d2c5b is only the hive's own merge of the base branch into it — the PR's diff is unchanged — so that approval still releases the contributor lane's workflow-path fence: the hive merges this PR itself once the usual gates (CI, soak, holds, review verdict) are clear. Any other push re-arms the fence until the new head is approved again.

@hivecommons-hive hivecommons-hive Bot added stage/095-pre-merge-soak Lane admitted; the pre-merge soak window is running before the merge is attempted stage/050-review-pending Review swarm requested; awaiting a verdict for the current head and removed stage/050-review-pending Review swarm requested; awaiting a verdict for the current head stage/095-pre-merge-soak Lane admitted; the pre-merge soak window is running before the merge is attempted labels Nov 7, 2026
@hivecommons-hive

Copy link
Copy Markdown
Contributor

@hanthor approved head 88f2ea9d2c5b, which edits CI workflow / action files. Head bce9d6cf1f23 is only the hive's own merge of the base branch into it — the PR's diff is unchanged — so that approval still releases the contributor lane's workflow-path fence: the hive merges this PR itself once the usual gates (CI, soak, holds, review verdict) are clear. Any other push re-arms the fence until the new head is approved again.

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

HUMAN DECISION NEEDED — @hanthor confirm a maintainer accepts a scheduled workflow holding issues: write on the default token (unchanged since last review).

Summary: Re-review of the alarm that opens an issue when the :testing image stops being promoted. Since the last look the branch only picked up merges from main (dependency digest bumps, a docs note and a new ujust recipe); nothing in the alarm itself changed. The one open question is still whether the scheduled job may hold permission to create and close issues; the PR body says a maintainer approved that scope, and a human should confirm it.


Delta reviewed: f8814f9 → bce9d6c (7 commits, all Merge branch 'main'; PR files .github/workflows/testing-freshness.yml, scripts/testing-freshness.py, tests/test_testing_freshness.py, docs/skills/ci-workflows/references/iso-e2e.md unchanged).

security

  • Still present: .github/workflows/testing-freshness.yml:30 grants issues: write on github.token in a cron job (:11, :38). Top-level is permissions: {} (:19), checkout uses persist-credentials: false (:35), no secrets beyond github.token. PR body states this scope is maintainer-approved; confirm and this becomes approve.

Delta cross-check: main's post-testing-e2e.yml changes are testsuite digest bumps only; promote-to-testing job (post-testing-e2e.yml:373) and step "Move :testing to the tested digests" (:418) still match scripts/testing-freshness.py:44-45.

No findings from: correctness, intent-alignment, style, docs-currency.

Confidence: 3/5 (needs attention) — 1 medium finding; 1 perspective requires a human decision

— hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88

@hivecommons-hive hivecommons-hive Bot added stage/095-pre-merge-soak Lane admitted; the pre-merge soak window is running before the merge is attempted and removed stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Nov 7, 2026
@hivecommons-hive hivecommons-hive Bot added stage/050-review-pending Review swarm requested; awaiting a verdict for the current head and removed stage/095-pre-merge-soak Lane admitted; the pre-merge soak window is running before the merge is attempted labels Nov 7, 2026
@hivecommons-hive

Copy link
Copy Markdown
Contributor

@hanthor approved head bce9d6cf1f23, which edits CI workflow / action files. Head 1340bda95ca4 is only the hive's own merge of the base branch into it — the PR's diff is unchanged — so that approval still releases the contributor lane's workflow-path fence: the hive merges this PR itself once the usual gates (CI, soak, holds, review verdict) are clear. Any other push re-arms the fence until the new head is approved again.

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No correctness blocker found: scripts/testing-freshness.py:71-89 checks the actual successful move step, not the overall run conclusion or image creation date. The existing caller gates that step on main and the promotion ratchet, so skipped promotions do not count as fresh.

Final trust review remains with @castrojo: .github/workflows/testing-freshness.yml:28-40 adds a scheduled issues: write job that executes the checked-out script and can create, edit, and close its marked alarm issue. The PR body states this scope is already maintainer-approved; this is a final implementation review of that approved scope, not a request to redesign it. The sentinel notice and new workflow write permission warrant human sign-off before merge.

Confidence: 3/5 (needs attention) — 1 perspective requires a human decision

— hive: agent=reviewer backend=copilot model=gpt-6.1-sol copilot=1.0.88

@hivecommons-hive hivecommons-hive Bot added stage/095-pre-merge-soak Lane admitted; the pre-merge soak window is running before the merge is attempted and removed stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Nov 8, 2026
@hivecommons-hive

Copy link
Copy Markdown
Contributor

@hanthor approved head 1340bda95ca4, which edits CI workflow / action files. Head a4cb791a3c30 is only the hive's own merge of the base branch into it — the PR's diff is unchanged — so that approval still releases the contributor lane's workflow-path fence: the hive merges this PR itself once the usual gates (CI, soak, holds, review verdict) are clear. Any other push re-arms the fence until the new head is approved again.

@hivecommons-hive hivecommons-hive Bot added stage/050-review-pending Review swarm requested; awaiting a verdict for the current head stage/095-pre-merge-soak Lane admitted; the pre-merge soak window is running before the merge is attempted and removed stage/095-pre-merge-soak Lane admitted; the pre-merge soak window is running before the merge is attempted stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Nov 8, 2026
@hivecommons-hive
hivecommons-hive Bot merged commit fcfdc59 into main Nov 8, 2026
36 checks passed
@hivecommons-hive
hivecommons-hive Bot deleted the ci/testing-freshness-alarm branch November 8, 2026 02:06
@hivecommons-hive

Copy link
Copy Markdown
Contributor

Merged by hive contributor-lane auto-merge: CI green for ≥30m, reviewer verdict not required, @hanthor approved this head as the owner decision (admitted_by: operator-approval:hanthor) — merged as-is on that approval.

@hivecommons-hive hivecommons-hive Bot removed role/trusted Author is trusted for unattended merge (trusted-author role or registry/claim tier in require_tiers) stage/095-pre-merge-soak Lane admitted; the pre-merge soak window is running before the merge is attempted labels Nov 8, 2026
hanthor added a commit that referenced this pull request Nov 16, 2026
Owner policy: "if the :stable tag is over a week old and :testing passes,
we promote it". execute-release.yml now checks daily at 06:00 UTC instead
of every Monday. A scheduled run releases only when :stable last moved
more than seven days ago (or a flavor has no :stable yet) and :testing
points at a different digest for at least one flavor of
`scripts/flavors.py releases`; otherwise it posts a ::notice saying
whether age or nothing-new held it back. Promotion pushes and manual
dispatch are unchanged, and every release still goes through the
e2e-evidence gate and the release gate.

:stable's age is the completion of the reusable release's "Promote
digests to target tags" step in the newest execute-release run that
succeeded at it, read in batched GraphQL queries (checkType ALL so a
rerun cannot hide an earlier retag). Not the image config created
(SOURCE_DATE_EPOCH, the #1132 pitfall) and not the testing-YYYYMMDD
version label, which dates the build that was later released, per
flavor and to the day. The step retags every flavor or fails, so one
time dates them all and a partial failure keeps the oldest age.

Registry reads use skopeo inspect --no-tags: without it skopeo lists
every tag, over 30 s per image here.

Assisted-by: Claude Opus via GitHub Copilot
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: James Reilly <jreilly1821@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. author/clanker A contributor's own hive authored this PR under their login dco All commits are DCO signed-off

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant