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
master
branch during the above mentioned window. - Releases may be done more frequently than the above mentioned window.
- Ensure all CIs are passing on the master branch that we're about to release.
The release process is controlled and run by GitHub Actions.
- Make sure you have
write_repo
access. - Share your plan for the release with other maintainers to avoid conflicts during the release process.
- Open prepare release and click on
Run workflow
dropdown. - If needed, enter new version identifier in the
New version number
input box (e.g.1.10.0
). The default updates the previous minor. - Trigger the action by clicking on
Run workflow
button.
- Review the generated pull-request for
release/<New version number>
branch. - If everything is fine, merge the pull-request.
- Check that the release action created a new release on GitHub.
- A GitHub action will kick off that builds and publishes this tag to PyPI. Confirm the release is available