[PR #3151] [CLOSED] docs(releasing): make compatibility review version-agnostic #5644

New issue

Closed

opened 2026-10-31 01:08:13 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-31 01:08:13 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/3151
Author: @L00PLeGeNd
Created: 10/14/2026
Status: ❌ Closed

Base: main ← Head: docs/releasing-compatibility-review-version-agnostic

📝 Commits (1)

db34619 docs(releasing): make compatibility review version-agnostic

📊 Changes

1 file changed (+5 additions, -2 deletions)

View changed files

📝 docs/releasing.md (+5 -2)

📄 Description

Summary

Rewrite the compatibility-review step in docs/releasing.md so it applies to the release under preparation, not a past 6.2 candidate.
Keep the 6.1→6.2 migration guide linked as historical reference for that earlier release pair.
No product behavior changes.

Fixes #3058

Test plan

Read docs/releasing.md#compatibility-and-version-selection and confirm the opening step no longer names the 6.2 candidate
Confirm the next paragraph's version-independent always-bump-minor guidance is unchanged
Confirm migration-6.2.md remains linked as history

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/3151 **Author:** [@L00PLeGeNd](https://github.com/L00PLeGeNd) **Created:** 10/14/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `docs/releasing-compatibility-review-version-agnostic` --- ### 📝 Commits (1) - [`db34619`](https://github.com/morluto/rea/commit/db3461936baace184a5a30fb864d7c15108dccdf) docs(releasing): make compatibility review version-agnostic ### 📊 Changes **1 file changed** (+5 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `docs/releasing.md` (+5 -2) </details> ### 📄 Description ## Summary - Rewrite the compatibility-review step in `docs/releasing.md` so it applies to the release under preparation, not a past 6.2 candidate. - Keep the 6.1→6.2 migration guide linked as historical reference for that earlier release pair. - No product behavior changes. Fixes #3058 ## Test plan - [x] Read `docs/releasing.md#compatibility-and-version-selection` and confirm the opening step no longer names the 6.2 candidate - [x] Confirm the next paragraph's version-independent `always-bump-minor` guidance is unchanged - [x] Confirm `migration-6.2.md` remains linked as history --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-31 01:08:13 +00:00