Skip to content

chore(release): prepare v1.27.0 - #436

Merged
bmscomp merged 2 commits into
mainfrom
chore/release-v1.27.0
Oct 20, 2026
Merged

bmscomp merged 2 commits into
mainfrom
chore/release-v1.27.0

Conversation

@bmscomp

@bmscomp bmscomp commented Oct 20, 2026

Copy link
Copy Markdown
Owner

Release prep for v1.27.0: image and kates-tester pins, chart versions and version tables. There are 29 commits since v1.26.0, almost all of them conformity.

Checked locally

  • scripts/check-versions.sh, gen-chart-table.sh --check and gen-version-matrix.sh --check all pass.
  • helm lint passes on kates and strimzi-operator. The other three need their dependencies built, so CI lints them.
  • main was green on every workflow at 36d2699.

Next: after merge, tag v1.27.0 on the merge commit to start the Release workflow. HOMEBREW_TAP_TOKEN was renewed on 2026-10-18, and v1.26.0's tap update and brew smoke test passed with it.

Image and kates-tester pins move to 1.27.0: the kates chart (0.11.6,
appVersion, image tags, README), kates/k8s/deployment.yaml, the four
Strimzi charts (strimzi-operator 0.3.6, kafka-cluster 1.0.10,
connect-cluster 2.1.8, mirror-maker2 0.11.6, each with a change entry),
the 12 Litmus experiment pins, the registry docs and runbook, the README
chart table and the book's version matrix. Nothing under tester/ moved
since 1.26.0.
Since #416 the Kind smoke job deploys Strimzi through
deploy-kafka-generic.sh, and strimzi-operator's CRD hook runs the
kates-tester image the charts pin. On a release PR that pin names the
tag the release has yet to publish, so ghcr.io answers 404 and the
install timed out in pre-install ("timed out waiting for the
condition"), as it did on #436. The job now builds the pinned tag from
tester/ and loads it into its kind cluster (ci-test) before the deploy,
as ci-kafka-charts.yml and ci-mirror-maker2.yml already do.
@bmscomp
bmscomp merged commit f4dfc7d into main Oct 20, 2026
62 checks passed
bmscomp added a commit that referenced this pull request Oct 21, 2026
Since #416 the Kind smoke job deploys Strimzi through
deploy-kafka-generic.sh, and strimzi-operator's CRD hook runs the
kates-tester image the charts pin. On a release PR that pin names the
tag the release has yet to publish, so ghcr.io answers 404 and the
install timed out in pre-install ("timed out waiting for the
condition"), as it did on #436. The job now builds the pinned tag from
tester/ and loads it into its kind cluster (ci-test) before the deploy,
as ci-kafka-charts.yml and ci-mirror-maker2.yml already do.
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.

1 participant