Repository navigation
ci(publish): use GitHub App token for release commit-back - #6
Merged
Merged
Conversation
…otection The stable-release commit-back + tag push must bypass the protected-main ruleset (PR required). GITHUB_TOKEN cannot; a GitHub App installation token can. Adds the create-github-app-token step and uses it for checkout/push. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ProduceReferenceAssembly=false only moved the missing file from ref/ to bin/; the parallel multi-TFM ProjectReference race persisted. Building with a single MSBuild node forces dependency-ordered builds and eliminates it deterministically. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
lgalluzzi2823
approved these changes
Jul 10, 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
2 participants
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
Uniforms the NuGet publish workflow with the client (npm) repo: the stable-release
version commit-back and `v` tag push are now authenticated with a GitHub App
installation token instead of `GITHUB_TOKEN`.
Why
`main` has a branch-protection ruleset (PR + CI required). The built-in `GITHUB_TOKEN`
cannot bypass it, so the automated commit-back on stable releases would fail. A GitHub App
token can bypass the rule.
Changes
Required secrets
(plus `NUGET_API_KEY` for the actual publish)
🤖 Generated with Claude Code