chore: consolidate release and publish into single multi-job workflow#8
Merged
Merged
Conversation
Copilot
AI
changed the title
[WIP] Update GitHub Actions release/publish workflow setup
chore: consolidate release and publish into single multi-job workflow
Jun 15, 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.
Releases created by
release-please-actionviaGITHUB_TOKENdon't reliably trigger downstreamon: releaseworkflows, causing the publish step to never run automatically.Changes
.github/workflows/release.yml— rewritten as a two-job pipeline:release-pleasejob: runs on push tomain, exposes manifest path-scoped outputspublishjob: gated once vianeeds/ifonrelease_created == 'true'; runs checkout → build → test → pack → NuGet publish → GitHub release upload → PR label.github/workflows/publish.yml— deleted; replaced by thepublishjob aboveworkflow_dispatchremoved; no manual trigger needed in the new designPermissions are job-scoped rather than workflow-level