Release automation · 2026 · Solo — trend research, GitHub transaction design, test-first implementation, security boundary, verification
Release Pagekeeper
A narrowly authorized release-documentation operator that opens evidence-rich pull requests without merge authority.
The problem
Release notes and a marked project-page block can drift apart. Release Pagekeeper reads one current GitHub release and one exact Markdown marker pair, plans the replacement, creates or reuses a deterministic branch, writes one exact-SHA commit, and opens a pull request. It never merges, deletes branches, writes the default branch, or stores the supplied credential.
Architecture
Key decisions
Keep authority narrower than the outcome
The browser can prepare a branch and pull request but cannot merge, delete, or write the default branch. The token is cleared after the transaction.
Make retries deterministic
Managed tag metadata, exact-SHA writes, deterministic branch naming, and open-PR reuse make interrupted transactions inspectable and repeatable.
Prove the external write once
The verified production run created open sandbox pull request #1 on branch release-pagekeeper/v0.0.13. The release evidence records 25 unit tests, four authenticated production-browser scenarios, zero dependency vulnerabilities, and code SHA 1463f09867cd4990ff9a58d21e206552f6f7b6b6.