Repository navigation
release(1.1.34): mirror Helm 1.1.34 pins (collectors sha-0a9cd59, cli-v0.6.8) - #101
Merged
Merged
Conversation
…-v0.6.8) Same pin set as tetrix-ee-helm-chart 1.1.34: collectors move from sha-41aaa36 to sha-0a9cd59 (tetrix-collectors main 0a9cd59, publish-image run 44229291489). It bakes the cli-v0.6.8 CLI (Vue/Svelte script-block fix) and keeps a GitLab budget question alive across a sync that dies before asking. Every other first-party image is unchanged. VERSION is 1.1.34, and assert-published-pins.sh requires the new set (its success line named 1.1.32 and now names 1.1.34). README keeps 1.1.33 as the latest published release; install examples are unchanged. No migration, no new env. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Hhday2KdaRvbJoPXakUJkY
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
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.
What
Mirrors the Helm 1.1.34 pin set. Only the collectors image moves:
sha-41aaa36→sha-0a9cd59(tetrix-collectors main0a9cd59, publish-image run 44229291489, GHCR indexsha256:4335c90f004f…).cli-v0.6.8: in a Vue or Svelte file, a<script>inside an attribute value no longer swallows or cuts the script block (tetrix-ee#259).Every other first-party image is unchanged. No migration (schema stays
0049_source_packs), no new env.Files
docker-compose.yml,.env.example: collectors defaultsha-0a9cd59.VERSION: 1.1.34.scripts/assert-published-pins.sh: requires the new set. Its success line said 1.1.32 and now says 1.1.34.README.md: a 1.1.34 section. 1.1.33 stays the latest published release, and the install examples are unchanged until 1.1.34 is published.Note on the tag
sha-0a9cd59was first pushed by the merge build, which bakedcli-v0.6.7because the collectorsTETRIX_CLI_VERSIONActions variable overrode the build default. It was rebuilt at the same commit after the variable was fixed. Compose installs that never pulled the earlier image get the rebuilt one.Checks
scripts/assert-published-pins.sh,assert-chart-compose-collectors-env.sh,assert-daemon-config-env-complete.shandassert-postgres-healthcheck-tcp.shpass locally.assert-seaweedfs-compose-service.shneeds a Docker daemon and was not run locally.0a9cd59, worker CLIcli-v0.6.8, schema at head, aggregate healthy.diagnostics_triageover the hour after the deploy shows no new issue.Publish order
This repo's
VERSION1.1.34 and its GitHub Release go first, then the chart (deskree-inc/tetrix-ee-helm-chart, same branch name).Generated by Claude Code