[PR #7355] docs(release): correct 6.1.0 change provenance #7829

Open
opened 2026-11-05 01:47:58 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/7355
Author: @TheAlgo7
Created: 10/27/2026
Status: 🔄 Open

Base: main ← Head: docs/correct-6-1-release-notes


📝 Commits (1)

  • babff19 docs(release): correct 6.1.0 change provenance

📊 Changes

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

View changed files

📝 CHANGELOG.md (+2 -3)

📄 Description

Summary

Correct three release-note entries still present after #1106: link both Hopper breaking-change bullets to their originating commits and remove the acceptance-harness entry reverted before 6.1.0.

Problem and expected behavior

The 6.1.0 notes advertise 5ac3dc9, although 283c82f removed all five files it introduced. The two breaking-change bullets also lack direct source references. Release notes should describe shipped changes with traceable provenance.

Change and scope

Only CHANGELOG.md changes. This addresses the three unresolved review findings on #1106. The current release checker also accepts matching BREAKING CHANGE text, so this does not claim to fix a current release-validation failure.

Contract and boundary impact

The authored changelog owns these claims. Runtime, CLI/MCP, providers, target interaction, generated catalogs, installation, and package contents are unchanged. Maintainer scope decision: not applicable to this documentation correction.

  • Documentation or usability only; no target interaction.

Evidence and regression coverage

GitHub commit inspection confirmed that f201b04 and 2f71375 contain the exact breaking notes and that 283c82f deletes all five files added by 5ac3dc9.

Validation performed

  • git diff --check — passed.
  • Executed Node assertions against HEAD and the edited file — both breaking sections now link to their commits, the reverted claim is removed, and every other release section is unchanged.
  • No runtime tests or full docs gate run; this is a three-entry historical changelog correction. Real-provider coverage is not applicable.

Compatibility, safety, and release

Documentation only; existing breaking-change migration guidance is preserved. Published release assets are unchanged.

Author readiness

Human owner: @TheAlgo7

  • I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
  • I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
  • I declare this PR ready for initial maintainer review.

🔄 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/7355 **Author:** [@TheAlgo7](https://github.com/TheAlgo7) **Created:** 10/27/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `docs/correct-6-1-release-notes` --- ### 📝 Commits (1) - [`babff19`](https://github.com/morluto/rea/commit/babff195a6e00e79e9158203870b4727a6a58ac9) docs(release): correct 6.1.0 change provenance ### 📊 Changes **1 file changed** (+2 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `CHANGELOG.md` (+2 -3) </details> ### 📄 Description ## Summary Correct three release-note entries still present after #1106: link both Hopper breaking-change bullets to their originating commits and remove the acceptance-harness entry reverted before 6.1.0. ## Problem and expected behavior The 6.1.0 notes advertise `5ac3dc9`, although `283c82f` removed all five files it introduced. The two breaking-change bullets also lack direct source references. Release notes should describe shipped changes with traceable provenance. ## Change and scope Only CHANGELOG.md changes. This addresses the three unresolved review findings on #1106. The current release checker also accepts matching BREAKING CHANGE text, so this does not claim to fix a current release-validation failure. ## Contract and boundary impact The authored changelog owns these claims. Runtime, CLI/MCP, providers, target interaction, generated catalogs, installation, and package contents are unchanged. Maintainer scope decision: not applicable to this documentation correction. - [x] Documentation or usability only; no target interaction. ## Evidence and regression coverage GitHub commit inspection confirmed that `f201b04` and `2f71375` contain the exact breaking notes and that `283c82f` deletes all five files added by `5ac3dc9`. ## Validation performed - `git diff --check` — passed. - Executed Node assertions against HEAD and the edited file — both breaking sections now link to their commits, the reverted claim is removed, and every other release section is unchanged. - No runtime tests or full docs gate run; this is a three-entry historical changelog correction. Real-provider coverage is not applicable. ## Compatibility, safety, and release Documentation only; existing breaking-change migration guidance is preserved. Published release assets are unchanged. ## Author readiness Human owner: @TheAlgo7 - [ ] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [ ] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [ ] I declare this PR ready for initial maintainer review. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#7829
No description provided.