Repository navigation
Retry the cosign install once in the release integrity check - #274
Merged
Merged
Conversation
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.
The scheduled release integrity check failed on 2026-11-09 because downloading cosign returned 504 four times, so the check itself never ran and #272 was opened. A manual run right after (https://github.com/Hodeitek/hodeishield-cli/actions/runs/42585947495) verified every release and image, and closed #272.
The install step now continues on error, waits 60 seconds and installs cosign once more; if that also fails, the check step fails as before and the issue is opened.
docs/release-signing.mdsays so.Refs #272