Skip to content

Latest commit

 

History

History
33 lines (23 loc) · 1.61 KB

RELEASING.md

File metadata and controls

33 lines (23 loc) · 1.61 KB
Raw

Releasing

This document summarizes the process of doing a new release of this project. Release can only be performed by Datadog maintainers of this repository.

Schedule

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.

Prerequisites

  • Ensure all CIs are passing on the master branch that we're about to release.

Release Process

The release process is controlled and run by GitHub Actions.

Prerequisite

  1. Make sure you have write_repo access.
  2. Share your plan for the release with other maintainers to avoid conflicts during the release process.

Update Changelog

  1. Open prepare release and click on Run workflow dropdown.
  2. If needed, enter new version identifier in the New version number input box (e.g. 1.10.0). The default updates the previous minor.
  3. Trigger the action by clicking on Run workflow button.

Review

  1. Review the generated pull-request for release/<New version number> branch.
  2. If everything is fine, merge the pull-request.
  3. Check that the release action created a new release on GitHub.
  4. A GitHub action will kick off that builds and publishes this tag to crates.io. Confirm the release is available