Release Process

Bump dependencies

To bump all (execpt the /build module's) dependencies run:

./goyek.sh bump mod

Verify if wizard and official docs needs any adjustments. Create a Pull Request with documentation updates in splunk/public-o11y-docs if necessary. Contact @splunk/gdi-docs team if needed.
Create a new release branch. I.e. git checkout -b release-X.X.X main.
Update the version in versions.yaml
Run the pre-release step which updates go.mod and version.go files in modules for the new release.
```
./goyek.sh prerelease
```
Merge the branch created by multimod into your release branch.
Update CHANGELOG.md with new the new release.
Push the changes and create a Pull Request on GitHub.

Once the Pull Request with all the version changes has been approved and merged it is time to tag the merged commit.

IMPORTANT: It is critical you use the same tag that you used in the Pre-Release step! Failure to do so will leave things in a broken state.

IMPORTANT: There is currently no way to remove an incorrectly tagged version of a Go module. It is critical you make sure the version you push upstream is correct. Failure to do so will lead to minor emergencies and tough to work around.

Run for the the commit of the merged Pull Request.

./goyek.sh -commit <commit> -remote <remote> release

Create a Release for the new <new tag> on GitHub. The release body should include all the release notes for this release taken from CHANGELOG.md.

Bump versions in the following examples: