When spec generation fails for some reason (independent of spec-prod), the action correctly reports the error but then still attempts to run subsequent job steps, which trigger a bunch of additional error reports that can make readers think that spec-prod is the root cause of the issue at hand.
Typical example of reported "template is not valid" error:
Error: w3c/spec-prod/v2/action.yml (Line: 113, Col: 24):
Error: The template is not valid. w3c/spec-prod/v2/action.yml (Line: 113, Col: 24): Error reading JToken from JsonReader. Path '', line 0, position 0.
When spec generation fails for some reason (independent of spec-prod), the action correctly reports the error but then still attempts to run subsequent job steps, which trigger a bunch of additional error reports that can make readers think that spec-prod is the root cause of the issue at hand.
Typical example of reported "template is not valid" error:
Examples of occurrences:
This is all the more confusing that these error lines appear in red in the job log on GitHub, whereas the initial error may not.