This document is intended for Nautobot ChatOps maintainers and covers the steps to perform when releasing new versions.
Minor Version Bumps¶
Required Python packages are maintained in two files:
Python packages are defined inside
[tool.poetry.dependencies] section of this file contains a list of all the packages required by Nautobot ChatOps.
Where possible, we use tilde requirements to specify a minimal version with some ability to update, for example:
This would allow Poetry to install
The other file is
poetry.lock, which is managed by Poetry and contains package names, versions, and other metadata.
Each of the required packages pinned to its current stable version. When Nautobot is installed, this file is used to resolve and install all dependencies listed in
pyproject.toml, but Poetry will use the exact versions found in
poetry.lock to ensure that a new release of a dependency doesn't break Nautobot ChatOps.
You must never directly edit this file. You will use
poetry update commands to manage it.
Every minor version release should refresh
poetry.lock, so that it lists the most recent stable release of each package. To do this:
- Review each requirement's release notes for any breaking or otherwise noteworthy changes.
poetry update <package>to update the package versions in
- If a required package requires updating to a new release not covered in the version constraints for a package as defined in
Django ~3.1.7would never install
Django >=4.0.0), update it manually in
poetry installto install the refreshed versions of all required packages.
- Run all tests and check that the UI and API function as expected.
You may use
poetry update --dry-run to have Poetry automatically tell you what package updates are available and the versions it would upgrade.
Link to the Release Notes Page¶
Add the release notes (
docs/release-notes/X.Y.md) to the table of contents within
mkdocs.yml, and point
index.md to the new file.
Verify and Revise the Installation Documentation¶
Follow the installation instructions to perform a new production installation of Nautobot ChatOps.
The goal of this step is to walk through the entire install process as documented to make sure nothing there needs to be changed or updated, to catch any errors or omissions in the documentation, and to ensure that it is current with each release.
mkdocs serve in your development environment to start the documentation server! This allows you to view the documentation locally and automatically rebuilds the documents as you make changes.
Commit any necessary changes to the documentation before proceeding with the release.
Close the Release Milestone¶
Close the release milestone on GitHub after ensuring there are no remaining open issues associated with it.
Verify CI Build Status¶
Ensure that continuous integration testing on the
develop branch is completing successfully.
Bump the Version¶
Update the package version using
poetry version. This command shows the current version of the project or bumps the version of the project and writes the new version back to
pyproject.toml if a valid bump rule is provided.
The new version should ideally be a valid semver string or a valid bump rule:
prerelease. Always try to use a bump rule when you can.
Display the current version with no arguments:
Bump pre-release versions using
For major versions, use
For patch versions, use
And lastly, for patch versions, you guessed it, use
Please see the official Poetry documentation on
version for more information.
Update the Changelog¶
This example uses 1.4.3, but change the version number to match your version.
Create a release branch off of
git checkout -b release-1.4.3 develop)
Generate release notes with
towncrier build --version 1.4.3 and answer
yes to the prompt
Is it okay if I remove those files? [Y/n]:. This will update the release notes in
docs/admin/release_notes/version_1.4.md, stage that file in git, and
git rm all the fragments that have now been incorporated into the release notes.
invoke markdownlint to make sure the generated release notes pass the linter checks.
Check the git diff to verify the changes are correct (
git diff --cached).
Commit and push the staged changes.
The changelog must adhere to the Keep a Changelog style guide.
Submit Pull Requests¶
Submit a pull request to merge your release branch into
develop. Once merged, submit another pull request titled
**"Release vX.Y.Z"** to merge the
develop branch into
main. Copy the documented release notes into the pull request's body.
Once CI has completed on the PR, merge it.
Create a New Release¶
Draft a new release with the following parameters.
- Tag: Current version (e.g.
- Title: Version and date (e.g.
v1.0.0 - 2021-06-01)
Copy the description from the pull request to the release.
Bump the Development Version¶
poetry version patch to bump the version to the next release and commit it to the
For example, if you just released