{"repo":"rhysmcneill/helm-semver","free":true,"listed":false,"github":"https://github.com/rhysmcneill/helm-semver","clone":"git clone https://github.com/rhysmcneill/helm-semver.git","description":"Semver release automation for Helm charts. Bumps chart versions from conventional commits (fix: → patch, feat: → minor, feat!: → major), packages and pushes to any OCI registry. Works as a GitHub Action or standalone Docker image on any CI platform.","language":"Go","stars":19,"topics":["cicd","cli","docker","github-actions","go","helm","kubernetes","semantic-release"],"license":"MIT","category":"deployment-docker-iac","readme_excerpt":"Welcome to helm-semver Semver release automation for Helm chart monorepos, single Helm charts and everything in-between. helm-semver bumps chart versions from conventional commits, packages and pushes to any OCI registry. Works as a GitHub Action or standalone Docker image on any CI platform. --- The problem Releasing a Helm chart from a monorepo today looks like this: With helm-semver : Every chart that has fix: , feat: , or feat!: commits since its last release is bumped, packaged, pushed, committed, and tagged automatically. --- Install GitHub Action: Binaries for Linux, macOS, and Windows on every release. --- Real-world use cases Monorepo: multiple charts released independently from one push The primary use case. A single push touches two charts with different commit types — each gets its own independent version bump and OCI tag. Each chart is tagged independently ( observability-v0.2.0 , my-service-v1.3.1 ) and pushed as separate OCI artifacts. No chart list to maintain — new directories are detected automatically. Single chart repo GitLab CI Bitbucket Pipelines Using ECR as the OCI registry — the natural fit for Bitbucket-based pipelines in AWS environments. See docs/ecr.md for full OIDC role setup. Dry-run as a PR gate Add helm-semver release --dry-run as a required CI check on every pull request. Reviewers see exactly which charts will be released and at what version before anything merges — no surprises on main. The PR will show a comment like: --- Why not just use ","default_branch":null,"files":null,"tree":[],"storefront":"/r/rhysmcneill","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/rhysmcneill/helm-semver/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}