You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This document summarizes the process of doing a new release of this project.
3
+
Release can only be performed by Datadog maintainers of this repository.
4
+
5
+
## Schedule
6
+
This project does not have a strict release schedule. However, we would make a release at least every 2 months.
7
+
- No release will be done if no changes got merged to the `master` branch during the above mentioned window.
8
+
- Releases may be done more frequently than the above mentioned window.
9
+
10
+
### Prerequisites
11
+
- Ensure all CIs are passing on the master branch that we're about to release.
12
+
13
+
## Release Process
14
+
15
+
The release process is controlled and run by GitHub Actions.
16
+
17
+
### Prerequisite
18
+
19
+
1. Make sure you have `write_repo` access.
20
+
1. Share your plan for the release with other maintainers to avoid conflicts during the release process.
21
+
22
+
### Update Changelog
23
+
24
+
1. Open [prepare release](https://github.com/DataDog/datadog-api-client-rust/actions/workflows/prepare_release.yml) and click on `Run workflow` dropdown.
25
+
1. If needed, enter new version identifier in the `New version number` input box (e.g. `1.10.0`). The default updates the previous minor.
26
+
1. Trigger the action by clicking on `Run workflow` button.
27
+
28
+
### Review
29
+
30
+
1. Review the generated pull-request for `release/<New version number>` branch.
31
+
1. If everything is fine, merge the pull-request.
32
+
1. Check that the [release](https://github.com/DataDog/datadog-api-client-rust/actions/workflows/release.yml) action created a new release on GitHub.
33
+
1. A GitHub action will kick off that builds and publishes this tag to crates.io. Confirm the [release is available](https://crates.io/crates/datadog-api-client)
0 commit comments