Skip to content

feat: add releasing notes and release #69

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
stevenolen merged 1 commit into from
Feb 4, 2026
Merged

feat: add releasing notes and release #69

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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:
Expand Down