chore(deps): bump dagger/kcl v0.103.0 → v0.114.0 in call-push-kustomize#90
Merged
Merged
Conversation
…kustomize v0.114.0 fixes the parameter-newline corruption bug (stuttgart-things/dagger#271, fixed by stuttgart-things/dagger#272): multi-line values from --parametersFile no longer get escaped as literal \n via the jq gsub hack, so kustomize OCIs built from KCL modules with multi-line config (e.g. an embedded YAML watch profile) ship valid block-literal scalars instead of single-quoted multi-line scalars that fold newlines into spaces on read. Surfaced by stuttgart-things/homerun2-git-pitcher#25 smoke — the git-pitcher kustomize OCI carries `config.watchConfigYaml: |` from its test profile, and all releases from v0.6.0 onward shipped a broken `data: { watch-profile.yaml: 'github:\n token: ...' }` ConfigMap that crashed the app on startup with `yaml: mapping values are not allowed in this context`. Other call-*.yaml templates that reference the kcl module (call-go-release.yaml, call-go-microservice-release.yaml at v0.82.1) only use the `semantic` function which doesn't exercise the buggy code path — left as-is for separate maintenance. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
patrick-hermann-sva
temporarily deployed
to
linting
GitHub Actions
Inactive
2 tasks
patrick-hermann-sva
added a commit
that referenced
this pull request
May 18, 2026
…ize (#91) Required follow-up to the kcl-module bump in PR #90. The kcl module's v0.114.0 release (which carries the parameter-newline fix from stuttgart-things/dagger#272) bumped its engine requirement to v0.20.8. With the previous v0.20.6 pin here, every push-kustomize workflow run fails on module load with: module requires dagger v0.20.8, but you have v0.20.6 Surfaced on the first PR that re-ran the workflow after #90 landed (stuttgart-things/homerun2-git-pitcher#30). Co-authored-by: sthings user <sthings@dev-vm3.tiab.labda.sva.de> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
49 tasks
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.
Summary
Bump
dagger-kcl-moduledefault incall-push-kustomize.yamlfromv0.103.0tov0.114.0to pick up the parameter-newline fix (stuttgart-things/dagger#271, fixed by stuttgart-things/dagger#272, released asv0.114.0).What the upstream fix does
v0.114.0 stops escaping newlines as the literal 2-character sequence
\nwhen reading--parametersFile. The oldjq -r '... gsub("\n"; "\\n") ...'hack corrupted any multi-line value: KCL received it as a single-line string with literal backslash-n chars, emitted a single-quoted multi-line scalar in the rendered ConfigMap, and downstream consumers got garbage because the YAML spec folds single-quoted multi-line scalar newlines into spaces.Concrete impact
stuttgart-things/homerun2-git-pitcherships aconfig.watchConfigYaml: |block in its test profile. Every release fromv0.6.0(April 2026) onward published a brokendata: { watch-profile.yaml: 'github:\n token: ...' }ConfigMap that crashed the app at startup withyaml: mapping values are not allowed in this context. Surfaced by stuttgart-things/homerun2-git-pitcher#25 smoke.After this bump merges and git-pitcher cuts its next release, the published kustomize OCI will ship a correct
|block-literal scalar.Scope
Only
call-push-kustomize.yamlis bumped — that's the template that exercises the buggy--parametersFilecode path. The other two templates referencing the kcl module (call-go-release.yaml,call-go-microservice-release.yamlat v0.82.1) only invoke thesemanticfunction, which doesn't go throughRun()'s parameter handling. Bumping those can be routine maintenance, separate PR.Test plan
watch-profile.yaml: |(block literal), notwatch-profile.yaml: '...'(single-quoted).Refs stuttgart-things/dagger#271
Refs stuttgart-things/dagger#272
Refs stuttgart-things/homerun2-git-pitcher#25
🤖 Generated with Claude Code