Doc: Update to correctly explain Github releases-based workflow#212
Merged
Conversation
zephyris
force-pushed
the
docs-release-process
branch
from
9d45e90 to
d752205
Compare
Contributor
Author
|
We certainly do! Once NML 8.1 (OpenTTD/nml#399) is done, I'll test the build process then merge this. |
|
nml 0.8.1 has been released. |
zephyris
force-pushed
the
docs-release-process
branch
from
d752205 to
c172b85
Compare
rubidium42
approved these changes
Dec 2, 2025
rubidium42
left a comment
rubidium42
left a comment
There was a problem hiding this comment.
I'd merge this before the release and add any fixes/improvements afterwards.
zephyris
force-pushed
the
docs-release-process
branch
from
c172b85 to
b22cf21
Compare
PeterN
approved these changes
Dec 2, 2025
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
4 participants
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.
With the new CI configuration, releases are (well, should be, not tested!) triggered by making a new release with a new tag on Github, then publishing that release. The release documentation had not been updated to explain this process.
@TrueBrain explained this to me when setting up the CI and releases workflows. I'd stashed this update at the time, but not got around to making a PR, so it should be correct and not dependent on my memory.