ci(release): run the provenance job whenever the hashes exist - #102
Merged
Merged
Conversation
The first provenance-only dispatch hashed the assets and then skipped the generator: with the channel jobs skipped upstream, GitHub skips every dependant that does not say otherwise, whatever its direct dependency did. The job now runs whenever the hash job succeeded.
mescon
enabled auto-merge
September 14, 2026 21:18
|
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 first provenance-only dispatch (run 34897869341) hashed the 16 assets of v0.41.0 and then skipped the generator job, because GitHub propagates a skipped upstream job to every dependant without an explicit status check. The job now carries
if: !cancelled() && needs.hashes.result == 'success'.