morluto/rea

Fork 0

mirror of https://github.com/morluto/rea.git synced 2026-11-05 06:45:22 +00:00

[GH-ISSUE #7686] [Bug] Two historical changelog version links return GitHub 404 #4607

New issue

Closed

opened 2026-10-31 00:51:15 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-31 00:51:15 +00:00

Owner

Originally created by @coygeek on GitHub (Oct 28, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/7686

Before submitting

I searched the open and closed issues for a related report.
I removed credentials, tokens, private paths, and sensitive target data.

Area

Documentation

Observed behavior

Following the changelog version links for 0.3.0 and 0.2.0 opens a GitHub 404 instead of a release comparison. Direct HTTP GETs and the GitHub compare API both returned 404 for the exact linked ranges. The links name currently absent base tags, although the destination release tags exist.

For 0.3.0, changing the base from rea-agents-0.2.1 to the existing rea-0.2.1 produces HTTP 200 and a comparison containing 15 commits.

Reproduction

From the source baseline below, inspect the 0.3.0 and 0.2.0 version hyperlinks in the changelog, then run:

curl -L -sS --max-time 30 -o /dev/null -w '%{http_code}\n' https://github.com/morluto/rea/compare/rea-agents-0.2.1...rea-agents-0.3.0 — prints 404.
curl -L -sS --max-time 30 -o /dev/null -w '%{http_code}\n' https://github.com/morluto/rea/compare/rea-0.1.0...rea-0.2.0 — prints 404.
Control: curl -L -sS --max-time 30 -o /dev/null -w '%{http_code}\n' https://github.com/morluto/rea/compare/rea-0.2.1...rea-agents-0.3.0 — prints 200.

Each original URL returned 404 in two of two GETs. No fixture, target binary, or provider is required.

Expected behavior

Selecting a version hyperlink should open that release's comparison or another valid release destination. This expectation follows from the link's navigation purpose. The neighboring 0.2.1 version link successfully opens its comparison. Historical releases should use their actual tag spelling; a version without a corresponding tag should not serve as a compare endpoint.

Impact and scope

Readers cannot use these two version headings to inspect their release diffs. The release text and individual commit links remain available. The corrected 0.3.0 comparison is a verified workaround. No CLI/MCP, analysis, installation, or publication failure was observed.

All 39 changelog heading compare ranges were checked against local Git refs. Only these two bases failed; the other 37 headings were not individually fetched over HTTP. Current upstream tag and release listings also lack these two bases. These observations do not prove that the refs never existed or that version 0.1.0 was never published elsewhere.

REA version

Exact output from node scripts/rea.mjs --version:

6.8.0

Source baseline: 65f1c447344a423fa2785847dbcea1e9a9e2454a.

Runtime and platform

Node v24.22.1; macOS 27.0.1; arm64. HTTP checks used curl and read-only GitHub CLI requests. No reverse-engineering provider was involved.

Target and artifact context

The repository changelog and its public GitHub comparison URLs.

Interface

Other

Earliest failure stage

Unknown

Relevant output or evidence

CHANGELOG.md:2686: the 0.3.0 heading links rea-agents-0.2.1...rea-agents-0.3.0.
CHANGELOG.md:2739: the 0.2.0 heading links rea-0.1.0...rea-0.2.0.
CHANGELOG.md:2731: the adjacent 0.2.1 heading links rea-0.2.0...rea-0.2.1; its GET returned 200.
git tag -l '*0.2*' returned rea-0.2.0 and rea-0.2.1; git tag -l '*0.1.0*' returned nothing. Both git rev-parse --verify 'rea-agents-0.2.1^{commit}' and git rev-parse --verify 'rea-0.1.0^{commit}' exited 128 with fatal: Needed a single revision.
gh api repos/morluto/rea/git/matching-refs/tags confirmed the current upstream tag spellings; gh release list -R morluto/rea --limit 100 listed no 0.1.0 GitHub release.
gh api repos/morluto/rea/compare/rea-agents-0.2.1...rea-agents-0.3.0 and the analogous rea-0.1.0...rea-0.2.0 request each returned Not Found (HTTP 404).
gh api repos/morluto/rea/compare/rea-0.2.1...rea-agents-0.3.0 --jq '{status,total_commits,html_url}' returned status: ahead, total_commits: 15, and the corrected comparison URL.

Analysis or suspected cause

Historical Release Please bot commits 365bd6ca2fe950ce8de9ad5de9906f7df309ba84 and b6a817750b596046077350ff4c54c16a4e2543ba introduced the respective headings. Their release workflow used Release Please. Before 0.3.0, the package-name configuration changed to rea-agents; before 0.2.0, the release manifest already recorded 0.1.0.

These facts support a generated-link origin. Applying the new package prefix to the prior manifest version is a plausible mechanism for 0.3.0. The historical generator was not rerun, so this report establishes broken stored documentation rather than a regression in today's generator. Correcting the historical destinations is sufficient for this reported behavior; creating missing tags would require separate evidence for their intended commits.

Additional context

The duplicate search covered open and closed issues, all-state and merged PRs, and comments. Related documentation/release work in issues #2156, #7517 and #1063 and PRs #7355, #7519 and #1064 concerns different defects. PR #75 reports an npm rea-agents@0.2.1 publication and PR #4 an npm @morluto/rea@0.1.0 publication; neither establishes the missing Git tags.

Triage assessment

Impact level: P3
Assessment status: supported
Impact basis: Two historical documentation hyperlinks fail; the release content remains readable, and no application behavior is affected by this report.
Workaround status: available
Workaround basis: The corrected 0.3.0 compare URL returned HTTP 200 and 15 commits; existing release text and per-commit links remain available for inspection.

Originally created by @coygeek on GitHub (Oct 28, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/7686 ### Before submitting - [x] I searched the open and closed issues for a related report. - [x] I removed credentials, tokens, private paths, and sensitive target data. ### Area Documentation ### Observed behavior Following the changelog version links for 0.3.0 and 0.2.0 opens a GitHub 404 instead of a release comparison. Direct HTTP GETs and the GitHub compare API both returned 404 for the exact linked ranges. The links name currently absent base tags, although the destination release tags exist. For 0.3.0, changing the base from `rea-agents-0.2.1` to the existing `rea-0.2.1` produces HTTP 200 and a comparison containing 15 commits. ### Reproduction From the source baseline below, inspect the 0.3.0 and 0.2.0 version hyperlinks in the changelog, then run: 1. `curl -L -sS --max-time 30 -o /dev/null -w '%{http_code}\n' https://github.com/morluto/rea/compare/rea-agents-0.2.1...rea-agents-0.3.0` — prints `404`. 2. `curl -L -sS --max-time 30 -o /dev/null -w '%{http_code}\n' https://github.com/morluto/rea/compare/rea-0.1.0...rea-0.2.0` — prints `404`. 3. Control: `curl -L -sS --max-time 30 -o /dev/null -w '%{http_code}\n' https://github.com/morluto/rea/compare/rea-0.2.1...rea-agents-0.3.0` — prints `200`. Each original URL returned 404 in two of two GETs. No fixture, target binary, or provider is required. ### Expected behavior Selecting a version hyperlink should open that release's comparison or another valid release destination. This expectation follows from the link's navigation purpose. The neighboring 0.2.1 version link successfully opens its comparison. Historical releases should use their actual tag spelling; a version without a corresponding tag should not serve as a compare endpoint. ### Impact and scope Readers cannot use these two version headings to inspect their release diffs. The release text and individual commit links remain available. The corrected 0.3.0 comparison is a verified workaround. No CLI/MCP, analysis, installation, or publication failure was observed. All 39 changelog heading compare ranges were checked against local Git refs. Only these two bases failed; the other 37 headings were not individually fetched over HTTP. Current upstream tag and release listings also lack these two bases. These observations do not prove that the refs never existed or that version 0.1.0 was never published elsewhere. ### REA version Exact output from `node scripts/rea.mjs --version`: ```text 6.8.0 ``` Source baseline: `65f1c447344a423fa2785847dbcea1e9a9e2454a`. ### Runtime and platform Node `v24.22.1`; macOS `27.0.1`; `arm64`. HTTP checks used curl and read-only GitHub CLI requests. No reverse-engineering provider was involved. ### Target and artifact context The repository changelog and its public GitHub comparison URLs. ### Interface Other ### Earliest failure stage Unknown ### Relevant output or evidence - `CHANGELOG.md:2686`: the 0.3.0 heading links `rea-agents-0.2.1...rea-agents-0.3.0`. - `CHANGELOG.md:2739`: the 0.2.0 heading links `rea-0.1.0...rea-0.2.0`. - `CHANGELOG.md:2731`: the adjacent 0.2.1 heading links `rea-0.2.0...rea-0.2.1`; its GET returned 200. - `git tag -l '*0.2*'` returned `rea-0.2.0` and `rea-0.2.1`; `git tag -l '*0.1.0*'` returned nothing. Both `git rev-parse --verify 'rea-agents-0.2.1^{commit}'` and `git rev-parse --verify 'rea-0.1.0^{commit}'` exited 128 with `fatal: Needed a single revision`. - `gh api repos/morluto/rea/git/matching-refs/tags` confirmed the current upstream tag spellings; `gh release list -R morluto/rea --limit 100` listed no 0.1.0 GitHub release. - `gh api repos/morluto/rea/compare/rea-agents-0.2.1...rea-agents-0.3.0` and the analogous `rea-0.1.0...rea-0.2.0` request each returned `Not Found (HTTP 404)`. - `gh api repos/morluto/rea/compare/rea-0.2.1...rea-agents-0.3.0 --jq '{status,total_commits,html_url}'` returned `status: ahead`, `total_commits: 15`, and the corrected comparison URL. ### Analysis or suspected cause Historical Release Please bot commits `365bd6ca2fe950ce8de9ad5de9906f7df309ba84` and `b6a817750b596046077350ff4c54c16a4e2543ba` introduced the respective headings. Their release workflow used Release Please. Before 0.3.0, the package-name configuration changed to `rea-agents`; before 0.2.0, the release manifest already recorded `0.1.0`. These facts support a generated-link origin. Applying the new package prefix to the prior manifest version is a plausible mechanism for 0.3.0. The historical generator was not rerun, so this report establishes broken stored documentation rather than a regression in today's generator. Correcting the historical destinations is sufficient for this reported behavior; creating missing tags would require separate evidence for their intended commits. ### Additional context The duplicate search covered open and closed issues, all-state and merged PRs, and comments. Related documentation/release work in issues #2156, #7517 and #1063 and PRs #7355, #7519 and #1064 concerns different defects. PR #75 reports an npm `rea-agents@0.2.1` publication and PR #4 an npm `@morluto/rea@0.1.0` publication; neither establishes the missing Git tags. ## Triage assessment - Impact level: P3 - Assessment status: supported - Impact basis: Two historical documentation hyperlinks fail; the release content remains readable, and no application behavior is affected by this report. - Workaround status: available - Workaround basis: The corrected 0.3.0 compare URL returned HTTP 200 and 15 commits; existing release text and per-commit links remain available for inspection.

bsakaguchi closed this issue

2026-10-31 00:51:16 +00:00

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#4607

No description provided.

Rows
Columns