This repository was archived by the owner on Oct 14, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 21
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
3 changed files
with
46 additions
and
13 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -34,6 +34,7 @@ jobs: | |
revert | ||
style | ||
test | ||
release | ||
scopes: | | ||
api | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,29 +1,61 @@ | ||
# Release | ||
|
||
VMClarity adopted the [Go MultiMod Releaser](https://github.com/open-telemetry/opentelemetry-go-build-tools/tree/main/multimod) to create a new release for each module. | ||
This document outlines the process for creating a new release for VMClarity using the [Go MultiMod Releaser](https://github.com/open-telemetry/opentelemetry-go-build-tools/tree/main/multimod). All code block examples provided below correspond to an update to version `v0.7.0`, please update accordingly. | ||
|
||
Find below the steps to create a release. | ||
## 1. Update the New Release Version | ||
|
||
## 1. Update the new release version | ||
|
||
Checkout to a new branch and update the version defined for VMClarity's module-set in `versions.yaml`. Please note that currently the same version is used for all methods. E.g. | ||
* Create a new branch for the release version update. | ||
```sh | ||
git checkout -b release/v0.7.0 | ||
``` | ||
|
||
* Modify the `versions.yaml` file to update the version for VMClarity's module-set. Keep in mind that the same version is applied to all modules. | ||
``` | ||
vmclarity: | ||
- version: v0.6.0 | ||
+ version: v0.7.0 | ||
``` | ||
|
||
Commit this change and verify the versioning with `make multimod-verify`. | ||
* Commit the changes with a suitable message. | ||
```sh | ||
git add versions.yaml | ||
git commit -m "release: update module set to version v0.7.0" | ||
``` | ||
|
||
* Run the version verification command to check for any issues. | ||
```sh | ||
make multimod-verify | ||
``` | ||
|
||
## 2. Bump All Dependencies to the New Release Version | ||
|
||
## 2. Bump all dependencies to new release version | ||
* Run the following command to update all `go.mod` files to the new release version. | ||
```sh | ||
make multimod-prerelease | ||
``` | ||
|
||
* Review the changes made in the last commit to ensure correctness. | ||
|
||
* Push the branch to the GitHub repository. | ||
```sh | ||
git push origin release/v0.7.0 | ||
``` | ||
|
||
To update all `go.mod` files with the new release version, run `make multimod-prerelease` and review the changes in the last commit. Then, create a pull request. | ||
* Create a pull request with the changes. | ||
|
||
## 3. Create and push tags | ||
## 3. Create and Push Tags | ||
|
||
Once the previous changes have been approved and merged, pull the latest changes in the `main` branch. Then, create the tags for the last commit and push them with `make multimod-push-tags`. | ||
* After the pull request is approved and merged, update your local main branch. | ||
```sh | ||
git checkout main | ||
git pull origin main | ||
``` | ||
|
||
## 4. Release | ||
* Create and push the tags for the last commit to the repository. | ||
```sh | ||
make multimod-push-tags | ||
``` | ||
|
||
Finally, create a Release on GitHub. | ||
## Post-release Checks | ||
Verify that the `Release` workflow was completed successfully in the GitHub Actions section. | ||
Ensure that the release is visible in the GitHub releases page. Additionally, check that the release description is correct and all assets are listed. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters