-
Notifications
You must be signed in to change notification settings - Fork 25
Prep for v1.4.0 release #130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
berndverst
merged 5 commits into
microsoft:main
from
andystaples:andystaples/1.4.0-release-prep
Apr 8, 2026
Merged
Changes from 3 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
3a4a883
Prep for 1.4.0
andystaples 91db716
Remove committed release drafts and update release-prep skill
andystaples 4767354
Update skill ordering
andystaples f06f3ee
Better changlog syntax, agent instructions
andystaples ca132c3
Focus CHANGELOGS to user-facing
andystaples File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,107 @@ | ||
| --- | ||
| name: release-prep | ||
| description: >- | ||
| Prepare a release for durabletask and durabletask.azuremanaged. Use when the | ||
| user asks for release prep, version bumping, changelog updates, or release | ||
| body drafting. Trigger phrases include: release prep, prepare vX.Y.Z, | ||
| changelog for release, and draft GitHub release notes. | ||
| --- | ||
|
|
||
| # Release Prep | ||
|
|
||
| This skill prepares a coordinated release for both packages in this repository: | ||
|
|
||
| - `durabletask` | ||
| - `durabletask.azuremanaged` | ||
|
|
||
| The skill accepts a target version (for example `1.4.0`) and performs the | ||
| required changes consistently. | ||
|
|
||
| ## Inputs | ||
|
|
||
| - `version`: Target semantic version (for example `1.4.0`) | ||
| - Optional: `baseTag` overrides for comparison if tags are non-standard | ||
|
|
||
| If `version` is not provided, ask the user before continuing. | ||
|
|
||
| ## Steps | ||
|
|
||
| ### 1. Determine source range and collect commits | ||
|
|
||
| - Root package range: `v<previousVersion>..HEAD` | ||
| - Azure managed package range: `azuremanaged-v<previousVersion>..HEAD` | ||
| - Use commit subjects and touched files to classify each change as: | ||
| - `durabletask` only | ||
| - `durabletask.azuremanaged` only | ||
| - shared/infra/docs changes | ||
|
|
||
| ### 2. Update package versions | ||
|
|
||
| Update both project versions: | ||
|
|
||
| - `pyproject.toml` -> `version = "<version>"` | ||
| - `durabletask-azuremanaged/pyproject.toml` -> `version = "<version>"` | ||
|
|
||
| Update azuremanaged dependency floors: | ||
|
|
||
| - `durabletask>=<version>` | ||
| - `durabletask[azure-blob-payloads]>=<version>` | ||
|
|
||
| ### 3. Update changelogs | ||
|
|
||
| - Add a new `## v<version>` section directly under `## Unreleased` in: | ||
| - `CHANGELOG.md` | ||
| - `durabletask-azuremanaged/CHANGELOG.md` | ||
| - Ensure all commits since the previous release tags are represented. | ||
| - Keep entries concise and grouped by type (`ADDED`, `CHANGED`, `FIXED`, `REMOVED`) where | ||
| applicable. | ||
|
|
||
| ### 4. Validate | ||
|
|
||
| - Run diagnostics on changed markdown and TOML files. | ||
| - Fix formatting or heading issues introduced by release prep changes. | ||
| - Verify the final diff only contains release-prep updates. | ||
|
|
||
| ### 5. Wait for merge and tags before release drafting | ||
|
|
||
| Before creating draft releases in GitHub UI, require explicit user | ||
| confirmation of both conditions: | ||
|
|
||
| - The version-bump/release-prep PR is merged | ||
| - Tags `v<version>` and `azuremanaged-v<version>` already exist in the target | ||
| repository | ||
|
|
||
| If either condition is not met, stop after preparing release body text and ask | ||
| the user to confirm once merge and tags are complete. | ||
|
|
||
| ### 6. Draft GitHub release bodies | ||
|
|
||
| Draft two release body texts for the GitHub Releases UI (do not add files to | ||
| the repository): | ||
|
|
||
| - Tag: `v<version>` | ||
| - Tag: `azuremanaged-v<version>` | ||
|
|
||
| Match existing release structure: | ||
|
|
||
| - Title (`# v<version>` or `# azuremanaged-v<version>`) | ||
| - `## What's Changed` | ||
| - `## External Links` | ||
| - `### Contributors` | ||
|
|
||
| Include: | ||
|
|
||
| - PyPI link for the exact release version | ||
| - Full changelog compare link | ||
| - Contributor handles from the commit range | ||
| - Keep drafts in the assistant response (or PR comment) so they can be pasted | ||
| directly into the Releases section | ||
|
|
||
|
|
||
| ## Output | ||
|
|
||
| Return a short summary with: | ||
|
|
||
| - Updated files | ||
| - Commit coverage confirmation | ||
| - Any manual follow-ups (for example, tag creation or publishing) |
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
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
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.