Skip costly fuzz and release jobs for unrelated changes - #535
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.
A fuzz README edit rebuilt every fuzz harness, and every pull request started the six-platform release matrix. We limit fuzz PR and main-branch runs to harness/build/seed inputs and release PR runs to source, build configuration, and packaged README/license files. Manual and scheduled fuzz runs retain their existing triggers.
cargo-dist 0.32 cannot configure PR paths, so we preserve the local release filter with allow-dirty = ["ci"] and document regeneration. This disables its generated-workflow freshness check; configuration changes require regenerating and reviewing the workflow. The pinned cargo-dist release plan succeeds with all six targets and 17 artifacts, and path checks cover both build changes and documentation-only changes.