Skip to content

test(release): protect runtime-only automatic publication rules - #11

Merged
DiegoV71 merged 1 commit into
mainfrom
test/release-eligibility-contracts-20261107
Nov 7, 2026
Merged

DiegoV71 merged 1 commit into
mainfrom
test/release-eligibility-contracts-20261107

Conversation

@DiegoV71

@DiegoV71 DiegoV71 commented Nov 7, 2026

Copy link
Copy Markdown
Contributor

Problem

A regression in .github/release-paths.txt could cause a missing automatic GitHub Release after a runtime edit, or an unwanted release from a README, tests or CI-only change.

Change

  • Add a self-contained unittest contract against the real checked-in release allowlist using the same fnmatch.fnmatchcase rules as the pinned shared 4FusionLab classifier.
  • Validate shipped add-in / catalog / packaging inputs, excluded documentation and tests, mixed commits, removal and rename path semantics.
  • Keep all existing build, platform checks, GitVersion 6.8.2, package paths and publish gates unchanged.

Verification & release safety

  • Existing Python test discovery will execute this test in ordinary PR CI.
  • The only edited file is tests/test_release_paths.py; it is not in the runtime release allowlist. Merging must skip the release job.
  • No tags, releases, runtime source or distribution builders are modified.

@DiegoV71
DiegoV71 merged commit 479babf into main Nov 7, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant