Design: only-changed releases (#5) — SPEC section, doc only #10

Closed
rhelwig wants to merge 0 commits from feat/only-changed-versioning-design into main
Owner

Doc-only design for #5 (only-changed releases). Adds docs/SPECS.md § Only-changed releases (planned, issue #5; not implemented) and an IMPLEMENTATION-PLAN entry.

  • Reuse unchanged version records from the parent release verbatim, keeping their original publishBatchId, sequence and previousVersionId. Only changed or new records get new versions. release and site are always new.
  • Offline validateReleaseRequest accepts other-batch versions only as reused candidates. inspectReleaseRequest requires each one to be in the parent manifest and to already exist on Platform, canonically equal.
  • Release-request version: 2, so older Auth builds fail closed with an "update Auth" message.
  • No contract or schema change, and no rewrite of Platform data. The Stub already resolves by version ID.
  • Expected for ronhelwig.com release 2: about 20 writes down to about 7. #6 timing logs will measure it.

No code changes. validateReleaseRequest behavior is unchanged. Based on main @ d379421.

Doc-only design for #5 (only-changed releases). Adds `docs/SPECS.md` § *Only-changed releases (planned, issue #5; not implemented)* and an IMPLEMENTATION-PLAN entry. - Reuse unchanged version records from the parent release verbatim, keeping their original `publishBatchId`, `sequence` and `previousVersionId`. Only changed or new records get new versions. `release` and `site` are always new. - Offline `validateReleaseRequest` accepts other-batch versions only as reused candidates. `inspectReleaseRequest` requires each one to be in the parent manifest and to already exist on Platform, canonically equal. - Release-request `version: 2`, so older Auth builds fail closed with an "update Auth" message. - No contract or schema change, and no rewrite of Platform data. The Stub already resolves by version ID. - Expected for ronhelwig.com release 2: about 20 writes down to about 7. #6 timing logs will measure it. **No code changes. `validateReleaseRequest` behavior is unchanged.** Based on `main` @ d379421.
Reuse unchanged version records from the parent release (verbatim, original
publishBatchId), new versions only for changed records, release-request
version 2, validate/inspect rules for reused candidates, Auth labelling,
no schema change. validateReleaseRequest behavior unchanged.
Author
Owner

Merged into main locally and pushed: merge commit 5f3298b. Resolved a docs/IMPLEMENTATION-PLAN.md conflict with #9 by keeping the timing entries and this PR's #5 status bullet. Closing (Forgejo did not auto-detect the merge).

Merged into main locally and pushed: merge commit 5f3298b. Resolved a docs/IMPLEMENTATION-PLAN.md conflict with #9 by keeping the timing entries and this PR's #5 status bullet. Closing (Forgejo did not auto-detect the merge).
rhelwig closed this pull request 2026-10-10 18:51:56 +00:00

Pull request closed

Sign in to join this conversation.
No reviewers
No labels
feature request
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
rhelwig/DecentSite!10
No description provided.