Skip to content

ci: skip tests and build for release-please PRs and their merges - #36

Open
shauneccles wants to merge 5 commits into
mainfrom
feat/version-scope
Open

shauneccles wants to merge 5 commits into
mainfrom
feat/version-scope

Conversation

@shauneccles

Copy link
Copy Markdown
Member

Problem

The release PR for 0.2.0-style bumps touches CHANGELOG.md, .release-please-manifest.json, the package version line in pyproject.toml and uv.lock, and the __version__ literal — none of which can change test outcomes or wheel bytes. The 18-cell test matrix (3 OS × 6 Python) plus the build job run anyway, then repeat on the merge to main.

Fix

A plan job computes version_only from the merge-base diff: true only when every file is release prose or every manifest hunk touches only name="audio-hotplug"-anchored version lines. test and build skip when set; lint always runs; tags/schedule/manual runs build everything; ci-passed fails if anything non-metadata was skipped without the signal.

Same semantics as ledfx-senders#15, samplerate-ledfx#35 and pyfastnoiselite-ledfx#14. Collapses to the shared release-ci action once LedFx/release-ci#15 lands.

Verification: actionlint and zizmor (--min-severity high) clean; detector logic identical to the version already green in the senders repo.

A release bump (changelog, manifest, the package's own version lines in
pyproject.toml/uv.lock, plus the __version__ literal) cannot change test
outcomes or built artifacts. The 18-cell test matrix and the build job
skip it on pull_request and on merges to main; renovate dependency and
lock bumps leave foreign anchors or lines and still run everything.

This branch has not been deployed

No deployments
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