ci(release): add manual trusted-publishing release workflow#20
Merged
Conversation
Mirror fiberpath's workflow_dispatch release pattern, trimmed for a zero-dependency pure-Python library: validate (semver + tag-free + version matches pyproject.toml and __init__.py) then build, tag, GitHub Release (auto notes + wheel/sdist), and PyPI trusted publish. No SBOM matrix or installer build — nothing to package beyond the wheel.
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.
What
Adds
.github/workflows/release.yml— a manual (workflow_dispatch) release pipeline somarlin-hostcan ship to PyPI, the prerequisite for fiberpath depending on a pinned release instead of its in-repoexecution/marlin.py.Deliberately leaner than fiberpath's release workflow (which carries an SBOM trio + Tauri installer matrix).
marlin-hostis a zero-dependency pure-Python library, so:vX.Y.Zis free, and input version matches bothpyproject.tomlandmarlin_host.__version__(guards the two-source drift)uv build→ push tag → GitHub Release (auto-generated notes + wheel/sdist attached) → PyPI trusted publishing (OIDC,pypienvironment)Before the first run (manual, PyPI-side)
Configure a pending publisher on PyPI so trusted publishing resolves for the new project:
marlin-hostfiberpathmarlin-hostrelease.ymlpypiNotes
check.yml(lint/type/test/codegen-drift) is unaffected.