[GH-ISSUE #7617] [Bug] SQLite guide describes a Node 24.15.0 CI lane absent from the workflow #4546

Open
opened 2026-10-31 00:50:40 +00:00 by bsakaguchi · 0 comments
Owner

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

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

A contributor reading the SQLite guide's Compatibility verification section is told that the reusable CI workflow tests Node 24.15.0. Static comparison with the workflow shows that its exact Node 24 pin is 24.22.1 and its rolling Node 24 selection starts at 24.22.1. Neither selection can run 24.15.0.

I checked this with the source-printing commands below on the stated baseline. This is a source-only documentation finding; I did not execute GitHub Actions or run SQLite inspection under an older Node release.

Reproduction

From the repository root at the baseline below:

  1. Run sed -n '205,210p' docs/sqlite-databases.md. The compatibility paragraph says the workflow tests the minimum supported 24.15.0 release.
  2. Run sed -n '18,29p' .github/workflows/sqlite-runtime.yml. The four selections are Node 22 starting at 22.23.4, exact 24.22.1, Node 24 starting at 24.22.1, and Node 26 starting at 26.12.1. The selected value is passed directly to setup-node.
  3. Run rg -n '24\.15|24\.21|node-version|sqlite-runtime' .github/workflows and cat .nvmrc. The workflow caller adds no older Node override; other version-file selections use the 24.22.1 pin. There is no alternate 24.15-24.21 workflow lane.

These commands were executed once during verification. The contradiction is deterministic for this source revision and requires no fixture or provider installation.

Expected behavior

The guide's compatibility-verification paragraph should describe the runtimes selected by the workflow it names. It should identify the tested Node 24 baseline as 24.22.1 and distinguish that from the earlier native SQLite API minimum.

Impact and scope

P3 documentation wording defect: contributors receive an incorrect account of current CI coverage. No runtime failure or consequential behavior change was established.

Node 24.15-24.21 is below REA's current package-wide supported Node 24 floor. The SQLite capability helper's earlier API minimum does not establish support for those versions, and this report does not request restoring an unsupported CI lane. The workflow itself provides an available way to check the actual runtime selections.

REA version

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

6.8.0

Source baseline: 65f1c447344a423fa2785847dbcea1e9a9e2454a.

Runtime and platform

Node v24.22.1; macOS, arm64. The finding concerns static documentation and workflow configuration.

Interface

Other

Earliest failure stage

Unknown

Relevant output or evidence

At the source baseline:

  • docs/sqlite-databases.md:207-210 explicitly says the reusable workflow tests a list that includes 24.15.0; the version is part of the testing claim, rather than only an API requirement.
  • .github/workflows/sqlite-runtime.yml:19-29 selects ^22.23.4, 24.22.1, ^24.22.1 and ^26.12.1, then supplies the selected entry to setup-node. Lines 33-39 install dependencies and run the SQLite suite.
  • .github/workflows/ci.yml:465-471 invokes that reusable workflow without a runtime override; .nvmrc:1 contains 24.22.1.
  • src/application/sqlite/SqliteDatabaseCapability.ts:25 recognizes the separate native API range starting at 24.15.0. src/domain/runtimeVersion.ts:4 and package.json:46 put REA's Node 24 support floor at 24.22.1. .npmrc:1 enables strict engine checks.

A read-only selector probe using the checkout's semver dependency confirmed that 24.15.0 through the sampled 24.21.99 input match none of the four matrix selectors; 24.22.1 matches the exact and rolling Node 24 selectors. This evaluates version strings on Node 24.22.1 and does not establish execution on those older versions.

Analysis or suspected cause

The related merged runtime-floor change, PR #6315, includes a review comment about the old CI pin failing installation. The current matrix contains the requested newer pin, while the guide still describes the earlier lane. That supports documentation drift as the explanation; it does not establish a new CI installation failure.

Originally created by @coygeek on GitHub (Oct 27, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/7617 ### 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 A contributor reading the SQLite guide's Compatibility verification section is told that the reusable CI workflow tests Node 24.15.0. Static comparison with the workflow shows that its exact Node 24 pin is 24.22.1 and its rolling Node 24 selection starts at 24.22.1. Neither selection can run 24.15.0. I checked this with the source-printing commands below on the stated baseline. This is a source-only documentation finding; I did not execute GitHub Actions or run SQLite inspection under an older Node release. ### Reproduction From the repository root at the baseline below: 1. Run `sed -n '205,210p' docs/sqlite-databases.md`. The compatibility paragraph says the workflow tests the minimum supported 24.15.0 release. 2. Run `sed -n '18,29p' .github/workflows/sqlite-runtime.yml`. The four selections are Node 22 starting at 22.23.4, exact 24.22.1, Node 24 starting at 24.22.1, and Node 26 starting at 26.12.1. The selected value is passed directly to setup-node. 3. Run `rg -n '24\.15|24\.21|node-version|sqlite-runtime' .github/workflows` and `cat .nvmrc`. The workflow caller adds no older Node override; other version-file selections use the 24.22.1 pin. There is no alternate 24.15-24.21 workflow lane. These commands were executed once during verification. The contradiction is deterministic for this source revision and requires no fixture or provider installation. ### Expected behavior The guide's compatibility-verification paragraph should describe the runtimes selected by the workflow it names. It should identify the tested Node 24 baseline as 24.22.1 and distinguish that from the earlier native SQLite API minimum. ### Impact and scope P3 documentation wording defect: contributors receive an incorrect account of current CI coverage. No runtime failure or consequential behavior change was established. Node 24.15-24.21 is below REA's current package-wide supported Node 24 floor. The SQLite capability helper's earlier API minimum does not establish support for those versions, and this report does not request restoring an unsupported CI lane. The workflow itself provides an available way to check the actual runtime selections. ### REA version Exact output of `node scripts/rea.mjs --version`: ```text 6.8.0 ``` Source baseline: `65f1c447344a423fa2785847dbcea1e9a9e2454a`. ### Runtime and platform Node v24.22.1; macOS, arm64. The finding concerns static documentation and workflow configuration. ### Interface Other ### Earliest failure stage Unknown ### Relevant output or evidence At the source baseline: - `docs/sqlite-databases.md:207-210` explicitly says the reusable workflow tests a list that includes 24.15.0; the version is part of the testing claim, rather than only an API requirement. - `.github/workflows/sqlite-runtime.yml:19-29` selects `^22.23.4`, `24.22.1`, `^24.22.1` and `^26.12.1`, then supplies the selected entry to setup-node. Lines 33-39 install dependencies and run the SQLite suite. - `.github/workflows/ci.yml:465-471` invokes that reusable workflow without a runtime override; `.nvmrc:1` contains 24.22.1. - `src/application/sqlite/SqliteDatabaseCapability.ts:25` recognizes the separate native API range starting at 24.15.0. `src/domain/runtimeVersion.ts:4` and `package.json:46` put REA's Node 24 support floor at 24.22.1. `.npmrc:1` enables strict engine checks. A read-only selector probe using the checkout's semver dependency confirmed that 24.15.0 through the sampled 24.21.99 input match none of the four matrix selectors; 24.22.1 matches the exact and rolling Node 24 selectors. This evaluates version strings on Node 24.22.1 and does not establish execution on those older versions. ### Analysis or suspected cause The related merged runtime-floor change, [PR #6315](https://github.com/morluto/rea/pull/6315), includes a [review comment about the old CI pin failing installation](https://github.com/morluto/rea/pull/6315#discussion_r4347273779). The current matrix contains the requested newer pin, while the guide still describes the earlier lane. That supports documentation drift as the explanation; it does not establish a new CI installation failure.
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#4546
No description provided.