Add a changelog, and say where it is - #113
Merged
Merged
Conversation
Five releases went out in a day with release notes that were install instructions and checksums. Useful for installing; useless for deciding whether to. Nothing said what changed between v0.1.0 and v0.1.4, and nothing said what has landed since. CHANGELOG.md covers every release newest first, grouped by what it would mean to someone running Colonizer rather than by commit order, with the pull request behind each line. Anything that could cost work — a colony, a worktree, a setting — is under "Take care" rather than left to be discovered. v0.1.0 is written as what the first release could do, not as its 62 commits. The Unreleased section is what is on main and not yet tagged, which is how a person finds out whether the thing they are waiting for has shipped. Note for whoever cuts the next release: the five existing tags point into the history from before it was rewritten, so none of them is an ancestor of main and `git describe --tags main` finds nothing. The trees are identical — the rewrite only changed commit messages — so re-pointing them at their twins on main would be exact, and would also let a build stamp the tag it came from instead of falling back to the crate version.
ParallelEntrepreneur
added a commit
that referenced
this pull request
Sep 23, 2026
Five releases went out in a day with release notes that were install instructions and checksums. Useful for installing; useless for deciding whether to. Nothing said what changed between v0.1.0 and v0.1.4, and nothing said what has landed since. CHANGELOG.md covers every release newest first, grouped by what it would mean to someone running Colonizer rather than by commit order, with the pull request behind each line. Anything that could cost work — a colony, a worktree, a setting — is under "Take care" rather than left to be discovered. v0.1.0 is written as what the first release could do, not as its 62 commits. The Unreleased section is what is on main and not yet tagged, which is how a person finds out whether the thing they are waiting for has shipped. Note for whoever cuts the next release: the five existing tags point into the history from before it was rewritten, so none of them is an ancestor of main and `git describe --tags main` finds nothing. The trees are identical — the rewrite only changed commit messages — so re-pointing them at their twins on main would be exact, and would also let a build stamp the tag it came from instead of falling back to the crate version. Co-authored-by: Nick <40026523+Nick-CHI@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Five releases went out in a day. Their notes are install instructions and checksums — useful for installing, useless for deciding whether to. Nothing said what changed between
v0.1.0andv0.1.4, and nothing said what has landed since.What it is
CHANGELOG.md, newest first, grouped by what a line means to someone running Colonizer rather than by commit order, with the pull request behind each line.mainand not yet tagged — how a person finds out whether the thing they are waiting for has shipped.v0.1.0is written as what the first release could do, not as its 62 commits.The README now points at it.
One thing for whoever cuts the next release
The five existing tags point into the history from before it was rewritten. None of them is an ancestor of
main:The trees are identical —
v0.1.4^{tree}and its twin onmainare both371545c, because the rewrite only changed commit messages — so re-pointing the tags at their twins would be exact, not a fudge.It matters beyond tidiness: #110 stamps each build with
git describe, so every build frommaintoday falls back to the crate version and cannot tell a release apart from a build after it. The update check still works (that fallback was designed in), but the version it reports is less precise than it should be.I have not re-pointed them: that is a force-update of published release tags on a public repository, and it is your call.
Verified
Every
#nnnlink resolves to a merged pull request in this repository, and the release ranges were taken from the tags rather than from memory.