Uh oh!
There was an error while loading. Please reload this page.
chore(chart): roll ingestor tag 0.6 → 0.7, bump chart 1.9.2 → 1.9.3 - #331
Merged
Conversation
data-ingestors 0.7.0 is released (multi-arch ghcr :0.7, PyPI, GitHub Release v0.7.0). Move the ingestor pin so spawned ingestion Jobs pick up 0.7 — tabular schema-inference rules (data-ingestors#349), the semseg mask_id contract (#358), and the minimum-image-size floor (#348). TSC (#359) was deferred and is not in 0.7.0. Standard 3-spot bump (digest stays "" = floating, auto-rolls on next submit; :0.7 is multi-arch so ingestor-multiarch CI passes): - client/values.yaml images.ingestor.tag 0.6 → 0.7 (+ rationale comment) - jobs-manager-deployment.yaml INGESTOR_IMAGE_TAG default 0.6 → 0.7 so a --reuse-values upgrade can't revert prod to the stale line - jobs_manager_test.yaml default-tag golden 0.6 → 0.7 (the 0.4 override-test assertion is unchanged) helm-unittest: 267/267 pass. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The ingestor 0.6 → 0.7 tag roll needs a new chart version to publish and reach prod — the chart releases on a GitHub Release → gh-pages package that fleet auto-upgrade consumes, so an unchanged version wouldn't ship. Same bundling as the 0.5 → 0.6 rollout (#323, which bumped 1.9.0 → 1.9.1). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
LukasWodka
approved these changes
Jul 10, 2026
Uh oh!
There was an error while loading. Please reload this page.
This was referenced Jul 10, 2026
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Closes#330.
Rolls the spawned-ingestor pin to the 0.7 line now that data-ingestors 0.7.0 is released (multi-arch ghcr
:0.7, PyPI, GitHub Release v0.7.0). Until this merges + syncs tomain, prod keeps spawning:0.6.0.7.0 brings tabular schema-inference rules (data-ingestors#349), the semantic-segmentation mask_id contract (#358), and the minimum-image-size floor (#348, incl. the min_size config-validation hardening). TSC #359 was deliberately deferred — it's not in 0.7.0.
The standard 3-spot bump
client/values.yamlimages.ingestor.tag0.6→0.7(+ rationale comment refresh)client/templates/jobs-manager-deployment.yamlINGESTOR_IMAGE_TAGdefault0.6→0.7— so ahelm upgrade --reuse-valuescan't revert prod to the stale lineclient/tests/jobs_manager_test.yamldefault-tag golden0.6→0.7(the0.4override-test assertion is untouched)digeststays""(floating mode) → auto-rolls on the next ingestion submit,imagePullPolicy=Always.Verification
:0.7confirmed multi-arch (linux/amd64 + linux/arm64) →ingestor-multiarchCI passes.helm unittest client: 267/267 pass.0.6pin anywhere in the chart / env value files.Chore PR to
develop(no chart-version bump). Prod ships via the subsequent Sync develop → main PR.Note
Low Risk
Helm default/tag wiring only; ingestion behavior changes are intentional with data-ingestors 0.7.0 and do not touch auth or core control-plane paths.
Overview
Bumps the default spawned ingestor image from the
0.6to the0.7floating tag so jobs-manager creates ingestion Jobs againstghcr.io/tracebloc/ingestor:0.7(digest still empty →imagePullPolicy=Always).The change is applied in the usual three places:
images.ingestor.tagin values, theINGESTOR_IMAGE_TAGtemplate default (so--reuse-valuescannot fall back to0.6), and the helm unittest expectation for the default-tag case. values comments are refreshed to document why the chart tracks the 0.7 line (submit-vs-run catalogue alignment).The chart version/appVersion move 1.9.2 → 1.9.3 in
Chart.yamlis included in this diff.Reviewed by Cursor Bugbot for commit c36ee21. Bugbot is set up for automated code reviews on this repo. Configure here.