you can publish changes before releasing them!

This is cool. The changelog’s main purpose is to serve as a source for a Feed. Because I think modifications is more interesting than new articles. But the way I have it set up (see =>24uc-d0a), you can totally publish changes to the web server before ‘releasing’ them. They will get picked up later, because you’re comparing things with the git log since the last release.

Let me test this out.

I’m going to publish this note; and I’m going to make some minor textual changes to the previous note; and then I’m going to see if my git log command lets me create a release after the fact.

Also, any changes you don’t feel like including in an explicit commit – some really small typo, for example – still gets included in the git history as part of the ‘sweep up’ release commit. So the changes are all auditable, but you don’t overload yourself with classifying every tiny little fixup.

yeah, that worked.

I also fixed a typo in a link on the Changelog page, after releasing. So now there is a change which will float around until later. I could commit it in a loose commit, if I wanted to. I’ll just leave it for now. This addition to this file (after the horizontal line) is visible on the public site, but ‘unreleased’ as of 2024-10-09 16:25 UTC+2. Just to show that it’s possible. Normally I’d just leave tiny inconsequential changes in that status. But I’ve worked on this enough for today, time to do other things.