Repository navigation
A scheduled reissue before the first release ends quietly - #166
Merged
Merged
Conversation
…nt key and no statement served is nothing to sign again, while a publish without the key, or a served statement without it, still fails
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
1 participant
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 Update channel workflow's daily schedule fails every morning until the statement key is in the KRYPTIK_LATEST_KEY secret, which happens at the first production release: a red run a day that means nothing. Now a run without the key first asks whether the site serves a statement for the channel: none served and no release named means there is nothing to sign again, and the run ends without deploying. A publish without the key, or a served statement without it (which would go stale), still fails with the same message as before. The workflow has no push trigger, so this is proved by dispatching a reissue from main after the merge.