Skip to content

Add the missing Harper Pro 5.4 release-note fragments, and correct 5.4 docs that contradict 5.4.0 - #1365

Merged
kriszyp merged 3 commits into
mainfrom
docs/release-notes-5.4-gaps
Nov 13, 2026
Merged

kriszyp merged 3 commits into
mainfrom
docs/release-notes-5.4-gaps

Conversation

@kriszyp

@kriszyp kriszyp commented Nov 13, 2026

Copy link
Copy Markdown
Member

⊙ Problem

Harper Pro 5.4.0 shipped, but docs/release-notes/v5-lincoln/5.4/ had no fragment for several user-facing changes since v5.3.1, among them private-network replication, Node 26 images and opt-in cluster record locks. Two 5.4 docs also contradicted the release: they said replication.threads defaults to 0 (5.4.0 defaults it to half of threads.count), and they labeled private network addresses as v5.5.0.

💡 Solution

  • Ten new fragments, one per change or group of related changes, with a Known Issues entry for remove_node of a live node can discard writes no peer has received yet #1348 (removing a node can lose writes it never delivered).
  • Corrected the dedicated replication threads fragment and reference to the shipped default, including its two fallbacks to 0: no dedicated port, or a deprecated residency hook registered at startup.
  • Changed the four v5.5.0 labels for private network addresses to v5.4.0.
Fragments added
File Section PRs
private-network-addresses.md Replication #1294
cluster-record-locks-stay-opt-in.md Replication #1316, #1350
record-locks-across-node-restarts.md Replication #1059, #1193, #1196, #1205, #1065, #1305
table-expiration-reaches-joining-nodes.md Replication #1233
cloned-applications-and-clone-safeguards.md Replication #1050, #1250
remove-node-by-the-address-it-was-added-with.md Replication #986
known-issue-remove-node-of-a-live-node.md Known Issues #1348
harper-pro-images-run-node-26.md Container Images #1119
npm-package-ships-a-locked-dependency-bundle.md Container Images #981
harper-pro-workers-start-with-a-smaller-heap.md Memory #992, #995

Already covered by an existing fragment: sharded owners idle past retention and the 503 for writes no owner receives (#1322, base-copies-that-could-not-finish.md), cloning from a sharded leader (#1290), update_node and membership (#1329), the profiler (#1012), hot-lock handover (#4065). Left to core's fragments: re-delivered writes (harper#4199, via #1312) and graceful shutdown (harper#3943, via #1282). #1264 changes nothing a user sees.

✅ Verification

  • Every claim checked against its PR and the code at the v5.4.0 tag (server/threads/workerPools.ts replicationThreadCount, replication/privatePaths.ts).
  • Every /reference/v5/... link and heading anchor resolves in this repo's docs/reference or core's at v5.4.0. The in-page links resolve to core fragment headings at v5.4.0.
  • prettier --check docs passes.

Docs: this is the docs change. PR QA: not substantive (docs only).

— Claude Opus 5.5

🤖 Generated with Claude Code

https://claude.ai/code/session_01F7groWG2PoCFsmKT2Wejui

Release target: v5.4 — documents what shipped in v5.4.0
Related PRs: #1301 overlaps, #1353 independent

Deferred findings

  • c4b0c2dd5383f234 nit documentation — docs/release-notes/v5-lincoln/5.4/cluster-record-locks-stay-opt-in.md — Links to #conditional-writes-without-cluster-record-locks and #smaller-per-thread-baseline have no Pro heading — NOT FILED

Review-Coverage: authored=claude; ran=gemini,cursor-composer,codex; adjudicated=domain; declined=cursor-grok,muse; urgency=fast; rounds=3; full=1 @ 983e38f

Review-Attention: skim ~2m (decisions: known-issue-in-release-notes) @ 983e38f

kriszyp and others added 3 commits November 12, 2026 17:29
…4 docs that contradict 5.4.0

New fragments for private-network replication, Node 26 images, opt-in
cluster record locks, record locks across restarts and stopped nodes, a
table's expiration on joining nodes, clone fixes, remove_node by address,
the smaller Pro worker heap, the npm dependency bundle, and a known issue
for removing a live node (#1348).

The dedicated replication threads fragment and reference said
replication.threads defaults to 0; 5.4.0 defaults it to half of
threads.count. Private network addresses shipped in 5.4.0, not 5.5.0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01F7groWG2PoCFsmKT2Wejui
Dispatch-Task: release-cut-main-5.4.0
…pe and replication-thread port wording

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01F7groWG2PoCFsmKT2Wejui
Dispatch-Task: release-cut-main-5.4.0
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01F7groWG2PoCFsmKT2Wejui
Dispatch-Task: release-cut-main-5.4.0
@kriszyp kriszyp added this to the v5.4 milestone Nov 13, 2026
@kriszyp
kriszyp marked this pull request as ready for review November 13, 2026 01:08
@kriszyp
kriszyp merged commit f42fd1c into main Nov 13, 2026
40 of 42 checks passed
@kriszyp
kriszyp deleted the docs/release-notes-5.4-gaps branch November 13, 2026 01:08
kriszyp added a commit that referenced this pull request Nov 13, 2026
Dispatch-Task: hp-1301-grid-rework-r2
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant