Draft
Split PyPI release into per-platform tag workflows with scm-pinned wheel publishing#77
Conversation
Copilot
AI
changed the title
[WIP] Add PyPI release workflow for tag-triggered builds
Split PyPI release into per-platform tag workflows with scm-pinned wheel publishing
Jul 24, 2026
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.
This changes the release path from a single tag-driven publish workflow to independent Linux/macOS/Windows wheel pipelines that each build, test, and publish on bare
X.Y.Ztags. It also moves package versioning tosetuptools-scmso tag builds publish the tag version consistently and reject mismatched wheel artifacts before upload.Per-platform release workflows
build.ymlfor Linuxbuild-macos.ymlbuild-windows.ymlbuild-wheel -> test-wheel -> publishconcurrencyandpaths-ignoreso platform pipelines rerun independently and avoid unnecessary CI burnWheel-first release behavior
skip-existingfor idempotent rerunsVersioning hardening
pyproject.tomltoscikit_build_core.metadata.setuptools_scmsetuptools-scmto build requirements andlocal_scheme = "no-local-version"SETUPTOOLS_SCM_PRETEND_VERSION_FOR_COMPAS_CGALon tag builds so CI-side tree mutations cannot producedevreleases__version__Publish-time safety checks
GITHUB_REF_NAMEbefore upload