docs: document the NuGet release process in AGENTS.md - #665
Merged
Conversation
Derived from reading .github/workflows/release.yml and gh release history while cutting 2.4.1 — record it so it doesn't need re-deriving each time: the version comes entirely from the published GitHub Release's tag name (no file to bump), only a *published* Release triggers the workflow, and publishing is irreversible so the merge/CI state should be confirmed first. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
rexm
enabled auto-merge
August 7, 2026 01:10
|
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
While cutting the upcoming 2.4.1 patch release (fixing #660 and #661), had to read through
.github/workflows/release.ymland prior release history to reconstruct how releases actually work here. Recording it inAGENTS.mdso that's a one-time cost instead of a recurring one.Key facts captured:
github.event.release.tag_name) — there's no version to bump in any.csproj/Directory.Build.props.release: publishedevent triggers the workflow — a tag alone, or a draft release, does nothing.vprefix (2.4.0, notv2.4.0).Test plan
N/A — documentation only.
🤖 Generated with Claude Code