You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Investigate workflow job failing on main: chooseDeployActions #85712
🐛 Error Message:
warning: Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions-ecosystem/action-get-merged-pull-request@59afe90, actions/checkout@8ade135. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
failure: The template is not valid. .github/workflows/preDeploy.yml (Line: 42, Col: 22): Error reading JToken from JsonReader. Path '', line 0, position 0.
failure: Fail to evaluate job outputs
failure: HttpError
⚠️Action Required⚠️:
🛠️ A recent merge appears to have caused a failure in the job named chooseDeployActions.
🔍 This issue has been automatically created and labeled with Workflow Failure for investigation.
This was a transient GitHub API failure, not caused by the merged PR.
Root cause: The actions-ecosystem/action-get-merged-pull-request step in chooseDeployActions threw an HttpError (visible in the job logs). Because that step failed, the downstream shouldDeploy step never ran, leaving its output empty. The fromJSON() wrapper on the job output (line 42 of preDeploy.yml) then failed trying to parse an empty string — producing the Error reading JToken from JsonReader error.
The next preDeploy run (23267436523) succeeded, confirming the API failure was transient.
Note: The fromJSON() on the SHOULD_DEPLOY output is fragile — if any earlier step fails, it will always produce this secondary error. Worth considering replacing it with a default fallback.
Activity
Julesssss commentedon Mar 18, 2026
This was a transient GitHub API failure, not caused by the merged PR.
Root cause: The
actions-ecosystem/action-get-merged-pull-requeststep inchooseDeployActionsthrew anHttpError(visible in the job logs). Because that step failed, the downstreamshouldDeploystep never ran, leaving its output empty. ThefromJSON()wrapper on the job output (line 42 of preDeploy.yml) then failed trying to parse an empty string — producing theError reading JToken from JsonReadererror.The next preDeploy run (23267436523) succeeded, confirming the API failure was transient.
Note: The
fromJSON()on theSHOULD_DEPLOYoutput is fragile — if any earlier step fails, it will always produce this secondary error. Worth considering replacing it with a default fallback.