|
1 | | -## Releasing |
| 1 | +# Releasing |
2 | 2 |
|
3 | | -Once the changes have been merged to main it's time to release a new |
4 | | -version of the gem. |
| 3 | +> **Note:** DropletKit is deprecated (see [README](README.md)). **No new gem releases are planned.** This document is kept for maintainers handling historical releases or a final deprecation notice release. |
5 | 4 |
|
6 | | -1. Creating a PR with a semantic version bump to |
7 | | -[version](https://github.com/digitalocean/droplet_kit/blob/main/lib/droplet_kit/version.rb) |
8 | | -and all the changes being released added to the |
9 | | -[CHANGELOG](https://github.com/digitalocean/droplet_kit/blob/main/CHANGELOG.md). |
10 | | -1. After the PR has been merged, create a release on GitHub for the new version: |
11 | | - - The tag should be in the format of: vX.Y.Z |
12 | | - - You can think of X.Y.Z as such: |
13 | | - X = breaking |
14 | | - Y = feature |
15 | | - Z = bugfix |
16 | | - - The title should be in the format of: vX.Y.Z (same as tag) |
17 | | - - The description should include all the changes being released in the format of: |
18 | | - - #[PR #] - @[contributor] - [description] |
19 | | -1. When the tag is created, a GitHub Actions workflow will publish the release to rubygems. |
| 5 | +## Historical process |
| 6 | + |
| 7 | +Once changes were merged to `main`, a new gem version was released as follows: |
| 8 | + |
| 9 | +1. Create a PR with a semantic version bump to |
| 10 | + [version](https://github.com/digitalocean/droplet_kit/blob/main/lib/droplet_kit/version.rb) |
| 11 | + and all changes being released added to the |
| 12 | + [CHANGELOG](https://github.com/digitalocean/droplet_kit/blob/main/CHANGELOG.md). |
| 13 | +2. After the PR was merged, create a release on GitHub for the new version: |
| 14 | + - Tag format: `vX.Y.Z` |
| 15 | + - Version semantics: `X` = breaking, `Y` = feature, `Z` = bugfix |
| 16 | + - Release description: `#[PR #] - @[contributor] - [description]` |
| 17 | +3. When the tag was created, a GitHub Actions workflow published the release to RubyGems. |
| 18 | + |
| 19 | +## Deprecation |
| 20 | + |
| 21 | +If a final gem release is published to surface the `post_install_message` in `droplet_kit.gemspec`, follow the steps above with a patch version bump and a CHANGELOG entry documenting the deprecation notice. |
0 commit comments