Replace release.yaml with repo-template standard#62
Merged
Conversation
Full replacement of the old "Release on Version Tag" workflow with the standard "Release on Published Release" pipeline. Changes: - Trigger: tag push → GitHub Release published - Multi-stage validated pipeline (validate → build/test → pack → publish → release) - NuGet package verification and smoke testing - CycloneDX SBOM generation - Coverage reporting - persist-credentials: false on all checkouts - SHA-pinned third-party actions Co-Authored-By: Claude Opus 4.6 (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
Full replacement of the old "Release on Version Tag" workflow with the standard repo-template pipeline.
persist-credentials: false, SHA-pinned actions, repo-template guardTest plan
🤖 Generated with Claude Code