ci: only run publish-pypi on real releases, not every main merge#4632
Merged
Conversation
Remove the `push: branches: [main]` trigger from publish-pypi.yml so the cross-platform wheel build and test matrix no longer run on every merge to main. The publish job was already gated to release/workflow_dispatch, so pushes only wasted CI. Build/PR validation remains covered by build.yml. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Summary
publish-pypi.ymltriggered on every push tomain, kicking off the full cross-platform wheel build (linux/musllinux/windows/macos/sdist) plus the test matrix — on every merge. The actualreleasepublish job was already gated torelease/workflow_dispatch, so pushes built and tested everything only to skip publishing. Wasted CI on every merge.This removes the
push: branches: [main]trigger so the workflow only runs on:release: [published]— a real new release (the intended path)workflow_dispatch— manual runsOrdinary build/PR validation is still covered by
build.yml, which runs on push tomainand PRs.Note: version is derived via
dunamai ... --latest-tag, so releases should continue to be cut by publishing a GitHub Release (which creates the tag) — exactly therelease: publishedevent that still triggers this workflow.🤖 Generated with Claude Code