chore: upgrade headscale to v0.29.3 - #33
Merged
Merged
Conversation
Bump the image tag and appVersion from v0.28.0 to v0.29.3 and the chart version to 0.3.0. The chart's default config sets no keys that 0.29 removed or renamed (randomize_client_port, oidc.expiry, ephemeral_node_inactivity_timeout), and the auto-generated policy uses no wildcards, so it is unaffected by the new `*` semantics. Document those breaking changes plus the strict one-minor-at-a-time upgrade path and the new trusted_proxies option in an "Upgrading to headscale 0.29" README section for users who override config or ship their own policy. Verified with helm lint, helm template (default, ingress+ui+policy, and client-only), and hack/kind-smoke.sh --with-client.
The published chart version comes from the git release tag: the publish
workflow runs `helm package --version "${CHART_VERSION}"`, so `version:`
in Chart.yaml is never used. Revert the 0.3.0 bump from the previous
commit, correct the AGENTS.md instruction that asked for it, and drop
the chart-version references from the upgrade notes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
headscale released 0.29.x; the chart still shipped
v0.28.0.Changes
appVersionandimage.tagtov0.29.3(latest upstream release).README.md.gotmpland regenerateREADME.md.AGENTS.mdinstruction that asked for a manualChart.yamlversion bump — the published chart version comes from the release tag viahelm package --versioninpublish-helm-chart.yaml, so that field is inert.User impact
The chart's own defaults set none of the config keys 0.29 removed or renamed (
randomize_client_port,oidc.expiry,ephemeral_node_inactivity_timeout), and the auto-generated policy uses no wildcards, so it is unaffected by the new*semantics. Users who overrideconfigor ship their own policy do need to act, so the README now documents:config.trusted_proxies, needed for real client IPs behind the ingress.Validation
helm lint headscale/— clean (only the pre-existing "icon is recommended" info).helm templatefor default,ingress+ui+policy, and client-only (server.enabled=false) — all render.hack/kind-smoke.sh --with-client— passed end-to-end on the new image, including the idempotent secondhelm upgrade.🤖 Generated with Claude Code