Skip to content

chore: do not trigger release when only tests file are updated#124

Merged
ryanking13 merged 1 commit into
mainfrom
gyeongjae/cli-release-tests
Jun 16, 2026
Merged

chore: do not trigger release when only tests file are updated#124
ryanking13 merged 1 commit into
mainfrom
gyeongjae/cli-release-tests

Conversation

@ryanking13

Copy link
Copy Markdown
Contributor

I often found that updating runtime-sdk triggers workers-py release, because of updating the cli/tests directory. This prevents it.

@ask-bonk

ask-bonk Bot commented Jun 15, 2026

Copy link
Copy Markdown

The change is straightforward: it adds "!tests/**" to the path_filters for the CLI's semantic release commit parser, so that commits touching only files under the tests/ directory won't trigger a release.

The logic is correct — path_filters in python-semantic-release supports negation patterns with !, and "!tests/**" will exclude any file under the tests/ directory from being considered when determining whether a commit should trigger a version bump.

The change is minimal, targeted, and the motivation (preventing spurious releases when only test files change) is sound. No bugs, no security concerns, no backward compatibility issues.

LGTM

github run

@ryanking13 ryanking13 merged commit e946633 into main Jun 16, 2026
14 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.

2 participants