fix(release): chama o deploy do Coolify com POST
Release / Plano (reaproveitar a imagem?) (push) Successful in 7s
Release / ci (push) Skipped
Release / Publica a imagem (linux/arm64) (push) Successful in 21s
Release / Cria a release no Gitea (push) Skipped
Release / Deploy no Coolify (push) Skipped

O Coolify 4.5 trocou /api/v1/deploy para POST e responde 405 ao GET, o que
derrubou o primeiro deploy automático.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Lucas RayanandClaude Opus 5.5 committed 2026-11-02 13:26:51 -03:00
1 parent b6fb230328
commit 5fba78308c
1 file changed
+1 -1
+1 -1
View File
@@ -168,7 +168,7 @@ jobs:
echo "faltam os secrets COOLIFY_URL e COOLIFY_TOKEN no repositório"; exit 1
fi
auth="Authorization: Bearer $COOLIFY_TOKEN"
dep=$(curl -fsS -H "$auth" "$COOLIFY_URL/api/v1/deploy?uuid=$APP&force=false" | jq -r '.deployments[0].deployment_uuid')
dep=$(curl -fsS -X POST -H "$auth" "$COOLIFY_URL/api/v1/deploy?uuid=$APP&force=false" | jq -r '.deployments[0].deployment_uuid')
[ -n "$dep" ] && [ "$dep" != null ] || { echo "o Coolify não devolveu um deployment"; exit 1; }
echo "deployment $dep"
# Até 15 minutos: o pull da imagem arm64 e o healthcheck cabem com folga.