ci: replace publish workflow with tag-triggered release pipeline#38
Merged
Conversation
scarmuega
force-pushed
the
ci/release-pipeline
branch
from
c913244 to
a26c691
Compare
Replaces the GitHub-Release-triggered publish.yml and the publish.sh script with a release workflow conforming to the umbrella SDK release pipeline contract (u5c-factory reference/sdk-pipeline.md): a v* version tag triggers verify -> build -> test -> publish. The verify job checks the pushed tag against the Utxorpc.Sdk.csproj version and fails the release if they disagree; publish pushes to NuGet. Verification: workflow YAML syntactically validated only; not executed and the package not built this session. Requires the NUGET_REGISTRY_TOKEN repository secret (replacing NUGET_API_KEY) 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
a26c691 to
e23aa26
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
Replaces the GitHub-Release-triggered
publish.ymland thepublish.shscript with arelease.ymlconforming to the umbrella SDK release pipeline contract (u5c-factory→reference/sdk-pipeline-requirements.md).v*version tag (was:release: published)verify→build→test→publish, each gating the nextverifyjob checks the pushed tag against theUtxorpc.Sdk.csprojversion and fails the release on mismatch — the manifest is the source of truth; the workflow never edits it--skip-duplicateVerification
Workflow YAML syntactically validated only. Not executed and the package not built this session — the pipeline can only be exercised by a real tag push.
Notes
main, independent of the in-flightfeat/spec-v0.19branch.NUGET_REGISTRY_TOKENrepository/org secret (a nuget.org API key) must exist before the first release — this replaces the oldNUGET_API_KEYsecret.