Repository navigation
release(1.1.30): VERSION 1.1.30 and the chart's pin set - #90
Conversation
collectors sha-7055373, daemon/remote sha-d64b4c9, front-end sha-1036d52; gateway, keycloak, the admin-api trio and audit-logs are unchanged. Same set as tetrix-ee-helm-chart#495, required by scripts/assert-published-pins.sh. The README keeps "Latest published release" and the install examples on 1.1.28 until 1.1.30 is cut. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
dmitry-grechko
left a comment
There was a problem hiding this comment.
The repin looks right. I checked that every pin matches chart#495: .env.example, all 10 collectors services in docker-compose.yml, daemon/remote, front-end and the setup.sh fallback. The publish runs check out: collectors run 41671946990 built 7055373a on main, and tetrix-ee run 40733617359 built d64b4c97 on main, both successful. 7055373 also contains 176e6c2f, so the #1295 expected-replicas reader ships in this release. CI is green.
One small thing I'd fix before tagging, inline: assert-published-pins.sh still says "Helm 1.1.29" in its error and success messages (L81, L132). Everything else is fine.
Generated by Claude Code
| @@ -81,11 +81,11 @@ for needle, label in required_env: | |||
| errors.append(f".env.example must pin {needle} (Helm 1.1.29)") | |||
There was a problem hiding this comment.
[nit] This error message still says (Helm 1.1.29), and so does the success line at L132 (public compose pins match Helm 1.1.29 published tags ...). The header comment and the required pin sets now say 1.1.30, so a failure (or a green run) on this branch names the wrong chart version. Suggest bumping both strings to 1.1.30.
Generated by Claude Code
There was a problem hiding this comment.
Fixed in 448bc67: both strings (L81 error, L132 success line) now say Helm 1.1.30, and assert-published-pins.sh prints "OK: public compose pins match Helm 1.1.30 published tags". No other 1.1.29 string is left in the script.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
sangam-deskree
left a comment
There was a problem hiding this comment.
Reviewed at 448bc67. Approved.
- Same pins as chart#495:
.env.example- every collectors service in
docker-compose.yml - daemon and remote
- front-end
- the
setup.shfallback
- The pin check is updated:
assert-published-pins.shrequires the new set in both.env.exampleand the compose defaults. - The README keeps 1.1.29's notes under 1.1.30, since 1.1.29 was never published, and lists the two additive migrations.
Note (not blocking): the README also says "Every first-party image is on its latest published build". Collectors sha-a7ddb35 (the merge of #1466) was published today after this PR was written. Please keep the wording in step with whatever chart#495 decides.
|
Merged. Your README note (and the chart's) is addressed in #91: 1.1.30 keeps |
Release candidate 1.1.30 for the public Compose bundle. It pairs with deskree-inc/tetrix-ee-helm-chart#495 and carries the same pin set.
sha-ba4a0b0sha-7055373(publish-image run 41671946990)sha-89456c6sha-d64b4c9(docker-build-push run 40733617359)sha-8161019sha-1036d52(publish-image run 40765855668)sha-6fd804d,sha-04b1e55,sha-349d602,sha-2a150ccEach tag was resolved on ghcr.io for linux/amd64 and linux/arm64. The Logto provisioner isn't part of this bundle.
Changed files:
VERSION: 1.1.29 → 1.1.30. 1.1.29 was never published.docker-compose.yml,.env.exampleandscripts/setup.sh: the new defaults.scripts/assert-published-pins.sh: requires the new set and still forbids the unpublished tags.README.md: describes 1.1.30 and the new migrations (0047,0048, both additive, run by the migrate job)."Latest published release" and the install examples in
README.md/HELM.mdstay on 1.1.28, because those must name a chart and checksum that already exist. A follow-up after both Releases are cut points them at 1.1.30.The chart's Compose twin has no change since 1.1.29 other than the pins, so nothing else needed mirroring. The collectors env lock is unchanged.
Gates, all passing:
pack-compose-bundle.sh --self-testassert-published-pins.shassert-daemon-config-env-complete.shassert-seaweedfs-compose-service.sh, both--self-testand the real runassert-postgres-healthcheck-tcp.shassert-chart-compose-collectors-env.sh, both--self-testand against the chart branchNo tag or Release is created by this PR.
🤖 Generated with Claude Code