Repository navigation
test(release): protect runtime-only automatic publication rules - #14
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.
Problem
A regression in
.github/release-paths.txtcould cause a missing automatic GitHub Release after a runtime edit, or an unwanted release from a README, tests or CI-only change.Change
unittestcontract against the real checked-in release allowlist using the samefnmatch.fnmatchcaserules as the pinned shared 4FusionLab classifier.Verification & release safety
tests/test_release_paths.py; it is not in the runtime release allowlist. Merging must skip the release job.