ci: rework release workflow as tag-triggered pipeline#10
Merged
Conversation
Reworks release.yml to conform to the umbrella SDK release pipeline contract (u5c-factory reference/sdk-pipeline-requirements.md): a v* version tag triggers verify -> build -> test -> publish. The verify job checks the pushed tag against the pyproject.toml version and fails the release if they disagree. Also fixes the previous workflow, which referenced an undefined inputs.registry-token in a non-workflow_call workflow so the PyPI token always resolved empty. Verification: workflow YAML syntactically validated only; not executed this session. Requires the PYPI_REGISTRY_TOKEN repository secret before the first release. Based on main, independent of the in-flight spec-0.19 branch.
scarmuega
force-pushed
the
ci/release-pipeline
branch
from
dab9811 to
dc9f7f9
Compare
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
Reworks
release.ymlto conform to the umbrella SDK release pipeline contract (u5c-factory→reference/sdk-pipeline-requirements.md).v*version tagverify→build→test→publish, each gating the nextverifyjob checks the pushed tag against thepyproject.tomlversion and fails the release on mismatch — the manifest is the source of truth; the workflow never edits itFixes a broken workflow: the previous
release.ymlreferenced an undefinedinputs.registry-tokenin a non-workflow_callworkflow, so the PyPI token always resolved empty. It also had no checkout, build, or test.Verification
Workflow YAML syntactically validated only. Not executed this session.
Notes
main, independent of the in-flightfix/spec-0.19-protobufbranch.PYPI_REGISTRY_TOKENrepository/org secret (a PyPI API token) must exist before the first release.