// This skill should be used when the user asks to "generate release notes", "list upcoming release PRs", "summarize upcoming release", "/upcoming-release", or needs to know what changes are part of an upcoming release.
This skill should be used when the user asks to "update SDK", "bump SDK version", "pin SDK to a commit", "test unreleased SDK", "update agent-server image", "bump the version", "prepare a release", "what files change for a release", or needs to know how SDK packages are managed in the OpenHands repository. For detailed reference material, see references/docker-image-locations.md and references/sdk-pinning-examples.md in this skill directory.
This skill should be used when the user asks to "test a cross-repo feature", "deploy a feature branch to staging", "test SDK against OH Cloud", "e2e test a cloud workspace feature", "test provider tokens", "test secrets inheritance", or when changes span the SDK and OpenHands server repos and need end-to-end validation against a staging deployment.
| name | upcoming-release |
| description | This skill should be used when the user asks to "generate release notes", "list upcoming release PRs", "summarize upcoming release", "/upcoming-release", or needs to know what changes are part of an upcoming release. |
Generate a concise summary of PRs included in the upcoming release.
Two commit SHAs are required:
If the user does not provide both SHAs, ask for them before proceeding.
Run the script from the repository root with the --json flag:
.github/scripts/find_prs_between_commits.py <older-sha> <newer-sha> --json
Filter out PRs that are:
Categorize the remaining PRs:
Format the output with PRs listed under their category, including the PR number and a brief description.