chore(main): release 0.5.0 - #70
Merged
rexionmars merged 3 commits intoAug 31, 2026
Merged
Conversation
github-actions
Bot
force-pushed
the
release-please--branches--main--components--TERRA
branch
from
August 31, 2026 12:12
d47190a to
f4726db
Compare
Each appeared once for the commit that made the change and once for the merge commit of the pull request carrying it -- release-please reads both, and gives the merge the PR's title, so a PR holding a single conventional commit is counted twice. All four are that shape: #54, #56, #60 and #67. The merge-commit line is dropped; both point at the same work and the original commit is the more precise of the two. DONE BY HAND FOR THE LAST TIME. Merge commits are now disabled on the repository, so squash and rebase are the only ways a pull request can land and neither creates a second conventional commit. That does not reach these four: the merges that produced them are already in the history and stay there, so they would return in every regeneration of this proposal. They are removed here because this is the release that carries them.
…ository Seven items out of a hundred, and the cut is the work. The changelog beside this carries 42 features and 58 fixes; What's New answers a different question, asked by someone who has just updated and wants to know what is different in front of them. A fix is not that -- it says something was broken -- so the fixes are out by rule rather than by judgement, and the judgement is which of the 42 a reader would notice. The two voices are not a transformation of each other. `**energy:** the run reads in a column of its own` is a commit subject: a scope, a hash, and the assumption that the reader knows the code. The entry it becomes has to say where the thing was before and why moving it mattered, which the changelog never recorded. That is why this is not generated. IT IS IN THE RELEASE PROPOSAL, not on main, and that is the ordering the version check demands. main still says 0.4.0 in version.go, and an entry for 0.5.0 there would sit ahead of the authority and fail check:version until the proposal merged. Here the bump and the notes land together and neither branch is ever inconsistent. The title names the release by what it is: work now belongs to the ground it was made over, and the ground is drawn on a planet. Draugen is the still that names it -- see brand.ts and the manifest in splashBackground.ts.
Contributor
Author
|
🤖 Created releases: 🌻 |
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
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.
🤖 I have created a release beep boop
0.5.0 (2026-08-31)
Features
Bug fixes
Performance
This PR was generated with Release Please. See documentation.