cockroachdb / cockroachdb/helm-charts

Deprecate incrementing `version` in values.yaml for every commit?

Open
#33 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
105
Forks
152
Avg merge
4d 23h
Merged PRs (30d)
5

Description

Our [contributing guidelines](https://github.com/cockroachdb/helm-charts/blob/master/cockroachdb/CONTRIBUTING.md) require that every commit increment the `version` field in `values.yaml`. This is easy to forget, and is also a frequent source of merge conflicts.

It should be possible to only require incrementing the `version` field for backwards-incompatible changes. For minor changes which are backwards-compatible, a minor version could be generated automatically post-commit.

Jira issue: HELM-40

Contributor guide

No contributing guide indexed for this repository

Research direction

Read cockroachdb/CONTRIBUTING.md and the chart's values.yaml to confirm the current versioning requirement. Review how chart changes and releases are handled; done means an agreed, documented approach that avoids manual increments for backward-compatible changes while preserving them for incompatible changes.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm
Domain
release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.