Repository navigation
fix(kcl): dagger-kcl-Modul v0.132.0 -> v0.133.1 -- Rendern mit Zugangsdaten, 429 wiederholen, lesbare Fehler - #194
Merged
Conversation
…ntials, retry 429, readable errors v0.133.1 carries stuttgart-things/dagger#392: PushKustomizeBase renders with the push's credentials, kcl run retries registry rate limits (429), and a failed render reports kcl's own stderr instead of `exit code: 1` on the oras push. Same engine (v0.21.9), same oras (1.2.2). Bumped where the kcl module is pinned: call-push-kustomize (PR previews), call-go-release and call-go-microservice-release (release pushes). Refs stuttgart-things/dagger#391 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Sep 29, 2026
This branch was successfully deployed
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.
Rollout von stuttgart-things/dagger#392 (Release v0.133.1, stuttgart-things/dagger#391).
Was sich im Modul ändert
PushKustomizeBaserendert mit den Zugangsdaten des Pushs (kcl registry loginvorkcl run)kcl runwiederholt bei Registry-Drosselung (429/toomanyrequests) bis zu 8-mal mit Backoffkcl run failed: …) statt! exit code: 1amoras pushGleiche Engine (
v0.21.9,dagger.jsonunverändert), gleiches oras (1.2.2). Der Kommentar zur oras-Version incall-push-kustomize.yamlstimmt weiterhin.Wo angehoben
call-push-kustomize.yamlcall-go-release.yamlcall-go-microservice-release.yamlNur das Modul
kcl. Die anderen dagger-Module (go, trivy, crane, release …) bleiben aufv0.132.0, der Fix betrifft sie nicht.Wirkung
Die Repos rufen die Templates über
@mainauf. Der Merge wirkt also sofort auf alle, diecall-push-kustomizebzw. die Go-Releases nutzen (homerun2-*, schmetterpause, …).Nicht gelöst
Der dauerhafte Block einzelner
ghcr.io/kcl-lang/*-Pakete von heute: Er traf auch angemeldete Pulls, und acht Versuche kamen nicht durch. Dafür stuttgart-things/kcl#323 (Spiegel).🤖 Generated with Claude Code