Workflow dispatch API returns 200 instead of 204 #182272
Replies: 4 comments 1 reply
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
|
Reading this to the hum of the world frantically rushing to update all GitHub dispatches API calls in their scripts... |
Beta Was this translation helpful? Give feedback.
-
|
Also, their SDKs are expecting |
Beta Was this translation helpful? Give feedback.
-
|
The GitHub REST API is versioned specifically to avoid cases like this. Based on that doc I would expect a new API version for the status code and response body change |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Bug
Body
https://docs.github.com/en/rest/actions/workflows?apiVersion=2022-11-28#create-a-workflow-dispatch-event
POST /repos/{owner}/{repo}/actions/workflows/{workflow_id}/dispatchesis documented to return status code 204, and it did until few hours ago.At some point, the API was changed to return 200 with JSON body containing
workflow_run_id,run_url,html_url, which caused automated workflows expecting 204 to fail.Possibly related: https://github.com/orgs/community/discussions/9752
Beta Was this translation helpful? Give feedback.
All reactions