🔖 chore(release): prepare v0.18.0 - #302
Merged
Merged
Conversation
Version numbers are not bumped by CI (docs/RELEASE.md), so the chart version, appVersion, the Artifact Hub image tag and the changelog section land on main first; the tag follows. The tranche is 69 commits since v0.17.0 and earns a minor rather than a patch -- it carries a new status API field, a new controller flag, and behaviour changes an operator can observe: - KollectTarget gains `status.collectedCount` + `collectedCountUpdatedAt` and COLLECTED/UPDATED printer columns, so the reported count tracks the live matched set instead of freezing at the last spec reconcile. - `--target-count-resync` (chart: `controller.targetCountResync`). - Leader-election timings are tunable and the metrics endpoint is authorizable from what the chart ships -- both landed after v0.17.0. - The published chart's CRDs now match the API. They had drifted 71 lines behind, including `extractionFailures`/`lastExtractionError`, which the API server was silently pruning on write for chart installs. - Go 1.26.6 clears 7 called stdlib advisories in the shipped image. `hack/check-changelog-release-guard.sh` confirms all 25 released sections survived regeneration. `task changelog:verify` is red here and that is the documented release ordering, not a defect: git-cliff regenerates from a HEAD where v0.18.0 does not exist yet and renders the section as `[Unreleased]`. `.github/workflows/preflight.yaml:52-58` deliberately does not gate it, and changelog-sync heals main after the tag lands. Gates on this commit: verify (incl. the new chart-CRD drift gate), lint, lint:markdown, helm-test 40/40 -- all green.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
The Docs job went red on the version bump, exactly as designed:
docs launch truth: roadmap Last verified line does not identify released v0.18.0
docs launch truth: announcement bar does not target released v0.18.0
`hack/test/docs_launch_truth_test.sh` derives the released version from
CHANGELOG.md and then asserts that the reader-facing surfaces agree with it. The
bump moved the changelog to 0.18.0 and left three surfaces claiming 0.17.0, so
the site would have announced a release that is not the one being cut.
Updated to match: the `Last verified` lines in docs/ROADMAP.md and
docs/roadmap/planned-features.md, and the announcement bar in overrides/main.html
(both the release-notes link and the version it names).
`hack/test/docs_launch_truth_test.sh` now reports
`ok (released v0.18.0; chart v0.18.0)`.
|
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.
Version numbers are not bumped by CI (
docs/RELEASE.md), so the chart version, appVersion, Artifact Hub image tag and changelog section land onmainfirst; the tag follows.69 commits since v0.17.0. Minor, not patch — it carries a new status API field, a new controller flag, and operator-visible behaviour changes.
Highlights
KollectTarget.status.collectedCount+collectedCountUpdatedAt, COLLECTED/UPDATED printer columnskubectl get kollecttargetused to report 1000 while collecting 1200.--target-count-resync/controller.targetCountResync/metricsreturned 403 to everything.extractionFailures/lastExtractionError— which the API server was silently pruning on write for chart installs.go.modand both Dockerfiles).Also: the lab harness is no longer Kind-only (default-deny substrate allowlist), the extractor budget can now actually fail, and chart-CRD drift is gated in
preflightso this cannot recur silently.Release-ordering note
task changelog:verifyis red on this branch and that is expected, not a defect: git-cliff regenerates from a HEAD wherev0.18.0does not exist yet and renders the section as[Unreleased]..github/workflows/preflight.yaml:52-58deliberately does not gate it, andchangelog-synchealsmainafter the tag lands. This is the exact scenariohack/check-changelog-release-guard.shwas written for — it confirms all 25 released sections survived regeneration.Gates
task verify(including the new chart-CRD drift gate),task lint,task lint:markdown,task helm-test(40/40) — all green.