Skip to content

Comments

Fix bug with non-commit based deploys; Upgrade to Node 24; Added deployment logs#14

Open
TMSCH wants to merge 3 commits intojohnbeynon:masterfrom
TMSCH:master
Open

Fix bug with non-commit based deploys; Upgrade to Node 24; Added deployment logs#14
TMSCH wants to merge 3 commits intojohnbeynon:masterfrom
TMSCH:master

Conversation

@TMSCH
Copy link

@TMSCH TMSCH commented Oct 22, 2025

The latest GitHub action was not working on my setup using image-based deploys, so this PR fixes this bug.

Took advantage of upgrading to latest support Node version, and added some logging to track deployment progress.

Thomas Césaré-Herriau and others added 3 commits October 22, 2025 13:24
The action crashes with "Unexpected end of JSON input" when the Render
API returns an empty body or non-JSON response (e.g. 429 rate limit,
502 gateway error). This is a flaky CI failure that requires manual
re-runs.

Changes:
- Add parseJsonResponse() helper that reads text first, then parses
- Move response.json() call after HTTP status checks in run()
- Include HTTP status and response body snippet in all error messages

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The Render API can return 202 Accepted with an empty body when a deploy
is queued. Previously this threw a non-JSON parse error. Now we detect
the empty body and poll the deploys list to fetch the latest deploy.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant