From a12d8163d76a141a0408497f0b43fb9dc189c10d Mon Sep 17 00:00:00 2001 From: Azure SDK Bot <53356347+azure-sdk@users.noreply.github.com> Date: Wed, 22 Oct 2025 10:09:43 -0700 Subject: [PATCH] Make SDK Release Steps common (#6802) Co-authored-by: Summer Warren --- .../copilot/sdk-release.instructions.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 eng/common/instructions/copilot/sdk-release.instructions.md diff --git a/eng/common/instructions/copilot/sdk-release.instructions.md b/eng/common/instructions/copilot/sdk-release.instructions.md new file mode 100644 index 000000000..e9b9f62ca --- /dev/null +++ b/eng/common/instructions/copilot/sdk-release.instructions.md @@ -0,0 +1,19 @@ +# SDK release + +There are two tools to help with SDK releases: +- Check SDK release readiness +- Release SDK + +## Check SDK Release Readiness +Run `CheckPackageReleaseReadiness` to verify if the package is ready for release. This tool checks: +- API review status +- Change log status +- Package name approval(If package is new and releasing a preview version) +- Release date is set in release tracker + +## Release SDK +Run `ReleasePackage` to release the package. This tool requires package name and language as inputs. It will: +- Check if the package is ready for release +- Identify the release pipeline +- Trigger the release pipeline. +User needs to approve the release stage in the pipeline after it is triggered. \ No newline at end of file