|Name ||Description |
|The branch on which the release is happening. |
|The previous release's version number or the previous branch if the release is the first on that branch. |
|The Git remote for the main InspIRCd repository. |
|The new release's version number. |
- Close the release milestone on GitHub.
vendor/update to check that the vendored third-party dependencies are up to date.
tools/mkauthors to update the authors file.
tools/mkdescriptions to update the module descriptions.
tools/mkheaders to update the copyright headers.
- If ABI breakages have been made then update
- Update the version in
- Commit the changes to
- Ensure that the branch tip builds with no warnings. Checking GitHub Actions is helpful as it builds with
- Tag the release with
git tag VERSION.
git push UPSTREAM BRANCH and
git push UPSTREAM VERSION.
- Add a GitHub release for the VERSION on tag.
- Generate a list of contributors for the news post using
git log --pretty=' - %aN' PREVIOUS...VERSION | sort -fu
- Create a news post on the website using the list of contributors from the previous step.
- Mark the new news post as featured and unmark the old one.
- If the release is stable then update
misc.currentVersion in the website config to VERSION.
- Update the change log on the documentation site.
- Run Doxygen and update the API documentation site.
- If the release fixes a security vulnerability then create an advisory on the documentation site.
INSP_VERSION in the Docker container build script.
- Update the topic in
#InspIRCd.dev on ChatSpike.
- Post a link to the news post on the InspIRCd Twitter account, InspIRCd Mastodon account and, if notable, on /r/irc.