author_name:atmos

We're going to extend the Deployment APIpreviewtimeframe based on feedback from end-users. We're still fleshing out whatthe[Deployments API][january-deployment-api-post]will look like when it graduatesfrompreview mode and becomes a fully supported part of the GitHub API. We've already[updated the payload][payload-update] that integrations can use to customize deployments.We're alsointegrating with the[Combined Status API][combined-statuses] to help ensure that only verified code gets deployed, even if you have multiple systems verifying different aspects of your software.

Thepreviewperiod forthenew[Deployments API][2014-01-deployments-api-post]continues to yield valuable feedbackfromdevelopers. In early March, we used that feedback to[improve the payload format][payload-update] that integrations can use to customize deployments.A few weeks later, we beganintegrating with the new[Combined Status API][combined-statuses] to help ensure that only verified code gets deployed, even if you have multiple systems verifying different aspects of your software.

We've decided to extend the Deployments API preview for another 30-60 days in ordertomake sure that everything works well with the changes we've been introducing. As always, if you have any questions or feedback, please[get in touch][contact].

To give developers time to explore these recent refinementstothe Deployments API, we're extending the preview period for a little while longer. As always, if you have any questions or feedback, please[get in touch][contact].

[january-deployment-api-post]:/changes/2014-01-09-preview-the-new-deployments-api/

[2014-01-deployments-api-post]:/changes/2014-01-09-preview-the-new-deployments-api/

[payload-update]:/changes/2014-03-03-deployments-api-updates/

[combined-statuses]:/changes/2014-03-27-combined-status-api/

[contact]:https://github.com/contact?form[subject]=Deployments+API