This document summarizes the process of doing a new release of this project. Release can only be performed by Datadog maintainers of this repository.
This project does not have a strict release schedule. However, we would make a release at least every 2 months.
- No release will be done if no changes got merged to the
masterbranch during the above mentioned window. - Releases may be done more frequently than the above mentioned window.
Our team will trigger the release pipeline.
- Install datadog_checks_dev using Python 3.
- See changes ready for release by running
ddev release show changes . --tag-prefix v --since <CURRENT_VERSION>at the root of this project. Add any missing labels to PRs if needed. - Run
ddev release changelog . <NEW_VERSION> <CURRENT_VERSION> --no-semverto update theCHANGELOG.mdfile at the root of this repository - Commit the changes to the repository in a release branch and open a PR.
- Ensure CI passes fully here, this is the commit that will be released!
- Ensure the documentation builds are passing
- Get this PR approved and merged
- Create the release on GitHub. Example
- A github action will kick off that builds and publishes this tag to PyPI. Confirm the release is available