From b548d43d8ef798a182ad895b6d90cd5fdf9b9e38 Mon Sep 17 00:00:00 2001 From: Yang Song Date: Tue, 23 Sep 2025 09:27:39 -0400 Subject: [PATCH] [chore] Update release.md --- docs/release.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/release.md b/docs/release.md index 83b83816a..1bd67ca05 100644 --- a/docs/release.md +++ b/docs/release.md @@ -11,7 +11,7 @@ For general information about all Collector repositories release procedures, see 0. Ensure that the [opentelemetry-collector][1] and [opentelemetry-collector-contrib][2] release procedures have been followed and a new opentelemetry-collector and opentelemetry-collector-contrib version have been released. The opentelemetry-collector-releases release should be done after both of these releases. -1. Review and merge the 2 Renovate PRs for core and contrib components, including OCB. If they were not created or updated yet, you can go to the **Dependency Dashboard** GitHub issue and check the boxes for the updates or for a manual Renovate run to expedite the process. +1. Review and merge the Renovate PR for core and contrib components, including OCB. If they were not created or updated yet, you can go to the **Dependency Dashboard** GitHub issue and check the boxes for the updates or for a manual Renovate run to expedite the process. 2. Run the GitHub Action workflow "[Update Version in Distributions and Prepare PR](https://github.com/open-telemetry/opentelemetry-collector-releases/actions/workflows/update-version.yaml)" which will update the minor version automatically (e.g. v0.116.0 -> v0.117.0) or manually provide a new version if releasing a bugfix or skipping a version. Select "create pr" option. The PR needs to be manually closed and re-opened once to trigger pipelines. - 🛑 **Do not move forward until this PR is merged.** 🛑