Skip to content

docs: after publishing 1.1.1 (RELEASING.md E1–E4) - #18

Merged
tedsluis merged 1 commit into
mainfrom
docs/1.1.1-after-publish
Oct 8, 2026
Merged

tedsluis merged 1 commit into
mainfrom
docs/1.1.1-after-publish

Conversation

@tedsluis

@tedsluis tedsluis commented Oct 8, 2026

Copy link
Copy Markdown
Owner

After-publish documentation for 1.1.1 (RELEASING.md E1–E4); no app change.

  • E1 CHANGELOG.md: [1.1.1] - 2026-10-08 (an empty [Unreleased] already exists). README.md: "Latest release: 1.1.1 (2026-10-08)" and the status paragraph.
  • E2 RELEASING.md §13: the Release log row — build 86a6fb3 (v1.1.1), APK 062f35b3…f1d0 (the downloaded release asset checked equal), certificate a7530f5c…c79d8dcb, capture CAP-071, merge commit f359aa2, D4 via Obtainium.
  • E3 ai-sessions/0080 RESULT: Commits back-filled (a84be2d, 4611885, ac1d1e3) and the release steps; INDEX row. TODO.md §1 was already empty.
  • E4 scripts/release_notes.template: the 1.1.1 "New in" and "Known issues" lines removed.

scripts/lint_docs.py → clean; ensure_footers.py → nothing to add.

🤖 Generated with Claude Code

…emplate

Why: RELEASING.md E1–E4. 1.1.1 was published on 2026-10-08 (tag v1.1.1 on the
build commit 86a6fb3; the downloaded APK's SHA-256 equals the tested build) and
the maintainer updated to it with Obtainium. So the CHANGELOG block gets its
date, the README points at the new latest release, the Release log gets its
row, the ai-sessions/0080 RESULT gets its commit hashes and the release steps,
and the release-notes template drops the 1.1.1 lines for the next version.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@tedsluis
tedsluis merged commit b348057 into main Oct 8, 2026
1 check passed
@tedsluis
tedsluis deleted the docs/1.1.1-after-publish branch October 8, 2026 19:51
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