modelcontextprotocol/csharp-sdk
Watch
1
0
Fork
You've already forked csharp-sdk
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

Update release processes to support release servicing branches (#1620)

Browse source 
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
Jeff Handley 2026-06-03 01:35:15 -07:00 • committed by GitHub
commit bc372f18c6
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 199 additions and 86 deletions
Download patch file Download diff file Expand all files Collapse all files

28
.github/skills/bump-version/SKILL.md vendored
View file

@ -8,18 +8,21 @@ compatibility: Requires gh CLI with repo access for creating branches and pull r
Assess and bump the SDK version in `src/Directory.Build.props` to prepare for the next release. This skill owns the [Semantic Versioning 2.0.0](https://semver.org/spec/v2.0.0.html) assessment logic — the [SemVer assessment guide](references/semver-assessment.md) is the single source of truth for version assessment criteria used across the release workflow by both the **prepare-release** and **publish-release** skills.
Use the shared [release branch reference](../shared-resources/release-branches.md) for branch roles, previous-release lookup rules, and release work-branch naming.
> **Note**: For comprehensive release preparation — including ApiCompat/ApiDiff, documentation review, and release notes — use the **prepare-release** skill, which incorporates version assessment as part of its broader workflow.
## Process
### Step 1: Read Current Version and Previous Release
Read `src/Directory.Build.props` on the default branch and extract:
Read `src/Directory.Build.props` on the current branch and extract:
- `<VersionPrefix>` — the `MAJOR.MINOR.PATCH` version
- `<VersionSuffix>` — the prerelease suffix, when present
Display the current version to the user.
The candidate version is `{VersionPrefix}` plus `-{VersionSuffix}` when the suffix is present (for example, `2.0.0-preview.1`). Display the current candidate version to the user.
Determine the previous release tag from `gh release list` (most recent **published** release). Draft releases must be ignored — they represent a pending release that has not yet shipped. Use `--exclude-drafts` or filter to only published releases when querying.
Determine the previous release tag from `gh release list` (most recent **published** release). Draft releases must be ignored — they represent a pending release that has not yet shipped. Use `--exclude-drafts` or filter to only published releases when querying. The lookup is branch-aware: from a `release/{MAJOR}.x` branch, restrict candidates to tags matching `v{MAJOR}.*`; from `main`, use the most recent published release globally. See [release-branches.md](../shared-resources/release-branches.md) for details.
### Step 2: Assess and Determine Next Version
@ -40,26 +43,31 @@ When context about queued changes is available or can be gathered, assess the ve
#### Default Suggestion (Fallback)
When a quick bump is needed without full change analysis, suggest the next **minor** version:
When a quick bump is needed without full change analysis, suggest based on the candidate version:
- Current `1.0.0` → suggest `1.1.0`
- Current `1.2.3` → suggest `1.3.0`
- **Stable candidate** — suggest the next **minor** version:
- Current `1.0.0` → suggest `1.1.0`
- Current `1.2.3` → suggest `1.3.0`
- **Prerelease candidate** — if the suffix starts with an identifier such as `preview.` or `rc.` followed by an integer, suggest incrementing the trailing integer:
- Current `2.0.0-preview.1` → suggest `2.0.0-preview.2`
- Current `2.0.0-rc.1` → suggest `2.0.0-rc.2`
Present the suggestion and let the user confirm or provide an alternative.
Parse the confirmed version into its `VersionPrefix` component.
Parse the confirmed version into its `VersionPrefix` and `VersionSuffix` components. Stable versions have no suffix.
### Step 3: Create Pull Request
1. Create a new branch named `bump-version-to-{version}` (e.g. `bump-version-to-1.1.0`) from the default branch
1. Create a new branch named `bump-version-to-{version}` (e.g. `bump-version-to-1.1.0`) from the current branch
2. Update `src/Directory.Build.props`:
- Set `<VersionPrefix>` to the new version
- Set `<VersionPrefix>` to the confirmed stable component
- Set `<VersionSuffix>` for prerelease versions, or clear it for stable versions; add the element if it is missing
- Update `<PackageValidationBaselineVersion>` if the MAJOR version has changed
3. Commit with message: `Bump version to {version}`
4. Push the branch and create a pull request:
- **Title**: `Bump version to {version}`
- **Label**: `infrastructure`
- **Base**: default branch
- **Base**: the current branch (which, for a servicing branch like `release/1.x`, is that servicing branch — not `main`)
### Step 4: Confirm