fix(ci): 🐛 disable base64 line wrapping in auth header#3
Open
omiladi wants to merge 1 commit into
Open
Conversation
iliesmrf
approved these changes
Jul 1, 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 free
to 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.
Issues liées
Issues numéro:
Quel est le comportement actuel ?
Le step Get image status (jobs build et merge) échoue systématiquement avec Error: Process completed with exit code 43.
La cause : secrets.GITHUB_TOKEN fait maintenant 426 caractères. Une fois encodé, base64 (GNU coreutils) wrap à 76 caractères et insère des \n dans la sortie. Le
header envoyé à curl devient donc multi-lignes :
Authorization: Bearer AAAA...(76 chars)
BBBB...(76 chars)
CCCC...
curl détecte des newlines dans un header HTTP, refuse la requête et sort avec CURLE_BAD_FUNCTION_ARGUMENT (exit 43) — sans même contacter le registry
(http_status=000).
Impact : le pipeline de build/push d'images est totalement bloqué sur ghcr.io.
Quel est le nouveau comportement ?
Ajout du flag -w 0 à tous les appels base64 dans build.yml (5 occurrences, jobs build et merge) pour désactiver le wrapping. Le header reste sur une seule ligne
quelle que soit la taille du token, curl accepte la requête et le check du manifest fonctionne à nouveau.
Aucun changement fonctionnel au-delà : même logique, même endpoint, même auth — juste un header valide.
Cette PR introduit-elle un breaking change ?
Autres informations