fix: remove paths-ignore from release.yml so content-only changes still gate releases on commit prefix#53
Merged
TMHSDigital merged 1 commit intomainfrom Apr 26, 2026
Conversation
…ll gate releases on commit prefix Closes DTD#50. Mirrors DTD#47 pattern fixed across the tool repos. The previous paths-ignore block excluded `*.md`, `docs/`, `standards/`, `LICENSE`, and `release-drafter.yml` from triggering the workflow, but the meta-repo's release.yml uses VERSION-vs-latest-tag semantics (not commit-prefix). The result was content edits to standards/ or docs/ that bumped VERSION still got skipped at trigger time. Removing the block lets every push to main reach the workflow; the VERSION-vs-tag check then correctly decides whether to release. Bumps VERSION 1.9.4 -> 1.9.5 to validate the fix end-to-end (this very commit will both bump VERSION and previously would have been excluded; with the fix it should fire and release v1.9.5). Made-with: Cursor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
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.
Closes DTD#50. Mirrors the DTD#47 surgery already applied across all eight tool repos (CFX, Unity, Docker, Home-Lab, Monday, Steam-Cursor, Blender, Plaid).
The bug
The meta-repo's
release.ymlwas the only release workflow in the ecosystem still carrying apaths-ignoreblock:This was load-bearing under the old commit-prefix-driven release model (where docs/standards changes shouldn't fire a bump), but the meta-repo's release workflow now uses VERSION-vs-latest-tag detection (DTD#23). Under that model:
paths-ignoreblock silently swallowed exactly this case if the commit only touched paths in the ignore list.The asymmetry: the workflow's own decision logic is correct and self-defending, but the trigger filter prevented it from running in the very case where it would have made the right call.
The fix
Remove
paths-ignoreentirely. Every push tomainreaches the workflow; the VERSION-vs-tag check decides whether to release.Diff shape
release.yml: minus 6 lines (paths-ignore block).VERSION: 1.9.4 -> 1.9.5 (PATCH bump for workflow config fix; also serves as end-to-end verification - this very commit, which only touches workflow YAML, was previously excluded by the old filter).Verification plan
After merge, the workflow should:
If the workflow does NOT fire, that's a regression in this same fix and I'll report immediately.
Cross-reference
DTD#47 (tool-repo paths-ignore removal) and DTD#51 (release-doc-sync staging fix) both landed earlier this session. After this merges, the entire ecosystem's release-trigger and release-staging behavior is uniform and correct.
Closes #50.