Skip to content

[LFXV2-1092] Use git tag for dynamic helm chart versioning#6

Merged
andrest50 merged 2 commits intomainfrom
andrest50/chart-version
Mar 2, 2026
Merged

[LFXV2-1092] Use git tag for dynamic helm chart versioning#6
andrest50 merged 2 commits intomainfrom
andrest50/chart-version

Conversation

@andrest50
Copy link
Contributor

@andrest50 andrest50 commented Feb 18, 2026

Summary

Implement dynamic helm chart versioning to match the pattern established in voting service PR #13, where chart versions are automatically derived from git tags rather than manually managed in Chart.yaml.

Ticket

LFXV2-1092

Changes

GitHub Actions Workflow Update

Updated the "Prepare versions and chart name" step to extract chart version from git tag instead of Chart.yaml.

Helm Chart Configuration

  • Reset version from 0.1.2 to 0.0.1 (placeholder value)
  • Added comment explaining the version is dynamically replaced during release
  • Version should never be manually incremented going forward

Documentation Update

Added documentation explaining chart versioning behavior: The chart version in Chart.yaml is set to 0.0.1 and should not be manually incremented. During the release process, the chart version is dynamically set to match the Git tag version.

Benefits

  • Single Source of Truth: Git tags drive both app version and chart version
  • Eliminates Manual Errors: No need to remember to bump Chart.yaml version
  • Consistency: Chart version always matches the release tag version
  • Standardization: Matches the pattern used in voting service and other v2 services

Example

When creating a release:

  • Create git tag: v0.1.6
  • Workflow automatically sets chart_version: 0.1.6
  • Published helm chart has version 0.1.6

Related

- Update ko-build-tag.yaml to use git tag instead of Chart.yaml version
- Set Chart.yaml version to 0.0.1 with comment explaining dynamic replacement
- Add documentation to README about chart versioning process

This matches the implementation in voting service PR #13, ensuring
consistent versioning across services where the chart version is
automatically set from the git tag during release.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Signed-off-by: Andres Tobon <andrest2455@gmail.com>
Copilot AI review requested due to automatic review settings February 18, 2026 17:30
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This pull request implements dynamic Helm chart versioning to align with the standardized pattern used across LFX v2 services. Instead of manually managing chart versions in Chart.yaml, versions are now automatically derived from git tags during the release process, establishing git tags as the single source of truth for versioning.

Changes:

  • Modified GitHub Actions workflow to extract chart version from git tags instead of Chart.yaml
  • Reset Chart.yaml version from 0.1.2 to 0.0.1 (placeholder) with explanatory comment
  • Added documentation to README explaining the dynamic versioning behavior

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File Description
.github/workflows/ko-build-tag.yaml Updated to extract chart version from git tag (github.ref_name) instead of reading from Chart.yaml
charts/lfx-v2-survey-service/Chart.yaml Reset version to 0.0.1 placeholder with comment explaining dynamic replacement during release
README.md Added documentation explaining chart versioning process and that Chart.yaml version should not be manually incremented

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@andrest50 andrest50 merged commit eda9b47 into main Mar 2, 2026
4 of 5 checks passed
@andrest50 andrest50 deleted the andrest50/chart-version branch March 2, 2026 16:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants