rossoctl / rossoctl/operator

:bug: Align Helm chart version with repository release tag

Open Beginner friendly
#532 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

kind/bug
Dominant language
Go
Stars
18
Forks
50
Avg merge
3d 3h
Merged PRs (30d)
8

Description

Describe the bug

Currently, the rossoctl operator versions its Helm chart differently from the repository's tag/release version.

For example, in the 0.3.0 tagged codebase, the Chart.yaml still hardcodes the chart version as 0.2.0-alpha.24:
https://github.com/rossoctl/operator/blob/v0.3.0/charts/operator/Chart.yaml#L5

Expected behavior
The Helm chart version should match the repository release version.

Proposed Solution / Recommendation
Update to ensure the chart version matches the repo release version.

Steps To Reproduce
  1. Go to https://github.com/rossoctl/operator/blob/v0.3.0/charts/operator/Chart.yaml#L5
  2. In the 0.3.0 tagged codebase, the Chart.yaml still shows the chart version as 0.2.0-alpha.24:
Expected Behavior

The Helm chart version should match the repository release version.

Rossoctl Version

v0.3.0

Additional Context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with charts/operator/Chart.yaml at the version field referenced in the issue, then inspect the repository's release or chart packaging workflow to see how versions are set. Verify the change against the v0.3.0 tagged codebase; done means the Helm chart version matches the repository release version rather than 0.2.0-alpha.24.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, helm
Domain
devops, release
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
78/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.