From 5171284f5890f799bf37f54c8d888f2a53027523 Mon Sep 17 00:00:00 2001 From: Aaron Abbott Date: Thu, 16 Oct 2025 16:57:08 +0000 Subject: [PATCH] Updating release docs to make it clear that it's ok to merge your own individual package release PRs --- RELEASING.md | 1 + 1 file changed, 1 insertion(+) diff --git a/RELEASING.md b/RELEASING.md index b8d4b56bcf..05aca72d79 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -37,6 +37,7 @@ to pick a specific package to release. It follows the same versioning strategy a Long-term package release branch follows `package-release/{package-name}/v{major}.{minor}.x` (or `package-release/{package-name}/v{major}.{minor}bx`) naming pattern. The workflow will create two pull requests, one against the `main` and one against the `package-release/` branch; both should be merged in order to proceed with the release. +To keep the process lightweight, it's OK to approve the PRs you generate and merge without additional reviews. ## Preparing a new patch release