Skip to content

chore: sync chart version and README with v0.8.0 - #95

Merged
jtslear merged 1 commit into
mainfrom
skarbek/sync-chart-version-v0-8-0
Oct 16, 2026
Merged

jtslear merged 1 commit into
mainfrom
skarbek/sync-chart-version-v0-8-0

Conversation

@jtslear

@jtslear jtslear commented Oct 16, 2026

Copy link
Copy Markdown
Collaborator

Summary

Commit the output of make chart/version-sync and make readme for the v0.8.0 tag:

  • coder-observability/Chart.yaml: 0.7.5 to 0.8.0
  • README.md: install command --version 0.7.5 to --version 0.8.0

Why

make lint sets Chart.yaml and the README from the latest stable tag, then check-unstaged fails if a file changed. Nothing updates the files when a tag is cut, so main fails lint after every release until a sync commit lands. v0.8.0 points at the #88 merge, where the files still said 0.7.5. The Lint run on the #89 merge failed for this reason, and so does every open PR.

The published chart is not affected: scripts/publish.sh runs helm package --version=<tag>.

Test

make lint with helm 3.17.4 and yq 4.42.1 (the CI versions): exit 0, no unstaged changes.

Notes

The Makefile already has a TODO to automate this on release. That is out of scope here.

make lint syncs Chart.yaml and the README install command to the latest
stable tag. The v0.8.0 tag is newer than the committed files, so
check-unstaged fails on main and on every pull request.

Commit the output of make chart/version-sync and make readme.
@jtslear

jtslear commented Oct 16, 2026

Copy link
Copy Markdown
Collaborator Author

When I tagged 0.8.0, I was unaware of this:

The Makefile already has a TODO to automate this on release. That is out of scope here.

@dannykopping

Copy link
Copy Markdown
Collaborator

When I tagged 0.8.0, I was unaware of this:

Gets me every time 😁

@jtslear
jtslear merged commit 938aba9 into main Oct 16, 2026
1 check passed
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.

2 participants