Notechondria

Version: 0.1.68 Build Date: 2026-04-23T00:00

What's Changed

Docs — release process now documented

The portal-release.yml workflow has existed since an earlier round but was never surfaced in the docs, which is why the owner "still didn't see the setup for GitHub release". This round documents what already exists and flags what's still missing.

  • New docs/deployment/release.md — full runbook for cutting a tagged release:
    • TL;DR (git tag v<VERSION> && git push origin v<VERSION>).
    • Matrix breakdown of what gets built (Linux x64/arm64, Windows x64, macOS, Android APK, iOS unsigned).
    • Manual workflow_dispatch behaviour (builds without publishing).
    • Recovery procedure when a matrix leg fails or the release already exists.
    • Pre-release checklist (VERSION bumped, version doc written, smoke tests green).
    • "Not yet automated" section listing editor/planner workflows, backend release (n/a — deploys via Northflank/Jenkins), and Windows code signing.
  • docs/SUMMARY.md indexes the new doc under Deployment.
  • docs/deployment/overview.md gets a new §2 "GitHub Release [Desktop + mobile archives]" slot; downstream sections renumbered (Cloudflare R2 is now §4, Render §5, Northflank §6, Railway §7).

Branch migration — codex → main

Per the owner's direction, the active development branch flips from codex back to main. The GitHub Release workflow triggers on v* tag push, not branch, so release mechanics are unaffected — the flip is about where day-to-day PRs target.

  • human-efforts branch created at the pre-merge main tip (2d04c0b Delete notechondria/.DS_Store) so the pre-codex state is preserved for provenance. Single-commit branch — the actual "human effort" history before codex-series development forked lives in shared ancestry at 2116e59.
  • codex (188 commits, 3f0aaf4 tip) merged into main with a merge commit (no fast-forward) so the codex history stays clearly demarcated in git log --first-parent main.
  • docs/index.md §0 "Project-specific overrides" flips the upstream-target rule: "Upstream target branch is main". Cross-reference to the release doc.

TODO updates

  • New "Release / CI" section in docs/TODO.md with the editor + planner release workflow follow-up (tag namespacing decision required — plain v* trigger would cause three workflows to race for the same release). Windows code signing listed as an open subitem.

Files Changed

  • VERSION — bumped 0.1.67 → 0.1.68.
  • docs/deployment/release.md — new runbook.
  • docs/deployment/overview.md — new §2 + renumbering.
  • docs/SUMMARY.md — Deployment index gets release.md.
  • docs/index.md — §0 upstream-target rule flipped to main.
  • docs/TODO.md — new Release / CI section with follow-ups.
  • docs/versions/0.1.68.md — this file.

Notes

  • Nothing code-level changed in this round — all docs + branch plumbing. No migrations, no frontend rebuild needed.

  • The branch operations (git branch human-efforts main, then git checkout main && git merge --no-ff codex) happen locally only. As usual I don't push; you can push human-efforts, main, and the merged main tip in whatever order you want.

  • The first release cut from this new main tip is the 0.1.68 tag — per the release runbook:

    git tag v0.1.68
git push origin v0.1.68