docs: roll over per-crate changelogs for 1.0.0-rc.3 - #307
Merged
StefanSteiner merged 1 commit intoSep 7, 2026
Conversation
Post-tag bookkeeping per docs/GITHUB_OPERATIONS.md ('Rolling over the
per-crate changelogs'). For each of the nine hand-maintained per-crate
changelogs, rename '## [Unreleased]' to '## [1.0.0-rc.3] - 2026-09-07'
(matching the root changelog's rc.3 date) and insert a fresh empty
'## [Unreleased]' above it.
Pure heading rollover: +2/-0 on every file, no bullet reordered or
reworded. All nine sections were non-empty. markdownlint-cli2 clean
(0 issues in 68 files). Root CHANGELOG.md, npm sub-package changelogs,
versions, and the tag are untouched.
This was referenced Sep 7, 2026
StefanSteiner
added a commit
that referenced
this pull request
Sep 7, 2026
… budget (#309) * test: make changelog contract robust to rollover; bump restart budget Fix A: smoke_demo_and_changelog_contract asserted KV/export/routing claims only against the `## [Unreleased]` slice of the embedded mcp CHANGELOG. PR #307 (the rc.3 changelog rollover) moved every bullet into `## [1.0.0-rc.3]`, emptying Unreleased and failing the test. Because #307 was docs-only, CI's `paths-ignore: **/*.md` skipped the Rust suite, so the break surfaced only on a later code PR. Assert instead against the current release window (`## [Unreleased]` + the most-recent dated section) via a new `current_release_window` helper, so a future rollover can't silently rebreak it. The window is bounded to the newest dated section so a stale token in an ancient entry can't satisfy a deleted-claim check. Fix B: engine_recovers_after_hyperd_killed and hyperd_monitor_detects_killed_hyperd_and_restarts time out on ubuntu-latest under CI load — a 5s monitor tick plus cold hyperd spawn against a 12s readiness budget. Replace the three magic `12`s with a named RESTART_READINESS_BUDGET_SECS = 45 and document the derivation. Budget bump only; the macOS-only ignore is unchanged, so Linux/Windows crash-recovery coverage from #279/#286 stays. See #305. * test: gate RESTART_READINESS_BUDGET_SECS to cfg(unix) The constant's only use sites are the three `#[cfg(unix)]` restart tests and their Unix-only helpers, so on Windows it compiled but was never referenced and `clippy -D warnings` (windows-latest) rejected it as dead code. Gate the definition with `#[cfg(unix)]` so it exists exactly where it's used — the honest fix, not `#[allow(dead_code)]`.
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
1 participant
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.
What
Post-tag bookkeeping for the
v1.0.0-rc.3release (main tip82b45cb, thechore: release main (#282)merge). This is the documented follow-up indocs/GITHUB_OPERATIONS.md→ "Rolling over the per-cratechangelogs":
nothing automates it, so entries for shipped work keep piling up under
## [Unreleased]until someone rolls them over by hand.For each of the nine hand-maintained per-crate changelogs,
## [Unreleased]was renamed to
## [1.0.0-rc.3] - 2026-09-07and a fresh, empty## [Unreleased]inserted above it. Pure heading rollover — no bullet wasreordered, reworded, or moved (
git diffis+2 / -0on every file: the datedheading plus one blank line).
The date
2026-09-07matches the rootCHANGELOG.md's## [1.0.0-rc.3]heading (release-please, UTC).Crates rolled over (all nine were non-empty)
hyperdb-mcphyperdb-apihyperdb-bootstraphyperdb-api-corehyperdb-api-nodehyperdb-compile-checkhyperdb-api-derivehyperdb-api-salesforcesea-query-hyperdbNone were left empty. In particular
hyperdb-api-node(4 bullets) wasrolled over.
Not touched
CHANGELOG.md— release-please-owned.hyperdb-api-node/npm/*andhyperdb-mcp/npm/*— no## [Unreleased]section.Cargo.toml,version.txt, workflows, release-pleaseconfig, or the
v1.0.0-rc.3tag/Release.Verification
npx markdownlint-cli2(no args): 0 issues in 68 files — identical to theupstream/mainbaseline. MD024 issiblings_only: true, so the new datedsection's
### Fixed/### Addeddo not collide with the adjacent olderdated section (different
##parents).git diff --numstat:2 0on all nine files — pure heading insertion.Notes for the reviewer
Changelog order —
hyperdb-api(Removed, Fixed, Changed, Added) andhyperdb-compile-check(Fixed, Changed). They were left exactly as they satunder
## [Unreleased], per the "pure rollover, do not reorder" rule; happyto sort them into KaC order if preferred.
hyperdb-api-nodehas a pre-existing layout quirk: a release-please-style## [0.1.3] … (2026-05-18)heading sits above## [Unreleased], so thefresh
## [Unreleased]and the new## [1.0.0-rc.3]now sit below it. Leftas-is (out of scope for a pure rollover), but flagging it.
had not been rolled over in a long time (
hyperdb-apisince0.1.1,hyperdb-mcpsince0.5.0), so the accumulated## [Unreleased]bulletsdescribe work shipped across the whole
0.x→rcrange, now all stamped1.0.0-rc.3as the procedure directs.hyperdb-mcpcarries an explicitin-file HTML comment about two entries that landed retroactively in
0.7.3.Nothing here describes unshipped/future work.
Its own PR, not bundled with feature work.