From 7ec441bb3a5da36cf605a78b2a518c1e27738d9c Mon Sep 17 00:00:00 2001 From: Trask Stalnaker Date: Wed, 19 Oct 2022 03:56:35 -0700 Subject: [PATCH] Update releasing doc (#6911) Something I learned today... --- RELEASING.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/RELEASING.md b/RELEASING.md index 1c24c9117964..ee6964911b71 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -41,6 +41,10 @@ and deadlocks. e.g. `release/v1.9.x`, then enter the pull request number that you want to backport, then click the "Run workflow" button below that. * Review and merge the backport pull request that it generates. + * Note: if the PR contains any changes to workflow files, it will have to be manually backported, + because the default `GITHUB_TOKEN` does not have permission to update workflow files (and the + `opentelemetrybot` token doesn't have write permission to this repository at all, so while it + can be used to open a PR, it can't be used to push to a local branch). * Merge a pull request to the release branch updating the `CHANGELOG.md`. * The heading for the unreleased entries should be `## Unreleased`. * Run the [Prepare patch release workflow](https://github.com/open-telemetry/opentelemetry-java-instrumentation/actions/workflows/prepare-patch-release.yml).