Repository navigation
ci: check the public alias tags anonymously in the release - #698
Open
SushaanthSrinivasan wants to merge 1 commit into
Open
SushaanthSrinivasan wants to merge 1 commit into
SushaanthSrinivasan wants to merge 1 commit into
Conversation
Add the verify-alias-tags job to release.yml, after publish-alias-tags. Like verify-image, it has no environment, no secrets and no way to get AWS credentials. It reads every alias tag with no credentials until it shows build's digest. Add verify-public-image.sh alias-tags. It checks the six alias tags and the list of digests the aliases pointed to before this run, then reads each alias's digest header with the same pacing and retry budget as version-tags. An alias that is not found, or on one of those digests, is read again. Any other digest stops the check at once. Extend the no-credentials test to the new job, add a test for its needs, permissions and inputs, and add tests for the new command. The header re-run guide now covers the new job.
SushaanthSrinivasan
requested a deployment
to
code-review
October 23, 2026 00:41 — with
GitHub Actions
Waiting
6 of 10 tasks
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## ci/release-alias-tags #698 +/- ##
======================================================
Coverage 61.62% 61.62%
======================================================
Files 11 11
Lines 740 740
======================================================
Hits 456 456
Misses 265 265
Partials 19 19 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This branch is waiting to be deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Why is this change being made?
What is changing?
verify-alias-tagsjob inrelease.yml(new), afterbuild,publish-version-tagsandpublish-alias-tags:id-tokenpermission, no environment and no secrets, the same asverify-image. Its only actions are harden-runner and checkout, withpersist-credentials: false.AWS_EC2_METADATA_DISABLED: 'true'on the check step.contents: read, a 15 minute timeout, the repo guard, andubuntu-24.04.verify-public-image.sh alias-tags(new command):version-tags.ALIAS_TAGSis the six alias tags, latest last, with therehearsal-<run id>-prefix on a practice run.publish-alias-tags'previousDigestsoutput): a JSON list of null orsha256:<64 hex>entries, none of them the tested digest.Only the digest header is read for each alias.
verify-imagealready checked the index and every image behind that digest.The retry budget is the one
version-tagsuses: up to 8 reads per alias, pausing 2, 4, 8, 16, 30, 30 and 30 seconds.GitHub settings
Related Links
Testing
How was this tested?
verify-public-image.batsandrelease-yaml.batstests.release.yml. actionlint: no new complaints.When testing locally, provide testing artifact(s):
Reviewee Checklist
Update the checklist after submitting the PR
If not, why:
If not, why:
If not, why: waiting on CI for this PR
If not, why: no Go code changes
If not, why: the new job runs only in the Release workflow; it will be tried with a practice run
If not, why:
If not, why:
If not, why:
If not, why: not needed; nothing user facing changes
If not, why: none
Reviewer Checklist
All reviewers please ensure the following are true before reviewing:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.