Repository navigation
Add the missing Harper Pro 5.4 release-note fragments, and correct 5.4 docs that contradict 5.4.0 - #1365
Merged
Conversation
…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
marked this pull request as ready for review
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>
This was referenced Nov 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
⊙ 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 saidreplication.threadsdefaults to0(5.4.0 defaults it to half ofthreads.count), and they labeled private network addresses as v5.5.0.💡 Solution
0: no dedicated port, or a deprecated residency hook registered at startup.v5.5.0labels for private network addresses tov5.4.0.Fragments added
private-network-addresses.mdcluster-record-locks-stay-opt-in.mdrecord-locks-across-node-restarts.mdtable-expiration-reaches-joining-nodes.mdcloned-applications-and-clone-safeguards.mdremove-node-by-the-address-it-was-added-with.mdknown-issue-remove-node-of-a-live-node.mdharper-pro-images-run-node-26.mdnpm-package-ships-a-locked-dependency-bundle.mdharper-pro-workers-start-with-a-smaller-heap.mdAlready 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_nodeand 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
v5.4.0tag (server/threads/workerPools.tsreplicationThreadCount,replication/privatePaths.ts)./reference/v5/...link and heading anchor resolves in this repo'sdocs/referenceor core's at v5.4.0. The in-page links resolve to core fragment headings at v5.4.0.prettier --check docspasses.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
c4b0c2dd5383f234nit 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 FILEDReview-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