<?xml version="1.0" encoding="UTF-8"?>

<feed xmlns="http://www.w3.org/2005/Atom">

<id>http://developer.github.com/</id>

<title>GitHub API Changes</title>

<updated>2015-03-09T00:00:00Z</updated>

<link rel="alternate" href="http://developer.github.com/" />

<link rel="self" href="http://developer.github.com/changes.atom" />

<author>

<name>technoweenie</name>

<uri>https://github.com/technoweenie</uri>

</author>

<entry>

<id>tag:developer.github.com,2015-03-09:/changes/2015-03-09-licenses-api/</id>

<title type="html">Licenses API</title>

<published>2015-03-09T00:00:00Z</published>

<updated>2015-03-09T00:00:00Z</updated>

<author>

<name>benbalter</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2015-03-09-licenses-api/" />

<content type="html">&lt;p&gt;We’re introducing a new &lt;a href="/v3/licenses"&gt;license API&lt;/a&gt; preview to support &lt;a href="https://github.com/blog/1964-license-usage-on-github-com"&gt;open source license usage on GitHub.com&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;To access the API during the preview period, you must provide a custom &lt;a href="/v3/media"&gt;media type&lt;/a&gt; in the &lt;code&gt;Accept&lt;/code&gt; header:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;application/vnd.github.drax-preview+json

&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;This will then expose two new API endpoints. You can get a list of all known licenses:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;GET /licenses

&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;Or get information about a particular license:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;GET /licenses/mit

&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;When the preview media type is passed, the repository api will also return information about a repository’s license file when you get an individual repository:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;GET /repos/github/hubot

&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;For more information, see the &lt;a href="/v3/licenses/"&gt;licenses API documentation&lt;/a&gt;, and if you have any questions or feedback, please &lt;a href="https://github.com/contact?form%5Bsubject%5D=Licenses+API"&gt;let us know&lt;/a&gt;.&lt;/p&gt;

</content>

</entry>

<entry>

<id>tag:developer.github.com,2015-02-24:/changes/2015-02-24-more-time-to-prepare-for-the-breaking-changes-to-organization-permissions/</id>

<title type="html">More time to prepare for the breaking changes to organization permissions</title>

<published>2015-02-24T00:00:00Z</published>

<updated>2015-02-24T00:00:00Z</updated>

<author>

<name>jakeboxer</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2015-02-24-more-time-to-prepare-for-the-breaking-changes-to-organization-permissions/" />

<content type="html">&lt;p&gt;After listening to your feedback on the upcoming &lt;a href="/changes/2014-12-08-organization-permissions-api-preview/"&gt;breaking changes to organization permissions&lt;/a&gt;, we’re giving developers more time to update their applications. We’ll announce an updated timeline for these changes in the coming weeks.&lt;/p&gt;

&lt;p&gt;In the meantime, if your application relies on any of the affected functionality described in our &lt;a href="/changes/2014-12-08-organization-permissions-api-preview/"&gt;previous blog post&lt;/a&gt;, please &lt;strong&gt;update your code&lt;/strong&gt; to account for these changes. If you have any questions or feedback, please &lt;a href="https://github.com/contact?form%5Bsubject%5D=Organization+Permissions+API"&gt;get in touch with us&lt;/a&gt;!&lt;/p&gt;

</content>

</entry>

<entry>

<id>tag:developer.github.com,2015-02-19:/changes/2015-02-20-migration-period-removing-authorizations-token/</id>

<title type="html">Breaking changes to Authorizations API responses on April 20</title>

<published>2015-02-19T00:00:00Z</published>

<updated>2015-02-19T00:00:00Z</updated>

<author>

<name>ptoomey3</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2015-02-20-migration-period-removing-authorizations-token/" />

<content type="html">&lt;p&gt;A couple weeks ago we &lt;a href="/changes/2015-02-03-removing-authorizations-token-update/"&gt;extended the preview period&lt;/a&gt; of several API changes related to managing OAuth application authorizations. Today, we’re finalizing these changes. This new functionality is now stable and suitable for production use. If your application relies on any of the affected functionality (described below), be sure to &lt;strong&gt;update your code before April 20&lt;/strong&gt; to account for these changes.&lt;/p&gt;

&lt;h3 id="breaking-changes-coming-on-april-20"&gt;Breaking changes coming on April 20&lt;/h3&gt;

&lt;p&gt;If your application uses any of the following APIs, then you may be affected by this change:&lt;/p&gt;

&lt;ul&gt;

&lt;li&gt;The &lt;a href="/v3/oauth_authorizations/#list-your-authorizations"&gt;List your authorizations&lt;/a&gt; API&lt;/li&gt;

&lt;li&gt;The &lt;a href="/v3/oauth_authorizations/#get-a-single-authorization"&gt;Get a single authorization&lt;/a&gt; API&lt;/li&gt;

&lt;li&gt;The &lt;a href="/v3/oauth_authorizations/#get-or-create-an-authorization-for-a-specific-app"&gt;Get-or-create an authorization for a specific app&lt;/a&gt; API (&lt;code&gt;token&lt;/code&gt; is still returned for “create”)&lt;/li&gt;

&lt;li&gt;The &lt;a href="/v3/oauth_authorizations/#get-or-create-an-authorization-for-a-specific-app-and-fingerprint"&gt;Get-or-create an authorization for a specific app and fingerprint&lt;/a&gt; API (&lt;code&gt;token&lt;/code&gt; is still returned for “create”)&lt;/li&gt;

&lt;li&gt;The &lt;a href="/v3/oauth_authorizations/#update-an-existing-authorization"&gt;Update an existing authorization&lt;/a&gt; API&lt;/li&gt;

&lt;/ul&gt;

&lt;p&gt;If your application uses these APIs, we urge you to update your application as soon as possible. (Read &lt;a href="/changes/2014-12-08-removing-authorizations-token/"&gt;the December announcement&lt;/a&gt; for more details on the changes.)&lt;/p&gt;

&lt;p&gt;Starting today, we’re offering a migration period allowing applications to opt in to these changes (as described below). On April 20, these changes will become official parts of the GitHub API v3. At that time, these changes will apply to all API consumers.&lt;/p&gt;

&lt;h3 id="migration-period"&gt;Migration period&lt;/h3&gt;

&lt;p&gt;During the migration period, you can opt-in to these changes using the following custom media type in the &lt;code&gt;Accept&lt;/code&gt; header:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;application/vnd.github.mirage-preview+json

&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;We want to make these updates as smooth as possible for everyone, and we hope that the migration period gives you flexibility to adopt these changes on your own schedule. If you have any questions or feedback, please &lt;a href="https://github.com/contact?form%5Bsubject%5D=Removing+authorizations+token"&gt;get in touch with us&lt;/a&gt;!&lt;/p&gt;

</content>

</entry>

<entry>

<id>tag:developer.github.com,2015-02-18:/changes/2015-02-18-new-releases-api-methods/</id>

<title type="html">New Releases API methods</title>

<published>2015-02-18T00:00:00Z</published>

<updated>2015-02-18T00:00:00Z</updated>

<author>

<name>pengwynn</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2015-02-18-new-releases-api-methods/" />

<content type="html">&lt;p&gt;We’ve added two new methods to the &lt;a href="/v3/repos/releases/"&gt;Releases API&lt;/a&gt;. You can now get the &lt;a href="/v3/repos/releases/#get-the-latest-release"&gt;latest published release&lt;/a&gt; for a repository.&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;GET /repos/:owner/:repo/releases/latest

&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;You can also get a &lt;a href="/v3/repos/releases/#get-a-release-by-tag-name"&gt;release by tag name&lt;/a&gt;.&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;GET /repos/:owner/:repo/releases/tags/:tag

&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;If you have any questions or feedback, please &lt;a href="https://github.com/contact?form%5Bsubject%5D=New+Releases+API+methods"&gt;get in touch&lt;/a&gt;.&lt;/p&gt;

</content>

</entry>

<entry>

<id>tag:developer.github.com,2015-02-03:/changes/2015-02-03-removing-authorizations-token-update/</id>

<title type="html">Removing token attribute from Authorizations API responses (Update)</title>

<published>2015-02-03T00:00:00Z</published>

<updated>2015-02-03T00:00:00Z</updated>

<author>

<name>ptoomey3</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2015-02-03-removing-authorizations-token-update/" />

<content type="html">&lt;p&gt;In December, we &lt;a href="/changes/2014-12-08-removing-authorizations-token/"&gt;released a preview&lt;/a&gt; of several API changes related to managing OAuth application authorizations. As part of those changes we introduced several new response attributes (&lt;code&gt;token_last_eight&lt;/code&gt;, &lt;code&gt;hashed_token&lt;/code&gt;, and &lt;code&gt;fingerprint&lt;/code&gt;) to the Authorizations API. We have decided to modify &lt;code&gt;hashed_token&lt;/code&gt; to return the SHA-256 hex digest of the associated token instead of Base64. Given that Base64 has several common variants (original, URL safe, etc) we decided that returning the value as hex is less ambiguous and will be more useful for developers.&lt;/p&gt;

&lt;h3 id="extended-preview-period"&gt;Extended preview period&lt;/h3&gt;

&lt;p&gt;Because of the change to &lt;code&gt;hashed_token&lt;/code&gt;, we are extending the preview period by two weeks. If no additional changes are made during this extended preview period we will announce the end of the preview and beginning of the eight week migration period on February 17. The migration period will allow applications to opt in to these changes before they become an official part of the GitHub API v3.&lt;/p&gt;

&lt;p&gt;If you have any questions or feedback, please &lt;a href="https://github.com/contact?form%5Bsubject%5D=Removing+authorizations+token"&gt;drop us a line&lt;/a&gt;!&lt;/p&gt;

</content>

</entry>

<entry>

<id>tag:developer.github.com,2015-01-19:/changes/2015-01-19-an-integrators-guide-to-organization-application-policies/</id>

<title type="html">An integrator's guide to organization application policies</title>

<published>2015-01-19T00:00:00Z</published>

<updated>2015-01-19T00:00:00Z</updated>

<author>

<name>pengwynn</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2015-01-19-an-integrators-guide-to-organization-application-policies/" />

<content type="html">&lt;p&gt;As we &lt;a href="https://github.com/blog/1941-organization-approved-applications"&gt;announced over on the GitHub blog&lt;/a&gt;, organization admins can now

control how third-party applications access their organization data. Allowing

admins to approve or deny applications will ultimately result in deeper trust

and increase overall adoption of integrations within organizations on GitHub.&lt;/p&gt;

&lt;p&gt;As an integrator, here’s what you need to know about organization application

policies and how this feature could impact your application.&lt;/p&gt;

&lt;h3 id="guiding-principles"&gt;Guiding principles&lt;/h3&gt;

&lt;p&gt;We’ve tried to strike the right balance between organization privacy and the

user experience for integrators and end users. Organizations should be able to

prevent applications they do not trust from accessing their organization data

without creating a multitude of new edge cases for integrators.&lt;/p&gt;

&lt;p&gt;With that goal in mind, the feature works like this: &lt;strong&gt;if an organization’s

application policy prevents an application from accessing its resources, the

API behaves as if the authenticating user is not a member of the

organization&lt;/strong&gt;. Specifically, this means an application authenticating on

behalf of a user using OAuth will have:&lt;/p&gt;

&lt;ul&gt;

&lt;li&gt;

&lt;strong&gt;Read-only access to public resources.&lt;/strong&gt; Organization-owned public

repositories, issues, and other resources will be visible via the API and

show up in resource listings, but mutating methods (&lt;code&gt;POST&lt;/code&gt;, &lt;code&gt;PATCH&lt;/code&gt;, &lt;code&gt;PUT&lt;/code&gt;,

and &lt;code&gt;DELETE&lt;/code&gt;) will return status &lt;code&gt;403&lt;/code&gt;.&lt;/li&gt;

&lt;li&gt;

&lt;strong&gt;No access to private resources.&lt;/strong&gt; Organization-owned private repositories,

issues, and other resources will not be visible via the API and will not

show up in resource &lt;a href="/v3/issues/#list-issues"&gt;listings&lt;/a&gt; that co-mingle public and private

resources. Hooks for these private repositories are muted and will not be

delivered as long as the application is restricted by the organization.&lt;/li&gt;

&lt;/ul&gt;

&lt;p&gt;Since applications should already handle the scenario where a user loses access

to organization resources, this reduces the work integrators need to do.&lt;/p&gt;

&lt;h3 id="checking-organization-access"&gt;Checking organization access&lt;/h3&gt;

&lt;p&gt;As organization admins adopt application whitelists and restrict third-party

application access to organization resources, your application may lose access

to those resources. If an organization member is not aware of the new access

policy, they may wonder why their private repositories or other resources no

longer work or show up in your application.&lt;/p&gt;

&lt;p&gt;There are a couple ways to help troubleshoot access for your end users.&lt;/p&gt;

&lt;ul&gt;

&lt;li&gt;

&lt;p&gt;&lt;strong&gt;Via the GitHub UI.&lt;/strong&gt; The simplest way to help end users understand how

organization access policies affect their access to your application is to

provide a link to &lt;a href="https://help.github.com/articles/requesting-organization-approval-for-your-authorized-applications/"&gt;their authorization details&lt;/a&gt;

under their GitHub account settings as &lt;a href="/v3/oauth/#directing-users-to-review-their-access-for-an-application"&gt;described in the OAuth

documentation&lt;/a&gt;.&lt;/p&gt;

&lt;/li&gt;

&lt;li&gt;

&lt;p&gt;&lt;strong&gt;Via the API.&lt;/strong&gt; For an even better user experience, &lt;a href="/guides/discovering-resources-for-a-user/"&gt;use the

API&lt;/a&gt; to list which user organizations your application

can access, and provide users with the link mentioned above to request

access from their organization admins.&lt;/p&gt;

&lt;/li&gt;

&lt;/ul&gt;

&lt;h3 id="listing-accessible-organization-resources"&gt;Listing accessible organization resources&lt;/h3&gt;

&lt;p&gt;In addition to checking access to a user’s organizations, you’ll want to ensure

you’re discovering their accessible resources in the most efficient way. Recent

changes to the &lt;a href="/v3/repos/#list-your-repositories"&gt;Respositories API&lt;/a&gt; might reduce the API calls

your application needs to make to find a user’s repositories across all of

their organization mememberships.&lt;/p&gt;

&lt;h3 id="ensuring-uninterrupted-ssh-access"&gt;Ensuring uninterrupted SSH access&lt;/h3&gt;

&lt;p&gt;Since applications should already handle the scenario where a user loses access

to organization resources (e.g., when a user leaves an organization), this

reduces the work integrators need to do. Keys created by OAuth applications (or

those created before GitHub started tracking that information) will not have

access to repositories owned by organizations that restrict third-party

applications. If your application uses keys &lt;strong&gt;created before February 24,

2014&lt;/strong&gt;, you &lt;a href="/changes/2014-12-12-replace-older-ssh-keys-created-by-your-application/"&gt;should replace those older keys&lt;/a&gt; to ensure things keep

running smoothly for your application.&lt;/p&gt;

&lt;h3 id="were-here-to-help"&gt;We’re here to help&lt;/h3&gt;

&lt;p&gt;This is a big feature, and we’re sure it will impact many of our integrators as

organizations adopt third-party application restrictions. We also think it

provides a huge net benefit for integrators as organizations choose to use

OAuth integrations with more confidence.&lt;/p&gt;

&lt;p&gt;If you have any questions or feedback, please &lt;a href="https://github.com/contact?form%5Bsubject%5D=Organization+Access+Policies+help+for+integrators"&gt;get in touch&lt;/a&gt;.&lt;/p&gt;

</content>

</entry>

<entry>

<id>tag:developer.github.com,2015-01-08:/changes/2015-01-08-discovering-resources-for-a-user/</id>

<title type="html">New guide: Discovering resources for a user</title>

<published>2015-01-08T00:00:00Z</published>

<updated>2015-01-08T00:00:00Z</updated>

<author>

<name>jasonrudolph</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2015-01-08-discovering-resources-for-a-user/" />

<content type="html">&lt;p&gt;Is your application taking advantage of the recommended workflow for discovering a user’s repositories and organizations? With the &lt;a href="/changes/2014-12-08-organization-permissions-api-preview/"&gt;recent improvements to the API&lt;/a&gt;, the process is simpler than ever. In our newest guide, we show you how to &lt;a href="/guides/discovering-resources-for-a-user/"&gt;reliably identify the resources that your app can access for a given user&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;If you have any questions or feedback, we’d love to &lt;a href="https://github.com/contact?form%5Bsubject%5D=API+v3:+Discovering+resources+for+a+user"&gt;hear from you&lt;/a&gt;.&lt;/p&gt;

</content>

</entry>

<entry>

<id>tag:developer.github.com,2015-01-07:/changes/2015-01-07-prepare-for-organization-permissions-changes/</id>

<title type="html">Prepare for upcoming organization permissions changes</title>

<published>2015-01-07T00:00:00Z</published>

<updated>2015-01-07T00:00:00Z</updated>

<author>

<name>jakeboxer</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2015-01-07-prepare-for-organization-permissions-changes/" />

<content type="html">&lt;p&gt;Last month, we &lt;a href="/changes/2014-12-08-organization-permissions-api-preview/"&gt;released a preview&lt;/a&gt; of several API changes related to managing organization members and repositories. Today, we’re finalizing these changes. This new functionality is now stable and suitable for production use. If your application relies on any of the affected functionality (described below), be sure to &lt;strong&gt;update your code before February 24&lt;/strong&gt; to account for these changes.&lt;/p&gt;

&lt;h3 id="breaking-changes-coming-on-february-24"&gt;Breaking changes coming on February 24&lt;/h3&gt;

&lt;p&gt;If your application uses any of the following APIs, then you are affected by this change:&lt;/p&gt;

&lt;ul&gt;

&lt;li&gt;APIs for managing your organization’s admins through the Owners team&lt;/li&gt;

&lt;li&gt;The &lt;a href="/v3/repos/#list-your-repositories"&gt;List your repositories&lt;/a&gt; API&lt;/li&gt;

&lt;li&gt;The &lt;a href="/v3/orgs/#list-your-organizations"&gt;List your organizations&lt;/a&gt; API&lt;/li&gt;

&lt;li&gt;The &lt;a href="/v3/orgs/#list-user-organizations"&gt;List user organizations&lt;/a&gt; API&lt;/li&gt;

&lt;/ul&gt;

&lt;p&gt;If your application uses these APIs, we urge you to update your application as soon as possible. (Read &lt;a href="/changes/2014-12-08-organization-permissions-api-preview/"&gt;last month’s announcement&lt;/a&gt; for more details on the changes.)&lt;/p&gt;

&lt;p&gt;Starting today, we’re offering a migration period allowing applications to opt in to these changes (as described below). On February 24, these changes will become official parts of the GitHub API v3. At that time, these changes will apply to all API consumers.&lt;/p&gt;

&lt;h3 id="migration-period"&gt;Migration period&lt;/h3&gt;

&lt;p&gt;During the migration period, you can opt-in to these changes using the following custom media type in the &lt;code&gt;Accept&lt;/code&gt; header:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;application/vnd.github.moondragon+json

&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;We want to make these updates as smooth as possible for everyone, and we hope that the migration period gives you flexibility to adopt these changes on your own schedule. If you have any questions or feedback, please &lt;a href="https://github.com/contact?form%5Bsubject%5D=Organization+Permissions+API"&gt;get in touch with us&lt;/a&gt;!&lt;/p&gt;

</content>

</entry>

<entry>

<id>tag:developer.github.com,2014-12-12:/changes/2014-12-12-replace-older-ssh-keys-created-by-your-application/</id>

<title type="html">Replace older SSH keys created by your application</title>

<published>2014-12-12T00:00:00Z</published>

<updated>2014-12-12T00:00:00Z</updated>

<author>

<name>jasonrudolph</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2014-12-12-replace-older-ssh-keys-created-by-your-application/" />

<content type="html">&lt;p&gt;Back in February, we &lt;a href="/changes/2014-02-24-finer-grained-scopes-for-ssh-keys/#keys-are-now-immutable"&gt;improved the security audit trail for SSH keys&lt;/a&gt;. Soon, organizations will be able to block access for SSH keys that were created prior to those improvements. If your application relies on &lt;a href="/guides/managing-deploy-keys/#deploy-keys"&gt;deploy keys&lt;/a&gt; or &lt;a href="/v3/users/keys/"&gt;user keys&lt;/a&gt; for repository access, we recommend replacing any keys created before February 24, 2014.&lt;/p&gt;

&lt;p&gt;To ensure that your application is not affected by organizations blocking access to these keys, &lt;strong&gt;you should replace the affected keys by January 15, 2015&lt;/strong&gt;.&lt;/p&gt;

&lt;h2 id="how-should-you-replace-these-keys"&gt;How should you replace these keys?&lt;/h2&gt;

&lt;p&gt;We recommend the following steps for identifying and replacing the affected keys.&lt;/p&gt;

&lt;h3 id="identify-the-affected-keys"&gt;1. Identify the affected keys&lt;/h3&gt;

&lt;p&gt;You only need to replace keys that your application created prior to February 24, 2014. If you don’t know when your app created a given key, you can get the creation timestamp from the API. The &lt;code&gt;created_at&lt;/code&gt; property is available for &lt;a href="/v3/repos/keys/"&gt;deploy keys&lt;/a&gt; and for &lt;a href="/v3/users/keys/#list-your-public-keys"&gt;user keys&lt;/a&gt;.&lt;/p&gt;

&lt;h3 id="inform-the-affected-users"&gt;2. Inform the affected users&lt;/h3&gt;

&lt;p&gt;Once you know which keys you need to replace, we recommend that you inform the affected users.&lt;/p&gt;

&lt;p&gt;For security, GitHub automatically sends an email to a user whenever a new SSH key is added to their account. Similarly, when a new deploy key is added to a repository, GitHub sends an email to the repository’s administrators. When you replace your application’s old keys with new ones, GitHub will email the affected users. To avoid surprising those users, you should alert them that you’ll be replacing your keys. You may want to include a link to this post in your message.&lt;/p&gt;

&lt;h3 id="add-a-new-key"&gt;3. Add a new key&lt;/h3&gt;

&lt;p&gt;Use the API to add the new &lt;a href="/v3/repos/keys/#create"&gt;deploy key&lt;/a&gt; or &lt;a href="/v3/users/keys/#create-a-public-key"&gt;user key&lt;/a&gt;.&lt;/p&gt;

&lt;h3 id="delete-the-old-key"&gt;4. Delete the old key&lt;/h3&gt;

&lt;p&gt;Once your application is using the new key, use the API to delete the old one. There’s an &lt;a href="/v3/repos/keys/#delete"&gt;API for deleting deploy keys&lt;/a&gt; and an &lt;a href="/v3/users/keys/#delete-a-public-key"&gt;API for deleting user keys&lt;/a&gt;.&lt;/p&gt;

&lt;h2 id="were-here-to-help"&gt;We’re here to help&lt;/h2&gt;

&lt;p&gt;As always, if you have any questions or concerns, please &lt;a href="https://github.com/contact?form%5Bsubject%5D=Replace+SSH+keys+created+by+application"&gt;get in touch&lt;/a&gt;.&lt;/p&gt;

</content>

</entry>

<entry>

<id>tag:developer.github.com,2014-12-09:/changes/2014-12-09-new-attributes-for-stars-api/</id>

<title type="html">New Attributes for Starring API</title>

<published>2014-12-09T00:00:00Z</published>

<updated>2014-12-09T00:00:00Z</updated>

<author>

<name>arfon</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2014-12-09-new-attributes-for-stars-api/" />

<content type="html">&lt;p&gt;You can now see when a user starred a repository. To receive the new response format containing the &lt;code&gt;starred_at&lt;/code&gt; field, request the new media type:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;curl -H "Accept: application/vnd.github.v3.star+json" https://api.github.com/users/andrew/starred

&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;Note the starred repository is now available in the repo field.&lt;/p&gt;

&lt;h3 id="feedback"&gt;Feedback&lt;/h3&gt;

&lt;p&gt;If you have any questions or feedback about these changes, please &lt;a href="https://github.com/contact?form%5Bsubject%5D=New+Attributes+for+Starring+API"&gt;drop us a line&lt;/a&gt;.&lt;/p&gt;

</content>

</entry>

<entry>

<id>tag:developer.github.com,2014-12-08:/changes/2014-12-08-organization-permissions-api-preview/</id>

<title type="html">Preview the upcoming organization permission changes</title>

<published>2014-12-08T00:00:00Z</published>

<updated>2014-12-08T00:00:00Z</updated>

<author>

<name>jakeboxer</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2014-12-08-organization-permissions-api-preview/" />

<content type="html">&lt;p&gt;&lt;strong&gt;UPDATE (2014-12-12):&lt;/strong&gt; The &lt;a href="/v3/orgs/#list-your-organizations"&gt;List your organizations&lt;/a&gt; API is now included in this preview as well.&lt;/p&gt;

&lt;p&gt;We have some upcoming changes that will affect the way organization members and repositories are managed. The most important changes are:&lt;/p&gt;

&lt;ul&gt;

&lt;li&gt;The Owners team will no longer be special.&lt;/li&gt;

&lt;li&gt;The &lt;a href="/v3/repos/#list-your-repositories"&gt;List your repositories&lt;/a&gt; API will include organization-owned repositories.&lt;/li&gt;

&lt;li&gt;The &lt;a href="/v3/orgs/#list-user-organizations"&gt;List user organizations&lt;/a&gt; API will only include public organization memberships.&lt;/li&gt;

&lt;li&gt;The &lt;a href="/v3/orgs/#list-your-organizations"&gt;List your organizations&lt;/a&gt; API will require &lt;code&gt;user&lt;/code&gt; scope or &lt;code&gt;read:org&lt;/code&gt; scope.&lt;/li&gt;

&lt;/ul&gt;

&lt;h2 id="whats-happening-to-the-owners-team"&gt;What’s happening to the Owners team?&lt;/h2&gt;

&lt;p&gt;Currently, members of your Owners team are administrators of your organization. Soon, your Owners team will become a totally normal team. Adding and removing Owners team members won’t change their administrator status anymore. Instead, you’ll be able to directly grant admin permissions to your organization’s members without adding them to any special teams.&lt;/p&gt;

&lt;p&gt;We won’t delete your Owners team, but you’ll be able to delete or rename it yourself if you want. Organizations created after the change won’t have an Owners team.&lt;/p&gt;

&lt;h3 id="what-should-you-do"&gt;What should you do?&lt;/h3&gt;

&lt;p&gt;In preparation for this change to the Owners team, we’re releasing a few new APIs. You’ll be able to use these APIs to manage organization admins without relying on the Owners team.&lt;/p&gt;

&lt;h4 id="adding-an-organization-admin"&gt;Adding an organization admin&lt;/h4&gt;

&lt;p&gt;To add a new organization admin, use the new &lt;a href="/v3/orgs/members/#add-or-update-organization-membership"&gt;Add or update organization membership&lt;/a&gt; endpoint, specifying a role of &lt;code&gt;"admin"&lt;/code&gt; in the request body. This replaces adding or inviting people to the Owners team.&lt;/p&gt;

&lt;h4 id="removing-an-organization-admin"&gt;Removing an organization admin&lt;/h4&gt;

&lt;p&gt;To remove someone from the organization role but keep them as a member of their teams, use the new &lt;a href="/v3/orgs/members/#add-or-update-organization-membership"&gt;Add or update organization membership&lt;/a&gt; endpoint, specifying a role of &lt;code&gt;"member"&lt;/code&gt; in the request body. This replaces removing people from the Owners team.&lt;/p&gt;

&lt;h4 id="listing-organization-admins"&gt;Listing organization admins&lt;/h4&gt;

&lt;p&gt;To get a list of all your organization’s admins, use the &lt;a href="/v3/orgs/members/#members-list"&gt;Organization members list&lt;/a&gt; endpoint, specifying a role of &lt;code&gt;"admin"&lt;/code&gt; in the query string. This replaces listing the members of the Owners team.&lt;/p&gt;

&lt;h4 id="checking-if-someone-is-an-organization-admin"&gt;Checking if someone is an organization admin&lt;/h4&gt;

&lt;p&gt;To check if a given user is an organization admin, use the new &lt;a href="/v3/orgs/members/#get-organization-membership"&gt;Get organization membership&lt;/a&gt; endpoint. If the returned &lt;code&gt;"role"&lt;/code&gt; attribute is set to &lt;code&gt;"admin"&lt;/code&gt; and the returned &lt;code&gt;"state"&lt;/code&gt; attribute is set to &lt;code&gt;"active"&lt;/code&gt;, the user is an organization admin. This replaces checking if a user is on the Owners team.&lt;/p&gt;

&lt;h2 id="whats-happening-to-the-list-your-repositories-api"&gt;What’s happening to the “List your repositories” API?&lt;/h2&gt;

&lt;p&gt;Currently, the &lt;a href="/v3/repos/#list-your-repositories"&gt;List your repositories&lt;/a&gt; API only returns repositories that are owned by users, not by organizations. If you want a list of &lt;em&gt;all&lt;/em&gt; the repositories that the authenticated user has access to, you need to use multiple API methods.&lt;/p&gt;

&lt;p&gt;Soon, this API will include all repositories that the authenticated user has access to (whether they’re owned by a user or by an organization).&lt;/p&gt;

&lt;h3 id="what-should-you-do-1"&gt;What should you do?&lt;/h3&gt;

&lt;p&gt;Many apps use the &lt;a href="/v3/repos/#list-your-repositories"&gt;List your repositories&lt;/a&gt; API in conjunction with the &lt;a href="/v3/orgs/#list-your-organizations"&gt;List your organizations&lt;/a&gt; and &lt;a href="/v3/repos/#list-organization-repositories"&gt;List organization repositories&lt;/a&gt; APIs to build up a list of all the repositories the authenticated user has access to. If your app is doing this, you’ll be able to get rid of all the organization-related API calls and just use the &lt;a href="/v3/repos/#list-your-repositories"&gt;List your repositories&lt;/a&gt; API.&lt;/p&gt;

&lt;p&gt;If your app uses the &lt;a href="/v3/repos/#list-your-repositories"&gt;List your repositories&lt;/a&gt; API for another purpose, you’ll need to update your app to handle the new organization-owned repositories we’ll be returning.&lt;/p&gt;

&lt;h2 id="whats-happening-to-the-list-user-organizations-api"&gt;What’s happening to the “List user organizations” API?&lt;/h2&gt;

&lt;p&gt;The &lt;a href="/v3/orgs/#list-user-organizations"&gt;List user organizations&lt;/a&gt; API is intended provide &lt;a href="https://help.github.com/articles/publicizing-or-concealing-organization-membership"&gt;public organization memberships&lt;/a&gt; for any user. When you use this API to fetch &lt;em&gt;your own&lt;/em&gt; organizations, this API currently returns your public and private organization memberships.&lt;/p&gt;

&lt;p&gt;Soon, this API will only return public organization memberships.&lt;/p&gt;

&lt;h3 id="what-should-you-do-2"&gt;What should you do?&lt;/h3&gt;

&lt;p&gt;If your app uses the &lt;a href="/v3/orgs/#list-user-organizations"&gt;List user organizations&lt;/a&gt; API to fetch all of the organization memberships (public and private) for the authenticated user, you’ll need to update your app to use the &lt;a href="/v3/orgs/#list-your-organizations"&gt;List your organizations&lt;/a&gt; API instead. The &lt;a href="/v3/orgs/#list-your-organizations"&gt;List your organizations&lt;/a&gt; API returns all organizations (public and private) that your app is authorized to access.&lt;/p&gt;

&lt;h2 id="whats-happening-to-the-list-your-organizations-api"&gt;What’s happening to the “List your organizations” API?&lt;/h2&gt;

&lt;p&gt;OAuth requests will soon require minimum &lt;a href="/v3/oauth/#scopes"&gt;scopes&lt;/a&gt; in order to access the &lt;a href="/v3/orgs/#list-your-organizations"&gt;List your organizations&lt;/a&gt; API.&lt;/p&gt;

&lt;p&gt;Currently, the API response always includes your &lt;a href="https://help.github.com/articles/publicizing-or-concealing-organization-membership"&gt;public organization memberships&lt;/a&gt;, regardless of the OAuth scopes associated with your request. If you have &lt;code&gt;user&lt;/code&gt;, &lt;code&gt;read:org&lt;/code&gt;, &lt;code&gt;write:org&lt;/code&gt;, or &lt;code&gt;admin:org&lt;/code&gt; scope, the response also includes your private organization memberships.&lt;/p&gt;

&lt;p&gt;Soon, this API will only return organizations that your authorization allows you to operate on in some way (e.g., you can list teams with &lt;code&gt;read:org&lt;/code&gt; scope, you can publicize your organization membership with &lt;code&gt;user&lt;/code&gt; scope, etc.). Therefore, this API will require at least &lt;code&gt;user&lt;/code&gt; or &lt;code&gt;read:org&lt;/code&gt; scope. (&lt;code&gt;write:org&lt;/code&gt; and &lt;code&gt;admin:org&lt;/code&gt; scope implicitly include &lt;code&gt;read:org&lt;/code&gt; scope.) OAuth requests with insufficient scope will receive a &lt;code&gt;403 Forbidden&lt;/code&gt; response.&lt;/p&gt;

&lt;h3 id="what-should-you-do-3"&gt;What should you do?&lt;/h3&gt;

&lt;p&gt;If you &lt;a href="/v3/auth/#via-username-and-password"&gt;authenticate via username and password&lt;/a&gt;, you are not affected by this change.&lt;/p&gt;

&lt;p&gt;If your app only needs to fetch the user’s public organization memberships, you should use the &lt;a href="/v3/orgs/#list-user-organizations"&gt;List user organizations&lt;/a&gt; API instead. Since that API only returns public information, it does not require any scopes.&lt;/p&gt;

&lt;h2 id="preview-period"&gt;Preview period&lt;/h2&gt;

&lt;p&gt;Starting &lt;strong&gt;today&lt;/strong&gt;, these new APIs are available for developers to preview. We expect the preview period to last for four weeks. (Stay tuned to the developer blog for updates.) At the end of the preview period, these additions will become official components of the GitHub API.&lt;/p&gt;

&lt;p&gt;While these additions are in their preview period, you’ll need to provide the following custom media type in the &lt;code&gt;Accept&lt;/code&gt; header:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;application/vnd.github.moondragon-preview+json

&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;During the preview period, we may change aspects of these endpoints. If we do, we will announce the changes on the developer blog, but we will not provide any advance notice.&lt;/p&gt;

&lt;h2 id="migration-period"&gt;Migration period&lt;/h2&gt;

&lt;p&gt;At the end of the preview period, we will announce the start of a migration period. At that time, developers should update their applications to use the new APIs for managing organization admins. During this period, you will still be able to use the Owners team to manage your organization’s admins, so that you have time to update your applications to use the new APIs without breakage. We expect the migration period to last for four weeks.&lt;/p&gt;

&lt;p&gt;At the end of the migration period, the Owners team will no longer be special, and you’ll no longer be able to rely on it for managing organization admins.&lt;/p&gt;

&lt;p&gt;If you have any questions or feedback, please &lt;a href="https://github.com/contact?form%5Bsubject%5D=Organization+Admin+Pre-release+Preview"&gt;get in touch with us&lt;/a&gt;!&lt;/p&gt;

</content>

</entry>

<entry>

<id>tag:developer.github.com,2014-12-08:/changes/2014-12-08-removing-authorizations-token/</id>

<title type="html">Removing token attribute from Authorizations API responses</title>

<published>2014-12-08T00:00:00Z</published>

<updated>2014-12-08T00:00:00Z</updated>

<author>

<name>ptoomey3</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2014-12-08-removing-authorizations-token/" />

<content type="html">&lt;p&gt;Since OAuth access tokens function like passwords, they should be treated with

care. Today we are making it easier to more securely work with authorizations

via the Authorizations API. We are deprecating the use use of the &lt;code&gt;token&lt;/code&gt;

attribute in the majority of the &lt;a href="/v3/oauth_authorizations/"&gt;Authorizations API&lt;/a&gt;

responses. For the &lt;a href="/v3/oauth_authorizations/#deprecation-notice"&gt;affected APIs&lt;/a&gt;, the

&lt;code&gt;token&lt;/code&gt; attribute will soon return an empty string. To get ready for that

change, we are giving developers a chance to

&lt;a href="#preview-period"&gt;preview the updated API&lt;/a&gt; starting today.&lt;/p&gt;

&lt;h2 id="whats-changing"&gt;What’s changing?&lt;/h2&gt;

&lt;p&gt;The current &lt;a href="/v3/oauth_authorizations/"&gt;OAuth Authorizations API&lt;/a&gt; requires GitHub to store the full value for

each OAuth token on our servers. In order to increase the security for our

users, we are changing our architecture to store the SHA-256 digest of OAuth

tokens instead. GitHub securely hashes user passwords using bcrypt and we want

to provide comparable security for OAuth tokens as well.&lt;/p&gt;

&lt;p&gt;Rest assured that this change is an entirely proactive measure from GitHub and is not associated with any security incident.&lt;/p&gt;

&lt;h2 id="who-is-affected"&gt;Who is affected?&lt;/h2&gt;

&lt;p&gt;This change affects any code that relies on accessing the &lt;code&gt;token&lt;/code&gt; attribute from

&lt;a href="/v3/oauth_authorizations/#deprecation-notice"&gt;these OAuth Authorizations API responses&lt;/a&gt;.

For example, our own &lt;a href="https://mac.github.com/"&gt;GitHub for Mac&lt;/a&gt; and

&lt;a href="https://windows.github.com/"&gt;GitHub for Windows&lt;/a&gt; applications relied on reading the &lt;code&gt;token&lt;/code&gt;

from the &lt;a href="/v3/oauth_authorizations/#get-or-create-an-authorization-for-a-specific-app"&gt;Get-or-create an authorization for a specific app&lt;/a&gt; API, in order to support multiple installations of our desktop application for a single user.&lt;/p&gt;

&lt;h2 id="what-should-you-do"&gt;What should you do?&lt;/h2&gt;

&lt;p&gt;In order to reduce the impact of removing the &lt;code&gt;token&lt;/code&gt; attribute, the OAuth

Authorizations API has added a new request attribute (&lt;code&gt;fingerprint&lt;/code&gt;), added

three new response attributes (&lt;code&gt;token_last_eight&lt;/code&gt;, &lt;code&gt;hashed_token&lt;/code&gt;, and

&lt;code&gt;fingerprint&lt;/code&gt;), and added &lt;a href="/v3/oauth_authorizations/#get-or-create-an-authorization-for-a-specific-app-and-fingerprint"&gt;one new API&lt;/a&gt;.

While these new APIs and attributes do not replace the full functionality that

previously existed, they can be used in place of &lt;code&gt;token&lt;/code&gt; for most common use cases.&lt;/p&gt;

&lt;ul&gt;

&lt;li&gt;

&lt;p&gt;&lt;code&gt;token_last_eight&lt;/code&gt; returns the last eight characters of the associated OAuth

token. As an example, &lt;code&gt;token_last_eight&lt;/code&gt; could be used to display a list of

partial token values to help a user manage their OAuth tokens.&lt;/p&gt;

&lt;/li&gt;

&lt;li&gt;

&lt;p&gt;&lt;code&gt;hashed_token&lt;/code&gt; is the base64 of the SHA-256 digest of the token.

&lt;code&gt;hashed_token&lt;/code&gt; could be used to programmatically validate that a given token

matches an authorization returned by the API.&lt;/p&gt;

&lt;/li&gt;

&lt;li&gt;

&lt;p&gt;&lt;code&gt;fingerprint&lt;/code&gt; is a new optional request parameter that allows an OAuth

application to create multiple authorizations for a single user. &lt;code&gt;fingerprint&lt;/code&gt;

should be a string that distinguishes the new authorization from others

for the same client ID and user.&lt;/p&gt;

&lt;p&gt;For example, to differentiate installations of a desktop application across

multiple devices you might set &lt;code&gt;fingerprint&lt;/code&gt; to

&lt;code&gt;SHA256_HEXDIGEST("GitHub for Mac - MAC_ADDRESS_OF_MACHINE")&lt;/code&gt;. Since

&lt;code&gt;fingerprint&lt;/code&gt; is not meant to be a user-facing value, you should still set

the &lt;code&gt;note&lt;/code&gt; attribute to help a user differentiate between authorizations on their

&lt;a href="https://github.com/settings/applications"&gt;OAuth applications listing on GitHub&lt;/a&gt;.&lt;/p&gt;

&lt;/li&gt;

&lt;li&gt;

&lt;p&gt;&lt;a href="/v3/oauth_authorizations/#get-or-create-an-authorization-for-a-specific-app-and-fingerprint"&gt;Get-or-create an authorization for a specific app and fingerprint&lt;/a&gt;

is a new API that is analagous to the

&lt;a href="/v3/oauth_authorizations/#get-or-create-an-authorization-for-a-specific-app"&gt;Get-or-create an authorization for a specific app&lt;/a&gt;

API, but adds support for the new &lt;code&gt;fingerprint&lt;/code&gt; request parameter.&lt;/p&gt;

&lt;/li&gt;

&lt;/ul&gt;

&lt;h2 id="preview-period"&gt;Preview period&lt;/h2&gt;

&lt;p&gt;We are making the new Authorizations API available today for developers to

preview. During this period, we may change aspects of these endpoints. If we do,

we will announce the changes on the developer blog, but we will not provide any

advance notice.&lt;/p&gt;

&lt;p&gt;While these new APIs are in their preview period, you’ll need to provide the

following custom media type in the Accept header:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;application/vnd.github.mirage-preview+json

&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;We expect the preview period to last 4-6 weeks. (Stay tuned to the developer blog for updates.) At the end of the preview period, these changes will become an official and stable part of GitHub API.&lt;/p&gt;

&lt;h2 id="migration-period"&gt;Migration period&lt;/h2&gt;

&lt;p&gt;At the end of the preview period, we will announce the start of a migration period. Developers will have 8 weeks to update existing code to use the new APIs.&lt;/p&gt;

&lt;h2 id="why-sha-256-over-bcrypt"&gt;Why SHA-256 over bcrypt?&lt;/h2&gt;

&lt;p&gt;Some users may be curious why we are not using bcrypt to hash our OAuth tokens

like we do for user passwords. Bcrypt is purposefully computationally expensive

in order to mitigate brute force attacks against low entropy passwords. However,

OAuth tokens are highly random and are not susceptible to brute force attacks.

Given that OAuth token validation occurs for each request to the API we chose

SHA-256 for performance reasons.&lt;/p&gt;

&lt;p&gt;If you have any questions or feedback, please &lt;a href="https://github.com/contact?form%5Bsubject%5D=Removing+authorizations+token"&gt;drop us a line&lt;/a&gt;.&lt;/p&gt;

</content>

</entry>

<entry>

<id>tag:developer.github.com,2014-12-03:/changes/2014-12-03-preview-the-new-organization-webhooks-api/</id>

<title type="html">Preview the New Organization Webhooks API</title>

<published>2014-12-03T00:00:00Z</published>

<updated>2014-12-03T00:00:00Z</updated>

<author>

<name>jdpace</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2014-12-03-preview-the-new-organization-webhooks-api/" />

<content type="html">&lt;p&gt;Today we’re very excited &lt;a href="https://github.com/blog/1933-introducing-organization-webhooks"&gt;to announce Organization Webhooks&lt;/a&gt;.

Organization Webhooks allow you to subscribe to events that happen across an

entire organization.&lt;/p&gt;

&lt;p&gt;In addition to being able to subscribe to the existing repository oriented

events across an organization, we’re also adding some new events which are

exclusive to organization webhooks. The new &lt;a href="/v3/activity/events/types/#repositoryevent"&gt;&lt;code&gt;repository&lt;/code&gt;

event&lt;/a&gt; allows you to receive webhook payloads when a new

repository is created. By subscribing to the &lt;a href="/v3/activity/events/types/#membershipevent"&gt;&lt;code&gt;membership&lt;/code&gt;

event&lt;/a&gt;, you’ll be notified whenever a user is added or

removed from a team.&lt;/p&gt;

&lt;p&gt;We’re making this new API for Organization Webhooks available today &lt;a href="/v3/orgs/hooks/#preview-period"&gt;for

developers to preview&lt;/a&gt;. The preview period will allow us to &lt;a href="https://github.com/contact?form%5Bsubject%5D=Organization+Webhooks"&gt;get

your feedback&lt;/a&gt; before declaring the Organization Webhooks API final.

We expect the preview

period to last for roughly 30-60 days.&lt;/p&gt;

&lt;p&gt;As we discover opportunities to improve the API during the preview period, we

may ship changes that break clients using the preview version of the API. We

want to iterate quickly. To do so, we will announce any changes here (on the

developer blog), but we will not provide any advance notice.&lt;/p&gt;

&lt;p&gt;At the end of preview period, the Organization Webhooks API will become an

official component of GitHub API v3. At that point, the new Organization

Webhooks API will be stable and suitable for production use.&lt;/p&gt;

&lt;p&gt;We hope you’ll take it for a spin and &lt;a href="https://github.com/contact?form%5Bsubject%5D=Organization+Webhooks"&gt;send us your feedback&lt;/a&gt;.&lt;/p&gt;

</content>

</entry>

<entry>

<id>tag:developer.github.com,2014-11-25:/changes/2014-11-25-the-deployments-api-is-official/</id>

<title type="html">The Deployments API is official</title>

<published>2014-11-25T00:00:00Z</published>

<updated>2014-11-25T00:00:00Z</updated>

<author>

<name>atmos</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2014-11-25-the-deployments-api-is-official/" />

<content type="html">&lt;p&gt;We’re happy to announce that the &lt;a href="/v3/repos/deployments"&gt;Deployments API&lt;/a&gt; is officially part

of GitHub API v3. We now consider it stable for production use.&lt;/p&gt;

&lt;p&gt;Thanks to everyone who provided feedback during the preview period. We got

some great feedback, and hope this feature helps you build the tools you

need to make GitHub the best place to ship exactly the way you want.&lt;/p&gt;

&lt;h3 id="preview-media-type-no-longer-needed"&gt;Preview media type no longer needed&lt;/h3&gt;

&lt;p&gt;If you used the Deployments API during the preview period, you needed to

provide a custom media type in the &lt;code&gt;Accept&lt;/code&gt; header:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;application/vnd.github.cannonball-preview+json

&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;Now that the preview period has ended, you no longer need to pass this custom

media type.&lt;/p&gt;

&lt;p&gt;Instead, we &lt;a href="/v3/media"&gt;recommend&lt;/a&gt; that you specify &lt;code&gt;v3&lt;/code&gt; as the version in the

&lt;code&gt;Accept&lt;/code&gt; header:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;application/vnd.github.v3+json

&lt;/code&gt;&lt;/pre&gt;

&lt;h3 id="feedback"&gt;Feedback&lt;/h3&gt;

&lt;p&gt;We’ll never be done listening to you! As always, please don’t hesitate to

&lt;a href="https://github.com/contact?form%5Bsubject%5D=Deployments+API"&gt;share your feedback&lt;/a&gt;.&lt;/p&gt;

</content>

</entry>

<entry>

<id>tag:developer.github.com,2014-10-29:/changes/2014-10-24-status-api-limits/</id>

<title type="html">Status API Limits</title>

<published>2014-10-29T00:00:00Z</published>

<updated>2014-10-29T00:00:00Z</updated>

<author>

<name>rsanheim</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2014-10-24-status-api-limits/" />

<content type="html">&lt;p&gt;To ensure a high level of service for all API consumers, we will soon limit the number of &lt;a href="/v3/repos/statuses/"&gt;statuses&lt;/a&gt;

to 1000 per commit SHA, repository, and context.&lt;/p&gt;

&lt;p&gt;Beginning Monday, November 3rd, we will trim existing data sets that exceed this limit, deleting the oldest

records first. Attempts to create statuses beyond that limit will result in a &lt;a href="https://developer.github.com/v3/#client-errors"&gt;validation error&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;If you have any feedback or questions, please don’t hesistate to &lt;a href="https://github.com/contact?form%5Bsubject%5D=Combined+Status+API"&gt;contact&lt;/a&gt; us.&lt;/p&gt;

</content>

</entry>

<entry>

<id>tag:developer.github.com,2014-10-21:/changes/2014-10-21-deployment-webhook-payload-changes/</id>

<title type="html">Deployment webhook payload changes</title>

<published>2014-10-21T00:00:00Z</published>

<updated>2014-10-21T00:00:00Z</updated>

<author>

<name>atmos</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2014-10-21-deployment-webhook-payload-changes/" />

<content type="html">&lt;p&gt;On November 4th, 2014, we will begin sending a new format for &lt;a href="https://developer.github.com/v3/activity/events/types/#deploymentevent"&gt;deployment&lt;/a&gt; and &lt;a href="https://developer.github.com/v3/activity/events/types/#deploymentstatusevent"&gt;deployment status&lt;/a&gt; payloads for webhooks. In the meantime we’ll be running in a compatability mode that will give integrators the time needed to start taking advantage of the new format. Integrators who are working with webhooks and deployments are advised to upgrade to the new payload format to avoid service interruption.&lt;/p&gt;

&lt;p&gt;This change brings the payloads for these events more inline with the responses you’d receive from the API. Instead of having deployment and deployment status attributes as top-level keys, we will now nest them under &lt;code&gt;deployment&lt;/code&gt; and &lt;code&gt;deployment_status&lt;/code&gt; keys. Since we’re still in the &lt;a href="https://developer.github.com/changes/2014-01-09-preview-the-new-deployments-api/"&gt;preview period&lt;/a&gt; for the deployments API we felt it was best to correct this inconsistency now.&lt;/p&gt;

&lt;h2 id="deploymentevent-changes"&gt;DeploymentEvent Changes&lt;/h2&gt;

&lt;h4 id="old-format"&gt;Old Format&lt;/h4&gt;

&lt;pre&gt;&lt;code class="language-javascript highlight"&gt;&lt;span class="p"&gt;{&lt;/span&gt;

&lt;span class="s2"&gt;"id"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;42&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"sha"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"deadbeef"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"ref"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"master"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"task"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"deploy"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"my-org/our-app"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"environment"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"production"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"payload"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="err"&gt;…&lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;

&lt;span class="s2"&gt;"description"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Deploying master"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"repository"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="err"&gt;…&lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;

&lt;span class="s2"&gt;"sender"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="err"&gt;…&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="p"&gt;}&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;h4 id="current-format---20141022"&gt;Current Format - 2014/10/22&lt;/h4&gt;

&lt;pre&gt;&lt;code class="language-javascript highlight"&gt;&lt;span class="p"&gt;{&lt;/span&gt;

&lt;span class="s2"&gt;"id"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;42&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"sha"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"deadbeef"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"ref"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"master"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"task"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"deploy"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"my-org/our-app"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"environment"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"production"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"payload"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="err"&gt;…&lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;

&lt;span class="s2"&gt;"description"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Deploying master"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"repository"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="err"&gt;…&lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;

&lt;span class="s2"&gt;"deployment"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;

&lt;span class="s2"&gt;"url"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://api.github.com/repos/my-org/our-app/deployments/42"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"id"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;42&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"sha"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"deadbeef"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"ref"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"master"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"task"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"deploy"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"environment"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"production"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"payload"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="err"&gt;…&lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;

&lt;span class="s2"&gt;"description"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Deploying master"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"creator"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="err"&gt;…&lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;

&lt;span class="s2"&gt;"created_at"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"2014-09-23T16:37:49Z"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"updated_at"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"2014-09-23T16:37:49Z"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"statuses_url"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://api.github.com/repos/my-org/our-app/deployments/42/statuses"&lt;/span&gt;

&lt;span class="p"&gt;},&lt;/span&gt;

&lt;span class="s2"&gt;"sender"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="err"&gt;…&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="p"&gt;}&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;h4 id="new-format---20141105"&gt;New Format - 2014/11/05&lt;/h4&gt;

&lt;pre&gt;&lt;code class="language-javascript highlight"&gt;&lt;span class="p"&gt;{&lt;/span&gt;

&lt;span class="s2"&gt;"deployment"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;

&lt;span class="s2"&gt;"url"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://api.github.com/repos/my-org/our-app/deployments/42"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"id"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;42&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"sha"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"deadbeef"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"ref"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"master"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"task"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"deploy"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"environment"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"production"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"payload"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="err"&gt;…&lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;

&lt;span class="s2"&gt;"description"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Deploying master"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"creator"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="err"&gt;…&lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;

&lt;span class="s2"&gt;"created_at"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"2014-09-23T16:37:49Z"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"updated_at"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"2014-09-23T16:37:49Z"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"statuses_url"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://api.github.com/repos/my-org/our-app/deployments/42/statuses"&lt;/span&gt;

&lt;span class="p"&gt;},&lt;/span&gt;

&lt;span class="s2"&gt;"repository"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="err"&gt;…&lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;

&lt;span class="s2"&gt;"sender"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="err"&gt;…&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="p"&gt;}&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;h2 id="deploymentstatusevent-changes"&gt;DeploymentStatusEvent Changes&lt;/h2&gt;

&lt;h4 id="old-format-1"&gt;Old Format&lt;/h4&gt;

&lt;pre&gt;&lt;code class="language-javascript highlight"&gt;&lt;span class="p"&gt;{&lt;/span&gt;

&lt;span class="s2"&gt;"id"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;2600&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"state"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"success"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"deployment"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="err"&gt;…&lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;

&lt;span class="s2"&gt;"target_url"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://gist.github.com/deadbeef"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"description"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Deployment was successful"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"repository"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="err"&gt;…&lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;

&lt;span class="s2"&gt;"sender"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="err"&gt;…&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="p"&gt;}&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;h4 id="current-format---20141022-1"&gt;Current Format - 2014/10/22&lt;/h4&gt;

&lt;pre&gt;&lt;code class="language-javascript highlight"&gt;&lt;span class="p"&gt;{&lt;/span&gt;

&lt;span class="s2"&gt;"id"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;2600&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"state"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"success"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"target_url"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://gist.github.com/deadbeef"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"description"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Deployment was successful"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"repository"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="err"&gt;…&lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;

&lt;span class="s2"&gt;"deployment_status"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;

&lt;span class="s2"&gt;"url"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://api.github.com/repos/my-org/our-app/deployments/42/statuses2600"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"id"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;2600&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"state"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"success"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"creator"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="err"&gt;…&lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;

&lt;span class="s2"&gt;"target_url"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://gist.github.com/deadbeef"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"description"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Deployment was successful"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"created_at"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"2014-09-23T16:45:49Z"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"updated_at"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"2014-09-23T16:45:49Z"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"deployment_url"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://api.github.com/repos/my-org/our-app/deployments/42"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"repository_url"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://api.github.com/repos/my-org/our-app"&lt;/span&gt;

&lt;span class="p"&gt;},&lt;/span&gt;

&lt;span class="s2"&gt;"deployment"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="err"&gt;…&lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;

&lt;span class="s2"&gt;"sender"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="err"&gt;…&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="p"&gt;}&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;h4 id="new-format---20141105-1"&gt;New Format - 2014/11/05&lt;/h4&gt;

&lt;pre&gt;&lt;code class="language-javascript highlight"&gt;&lt;span class="p"&gt;{&lt;/span&gt;

&lt;span class="s2"&gt;"deployment_status"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;

&lt;span class="s2"&gt;"url"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://api.github.com/repos/my-org/our-app/deployments/42/statuses2600"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"id"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;2600&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"state"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"success"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"creator"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="err"&gt;…&lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;

&lt;span class="s2"&gt;"target_url"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://gist.github.com/deadbeef"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"description"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Deployment was successful"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"created_at"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"2014-09-23T16:45:49Z"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"updated_at"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"2014-09-23T16:45:49Z"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"deployment_url"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://api.github.com/repos/my-org/our-app/deployments/42"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"repository_url"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://api.github.com/repos/my-org/our-app"&lt;/span&gt;

&lt;span class="p"&gt;},&lt;/span&gt;

&lt;span class="s2"&gt;"deployment"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="err"&gt;…&lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;

&lt;span class="s2"&gt;"repository"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="err"&gt;…&lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;

&lt;span class="s2"&gt;"sender"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="err"&gt;…&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="p"&gt;}&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;If you have any questions or feedback, please &lt;a href="https://github.com/contact?form%5Bsubject%5D=Deployments+API"&gt;get in touch&lt;/a&gt;.&lt;/p&gt;

</content>

</entry>

<entry>

<id>tag:developer.github.com,2014-10-16:/changes/2014-10-16-removed-ssl-version-3-support-from-webhooks-and-services/</id>

<title type="html">Removed SSLv3 support from webhooks and services</title>

<published>2014-10-16T00:00:00Z</published>

<updated>2014-10-16T00:00:00Z</updated>

<author>

<name>kdaigle</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2014-10-16-removed-ssl-version-3-support-from-webhooks-and-services/" />

<content type="html">&lt;p&gt;This morning, we &lt;a href="https://github.com/github/github-services/pull/949"&gt;removed support&lt;/a&gt; for the &lt;code&gt;ssl_version&lt;/code&gt; webhook configuration

option and made &lt;code&gt;TLS 1.X&lt;/code&gt; the default cryptographic protocol to address the &lt;a href="https://www.openssl.org/~bodo/ssl-poodle.pdf"&gt;POODLE exploit&lt;/a&gt;.

You should no longer set or rely on the &lt;code&gt;ssl_version&lt;/code&gt; configuration option.&lt;/p&gt;

&lt;p&gt;If you have any questions or feedback, please &lt;a href="https://github.com/contact?form%5Bsubject%5D=Removed+SSLv3+support+from+webhooks+and+services"&gt;drop us a line&lt;/a&gt;.&lt;/p&gt;

</content>

</entry>

<entry>

<id>tag:developer.github.com,2014-10-06:/changes/2014-10-06-new-attributes-for-issue-events-api/</id>

<title type="html">New Attributes for Issue Events API</title>

<published>2014-10-06T00:00:00Z</published>

<updated>2014-10-06T00:00:00Z</updated>

<author>

<name>jdpace</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2014-10-06-new-attributes-for-issue-events-api/" />

<content type="html">&lt;p&gt;We’ve made it easier to track changes to issues. The Issue Events API now provides more context for several event types:&lt;/p&gt;

&lt;ul&gt;

&lt;li&gt;

&lt;code&gt;assigned&lt;/code&gt; and &lt;code&gt;unassigned&lt;/code&gt; events now include an &lt;code&gt;assignee&lt;/code&gt; object so you can see just who was assigned or unassigned.&lt;/li&gt;

&lt;li&gt;

&lt;code&gt;labeled&lt;/code&gt; and &lt;code&gt;unlabeled&lt;/code&gt; events include a &lt;code&gt;label&lt;/code&gt; object.&lt;/li&gt;

&lt;li&gt;

&lt;code&gt;milestoned&lt;/code&gt; and &lt;code&gt;demilesoned&lt;/code&gt; events include a &lt;code&gt;milestone&lt;/code&gt; object.&lt;/li&gt;

&lt;li&gt;

&lt;code&gt;renamed&lt;/code&gt; events include a &lt;code&gt;rename&lt;/code&gt; object with the title before and after the rename.&lt;/li&gt;

&lt;/ul&gt;

&lt;p&gt;Check out the &lt;a href="/v3/issues/events/"&gt;Issue Events API documentation&lt;/a&gt; for a full list of supported events. If you have

any questions or feedback, please &lt;a href="https://github.com/contact?form%5Bsubject%5D=New+Attrs+for+Issue+Events+API"&gt;drop us a line&lt;/a&gt;.&lt;/p&gt;

</content>

</entry>

<entry>

<id>tag:developer.github.com,2014-09-23:/changes/2014-09-23-one-more-week-before-the-add-team-member-api-breaking-change/</id>

<title type="html">One more week before the "Add team member" API breaking change</title>

<published>2014-09-23T00:00:00Z</published>

<updated>2014-09-23T00:00:00Z</updated>

<author>

<name>jakeboxer</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2014-09-23-one-more-week-before-the-add-team-member-api-breaking-change/" />

<content type="html">&lt;p&gt;&lt;strong&gt;UPDATE (2014-09-30):&lt;/strong&gt; In response to feedback from developers, we’re delaying the breaking change to the &lt;a href="/v3/orgs/teams/#add-team-member"&gt;“Add team member” API&lt;/a&gt; until Monday, &lt;strong&gt;October 6, 2014&lt;/strong&gt;. The change will go into effect for all requests on that date.&lt;/p&gt;

&lt;p&gt;Starting October 6, if you use &lt;a href="/v3/orgs/teams/#add-team-member"&gt;the “Add team member” API&lt;/a&gt; to add a user to a team and that user isn’t already on another team in your organization, the request will fail. To avoid this, be sure to use the &lt;a href="/v3/orgs/teams/#add-team-membership"&gt;“Add team membership” API&lt;/a&gt;.&lt;/p&gt;

&lt;h3 id="the-organization-and-team-membership-apis-are-now-official"&gt;The Organization and Team Membership APIs are now official&lt;/h3&gt;

&lt;p&gt;As promised in &lt;a href="/changes/2014-09-16-finalizing-the-organization-and-team-membership-apis/"&gt;our blog post earlier this month&lt;/a&gt;, the &lt;a href="/changes/2014-08-28-accepting-organization-invitations-from-the-api/"&gt;Organization Membership&lt;/a&gt; and &lt;a href="/changes/2014-08-05-team-memberships-api/"&gt;Team Membership&lt;/a&gt; APIs are now an official part of the GitHub API! The preview media type is no longer required to access them.&lt;/p&gt;

&lt;p&gt;If you have any questions or feedback, please &lt;a href="https://github.com/contact?form%5Bsubject%5D=Organization+and+Team+Membership+APIs"&gt;get in touch with us&lt;/a&gt;!&lt;/p&gt;

</content>

</entry>

<entry>

<id>tag:developer.github.com,2014-09-16:/changes/2014-09-16-finalizing-the-organization-and-team-membership-apis/</id>

<title type="html">Finalizing the Organization and Team Membership APIs</title>

<published>2014-09-16T00:00:00Z</published>

<updated>2014-09-16T00:00:00Z</updated>

<author>

<name>jakeboxer</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2014-09-16-finalizing-the-organization-and-team-membership-apis/" />

<content type="html">&lt;p&gt;For the past few weeks, the new &lt;a href="/changes/2014-08-28-accepting-organization-invitations-from-the-api/"&gt;Organization Membership&lt;/a&gt; and &lt;a href="/changes/2014-08-05-team-memberships-api/"&gt;Team Membership&lt;/a&gt; APIs have been available for early access via a preview media type. As of today, these APIs are stable and suitable for production use.&lt;/p&gt;

&lt;h3 id="preview-period-ends-on-september-23"&gt;Preview period ends on September 23&lt;/h3&gt;

&lt;p&gt;On September 23, 2014, these APIs will become official parts of the GitHub API v3. At that time, the preview media type will no longer be required to access these APIs.&lt;/p&gt;

&lt;h3 id="reminder-breaking-change-to-legacy-endpoint"&gt;Reminder: Breaking change to legacy endpoint&lt;/h3&gt;

&lt;p&gt;The &lt;a href="/v3/orgs/teams/#add-team-member"&gt;breaking change to the “Add team member” endpoint&lt;/a&gt; will also go into effect for all requests on &lt;strong&gt;September 23, 2014&lt;/strong&gt;. At that time, if you use the &lt;a href="/v3/orgs/teams/#add-team-member"&gt;add team member&lt;/a&gt; endpoint to add a user to a team and that user isn’t already on another team in your organization, the request will fail. To avoid this, be sure to use the &lt;a href="/v3/orgs/teams/#add-team-membership"&gt;add team membership&lt;/a&gt; endpoint.&lt;/p&gt;

&lt;h3 id="addition-to-the-organization-membership-api"&gt;Addition to the Organization Membership API&lt;/h3&gt;

&lt;p&gt;Thanks to your feedback, we’ve updated the Organization Membership API to provide direct access to basic information about the organization whenever you fetch a &lt;a href="/v3/orgs/members/#list-your-organization-memberships"&gt;list of memberships&lt;/a&gt; or a &lt;a href="/v3/orgs/members/#get-your-organization-membership"&gt;single membership&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;If you have any questions or feedback, please &lt;a href="https://github.com/contact?form%5Bsubject%5D=Organization+and+Team+Membership+APIs"&gt;get in touch with us&lt;/a&gt;!&lt;/p&gt;

</content>

</entry>

<entry>

<id>tag:developer.github.com,2014-09-12:/changes/2014-09-12-changing-organization-feeds/</id>

<title type="html">Changing organization feeds in the Feeds API</title>

<published>2014-09-12T00:00:00Z</published>

<updated>2014-09-12T00:00:00Z</updated>

<author>

<name>mastahyeti</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2014-09-12-changing-organization-feeds/" />

<content type="html">&lt;p&gt;We have deprecated the &lt;code&gt;current_user_organization_url&lt;/code&gt; attribute and the

&lt;code&gt;current_user_organization.href&lt;/code&gt; attribute in the &lt;a href="/v3/activity/feeds/"&gt;Feeds API&lt;/a&gt;. If you make