From 87d8fc6151cf043310751eb7e3f223f09cf0f6c7 Mon Sep 17 00:00:00 2001 From: Steve Nolen Date: Wed, 4 Feb 2026 09:24:38 -0500 Subject: [PATCH] add some extra details about releases --- CONTRIBUTING.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index d2a03f41..6f776c58 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -11,6 +11,7 @@ Welcome! We appreciate your interest in contributing to the Team Operator projec - [Testing](#testing) - [Pull Request Process](#pull-request-process) - [Code Review Guidelines](#code-review-guidelines) +- [Releasing](#releasing) - [Getting Help](#getting-help) ## Project Overview @@ -352,6 +353,18 @@ We follow specific guidelines for code review. For detailed review standards, se - Personal preferences without clear benefit - Theoretical concerns without concrete impact +## Releasing + +Releases are automated via [semantic-release](https://semantic-release.gitbook.io/) when commits are merged to `main`. Version bumps are determined by conventional commit prefixes: + +- `fix:` → patch (1.0.0 → 1.0.1) +- `feat:` → minor (1.0.0 → 1.1.0) +- `feat!:` or `BREAKING CHANGE:` → major (1.0.0 → 2.0.0) + +The release workflow updates the changelog, tags the release, publishes the Helm chart to GHCR, and notifies downstream repos. + +To manually trigger a release: `gh workflow run release.yml` + ## Getting Help If you have questions or need help: