Release notes
Where stella's release notes live — the changelog at /releases, and the per-build notes on GitHub.
Release notes live in two places. Which one you want depends on what you're trying to find out.
Upgrade notes
stella.oxagen.sh/releases has one section per minor version, searchable and filterable by kind. This is the record to read when you're deciding whether to upgrade: what a version added, fixed, or changed.
It's generated straight from CHANGELOG.md
when the site builds, so the page always matches the file in the project.
Build notes
The releases page on GitHub has notes for every tagged build, generated from that build's own changes.
Every merge to main cuts a new patch release, so this is the page to use
when you're tracking down a regression or want the exact commit-level
history for one version.
Why GitHub's page and /releases differ
/releases is the curated, human-readable record, built straight from
CHANGELOG.md
so it can never fall out of sync with the project. GitHub's per-build page
is the finer-grained one, with a note for every single tagged build.
Writing an entry
Changelog entries are written by an automated process, not by individual
contributors, so every entry reads in one consistent voice. When a minor or
major version is cut,
scripts/changelog-ai.sh
drafts the section from the full set of changes, and
scripts/changelog-roll.sh
adds it under the new version heading.
If your change needs context that the code alone won't convey, put it in the pull request description. The drafter reads that too, not just the code.