Repository navigation
fix(release): track distributor changes and test release path policy - #11
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.
Why
The published distribution is influenced by
scripts/build_release.py, but the runtime-only release allowlist currently ignores it. A change to the builder can alter shipped ZIP contents without triggering a release.Changes
scripts/build_release.pyas a release-eligible path, while keeping documentation, tests and generic CI config excluded..github/release-paths.txtitself changes, to catch policy regressions in PRs.Safety
This PR only modifies CI policy files; these paths remain excluded from the runtime allowlist. After merge the automatic release job must be skipped. No manual tag or release is required. Merge after project CI and GitVersion checks pass.