<?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-08-04T00: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-08-04:/changes/2015-08-04-get-license-contents/</id>

<title type="html">Get the contents of a repository’s license</title>

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

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

<author>

<name>benbalter</name>

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

</author>

<link rel="alternate" href="http://developer.github.com/changes/2015-08-04-get-license-contents/" />

<content type="html">&lt;p&gt;The &lt;a href="/v3/licenses/"&gt;License API Preview&lt;/a&gt; now allows you to retrieve the contents of a repository’s open source license. As before, when the appropriate preview media type is passed, the repository endpoint will return information about the detected license, if any:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;curl -H "Accept: application/vnd.github.drax-preview+json" https://api.github.com/repos/benbalter/gman

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

&lt;p&gt;You can now also get the contents of the repository’s license file, whether or not the license was successfully identified via the license contents endpoint:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;curl -H "Accept: application/vnd.github.drax-preview+json" https://api.github.com/repos/benbalter/gman/license

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

&lt;p&gt;Similar to &lt;a href="/v3/repos/contents/#get-contents"&gt;the repository contents API&lt;/a&gt;, the license contents method also supports &lt;a href="/v3/repos/contents/#custom-media-types"&gt;custom media types&lt;/a&gt; for retrieving the raw license content or rendered license HTML.&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;curl -H "Accept: application/vnd.github.drax-preview.raw" https://api.github.com/repos/benbalter/gman/license

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

&lt;p&gt;For more information, see &lt;a href="/v3/licenses/#get-the-contents-of-a-repositorys-license"&gt;the license API documentation&lt;/a&gt;, and as always, if you have any questions or feedback, please &lt;a href="https://github.com/contact?form%5Bsubject%5D=License+API"&gt;get in touch with us&lt;/a&gt;.&lt;/p&gt;

</content>

</entry>

<entry>

<id>tag:developer.github.com,2015-07-22:/changes/2015-07-22-more-flexible-options-for-listing-repositories/</id>

<title type="html">More flexible options for listing repositories</title>

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

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

<author>

<name>jakeboxer</name>

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

</author>

<link rel="alternate" href="http://developer.github.com/changes/2015-07-22-more-flexible-options-for-listing-repositories/" />

<content type="html">&lt;p&gt;The &lt;a href="/v3/repos/#list-your-repositories"&gt;List your repositories&lt;/a&gt; API now offers additional parameters to help you fetch the exact set of repositories you’re looking for:&lt;/p&gt;

&lt;ul&gt;

&lt;li&gt;The &lt;code&gt;visibility&lt;/code&gt; parameter lets you request only your public repositories, only your private repositories, or both.&lt;/li&gt;

&lt;li&gt;With the &lt;code&gt;affiliation&lt;/code&gt; parameter, you can ask for repositories you own, repositories where you are a collaborator, repositories you have access to as an organization member, or any combination that suits your needs.&lt;/li&gt;

&lt;/ul&gt;

&lt;p&gt;Use these new parameters separately, together, or in combination with other parameters to craft flexible queries that fetch the specific repositories you’re seeking.&lt;/p&gt;

&lt;p&gt;For full details, check out the &lt;a href="/v3/repos/#list-your-repositories"&gt;documentation&lt;/a&gt;. If you have any questions, please &lt;a href="https://github.com/contact?form%5Bsubject%5D=List+your+repositories+API"&gt;get in touch&lt;/a&gt;!&lt;/p&gt;

</content>

</entry>

<entry>

<id>tag:developer.github.com,2015-07-21:/changes/2015-07-21-automatic-redirects-for-renamed-repositories/</id>

<title type="html">Automatic redirects for renamed repositories</title>

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

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

<author>

<name>jasonrudolph</name>

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

</author>

<link rel="alternate" href="http://developer.github.com/changes/2015-07-21-automatic-redirects-for-renamed-repositories/" />

<content type="html">&lt;p&gt;To help API clients gracefully handle renamed repositories, the API now &lt;a href="/changes/2015-04-17-preview-repository-redirects/"&gt;automatically redirects to the repository’s new location&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Our thanks goes out to everyone that tried out this enhancement &lt;a href="/changes/2015-04-17-preview-repository-redirects/"&gt;during the preview period&lt;/a&gt;. During the preview period, you needed to &lt;a href="/changes/2015-04-17-preview-repository-redirects/#how-can-i-try-out-the-redirects"&gt;provide a custom media type in the &lt;code&gt;Accept&lt;/code&gt; header&lt;/a&gt; to opt-in to the redirects. Now that the preview period has ended, you no longer need to specify this custom &lt;a href="/v3/media/"&gt;media type&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;To learn more about these redirects and how they benefit your applications, be sure to check out the &lt;a href="/changes/2015-04-17-preview-repository-redirects/"&gt;preview period announcement&lt;/a&gt;. As always, if you have any questions, we’re &lt;a href="https://github.com/contact?form%5Bsubject%5D=API+Repository+Redirects"&gt;here to help&lt;/a&gt;.&lt;/p&gt;

</content>

</entry>

<entry>

<id>tag:developer.github.com,2015-06-24:/changes/2015-06-24-breaking-changes-to-organization-permissions-are-now-official/</id>

<title type="html">Breaking changes to organization permissions are now official</title>

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

<updated>2015-06-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-06-24-breaking-changes-to-organization-permissions-are-now-official/" />

<content type="html">&lt;p&gt;As &lt;a href="/changes/2015-06-10-breaking-changes-to-organization-permissions-coming-on-june-24"&gt;promised earlier this month&lt;/a&gt;, the &lt;a href="/changes/2014-12-08-organization-permissions-api-preview/"&gt;API changes&lt;/a&gt; related to managing organization members and repositories are now official parts of the GitHub API.&lt;/p&gt;

&lt;p&gt;During the migration period, you needed to &lt;a href="/changes/2015-06-10-breaking-changes-to-organization-permissions-coming-on-june-24/#migration-period"&gt;provide a custom media type in the &lt;code&gt;Accept&lt;/code&gt; header&lt;/a&gt; to opt-in to the changes. Now that the migration period has ended, you no longer need to specify this custom &lt;a href="/v3/media"&gt;media type&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+Permissions+API"&gt;get in touch with us&lt;/a&gt;!&lt;/p&gt;

</content>

</entry>

<entry>

<id>tag:developer.github.com,2015-06-24:/changes/2015-06-24-api-enhancements-for-working-with-organization-permissions/</id>

<title type="html">API enhancements for working with organization permissions</title>

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

<updated>2015-06-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-06-24-api-enhancements-for-working-with-organization-permissions/" />

<content type="html">&lt;p&gt;We’re introducing several enhancements to allow API developers to take advantage of the &lt;a href="https://github.com/blog/2020-improved-organization-permissions"&gt;improved organization permissions&lt;/a&gt; that we are rolling out. Learn about these enhancements and how you can try them out below.&lt;/p&gt;

&lt;p&gt;Since we’re rolling out the &lt;a href="https://github.com/blog/2020-improved-organization-permissions"&gt;improved organization permissions&lt;/a&gt; improvements slowly, these enhancements will only apply to certain organizations at first. Most of these enhancements will degrade gracefully (returning an empty array or something similar) if used on an organization that doesn’t support improved organization permissions yet. Check the documentation for your specific API to see if errors are possible.&lt;/p&gt;

&lt;h2 id="api-enhancements"&gt;API enhancements&lt;/h2&gt;

&lt;h3 id="team-permissions"&gt;Team permissions&lt;/h3&gt;

&lt;p&gt;In our improved permissions system, a team no longer has a single permission that applies to all of its repositories. Instead, each repository is added to a team with its own permission. For example, an organization could use a single team to grant pull access to one repository, push access to a second, and admin access to a third.&lt;/p&gt;

&lt;p&gt;The team APIs now support this more granular notion of permissions:&lt;/p&gt;

&lt;ul&gt;

&lt;li&gt;The &lt;a href="/v3/orgs/teams/#add-team-repo"&gt;Add team repository&lt;/a&gt; API accepts a &lt;code&gt;permission&lt;/code&gt; parameter, so that you can specify whether a team should grant &lt;code&gt;pull&lt;/code&gt;, &lt;code&gt;push&lt;/code&gt;, or &lt;code&gt;admin&lt;/code&gt; access on a given repository.&lt;/li&gt;

&lt;li&gt;In the &lt;a href="/v3/orgs/teams/#list-team-repos"&gt;List team repositories&lt;/a&gt; and &lt;a href="/v3/orgs/teams/#get-team-repo"&gt;Check if a team manages a repository&lt;/a&gt; API, the response includes a &lt;code&gt;permissions&lt;/code&gt; attribute, indicating whether the team grants &lt;code&gt;pull&lt;/code&gt;, &lt;code&gt;push&lt;/code&gt;, or &lt;code&gt;admin&lt;/code&gt; access on each repository.&lt;/li&gt;

&lt;li&gt;The &lt;code&gt;permission&lt;/code&gt; parameter in the &lt;a href="/v3/orgs/teams/#create-team"&gt;Create team&lt;/a&gt; and &lt;a href="/v3/orgs/teams/#edit-team"&gt;Edit team&lt;/a&gt; APIs is deprecated. Since teams can grant a different permission on each repository, this parameter no longer dictates what permission a team grants on all of its repositories. Instead, it dictates the default permission that the &lt;a href="/v3/orgs/teams/#add-team-repo"&gt;Add team repository&lt;/a&gt; API will use for requests where no &lt;code&gt;permission&lt;/code&gt; parameter is specified.&lt;/li&gt;

&lt;/ul&gt;

&lt;h3 id="team-privacy"&gt;Team privacy&lt;/h3&gt;

&lt;p&gt;We now allow you to modify the privacy level of your teams. A “secret” team can only be seen by organization owners and people who are members of that team (which is how all teams have worked historically), while a “closed” team is visible to every member of the organization (which makes it easier to use &lt;a href="https://github.com/blog/1121-introducing-team-mentions"&gt;@mentions&lt;/a&gt; throughout your organization).&lt;/p&gt;

&lt;p&gt;The team APIs now support this new team privacy concept:&lt;/p&gt;

&lt;ul&gt;

&lt;li&gt;The &lt;a href="/v3/orgs/teams/#create-team"&gt;Create team&lt;/a&gt; and &lt;a href="/v3/orgs/teams/#edit-team"&gt;Edit team&lt;/a&gt; APIs accept a &lt;code&gt;privacy&lt;/code&gt; parameter, so that you can specify whether a team should be &lt;code&gt;secret&lt;/code&gt; or &lt;code&gt;closed&lt;/code&gt;.&lt;/li&gt;

&lt;li&gt;All team resources in the API now include a &lt;code&gt;privacy&lt;/code&gt; attribute, indicating whether the team is &lt;code&gt;secret&lt;/code&gt; or &lt;code&gt;closed&lt;/code&gt;.&lt;/li&gt;

&lt;/ul&gt;

&lt;h3 id="team-maintainers"&gt;Team maintainers&lt;/h3&gt;

&lt;p&gt;We’ve added the ability for you to delegate team maintenance to non-owners, reducing the workload for your organization’s owners. You can now promote a non-owner member of a team to be a “maintainer” of that team. A maintainer can add and remove team members and change the team’s title and description.&lt;/p&gt;

&lt;p&gt;The team membership APIs now support this new team maintainer concept:&lt;/p&gt;

&lt;ul&gt;

&lt;li&gt;The &lt;a href="/v3/orgs/teams/#add-team-membership"&gt;Add team membership&lt;/a&gt; API accepts a &lt;code&gt;role&lt;/code&gt; parameter, so that you can specify whether a given team member should be a &lt;code&gt;maintainer&lt;/code&gt; or a regular &lt;code&gt;member&lt;/code&gt;.&lt;/li&gt;

&lt;li&gt;The &lt;a href="/v3/orgs/teams/#list-team-members"&gt;List team members&lt;/a&gt; API accepts an optional &lt;code&gt;role&lt;/code&gt; parameter, allowing you to fetch only &lt;code&gt;maintainer&lt;/code&gt;s or only regular &lt;code&gt;member&lt;/code&gt;s.&lt;/li&gt;

&lt;li&gt;In the &lt;a href="/v3/orgs/teams/#get-team-membership"&gt;Get team membership&lt;/a&gt; and &lt;a href="/v3/orgs/teams/#add-team-membership"&gt;Add team membership&lt;/a&gt; APIs, the response includes a &lt;code&gt;role&lt;/code&gt; attribute, indicating whether a user is a &lt;code&gt;maintainer&lt;/code&gt; or a regular &lt;code&gt;member&lt;/code&gt; of the team.&lt;/li&gt;

&lt;/ul&gt;

&lt;p&gt;For more information on our improved team permissions, check out our &lt;a href="https://help.github.com/articles/improved-organization-permissions/#understanding-team-permissions"&gt;documentation&lt;/a&gt;.&lt;/p&gt;

&lt;h3 id="filtering-organization-members-by-role"&gt;Filtering organization members by role&lt;/h3&gt;

&lt;p&gt;The organization &lt;a href="/v3/orgs/members/#members-list"&gt;Members list&lt;/a&gt; API now accepts a &lt;code&gt;role&lt;/code&gt; parameter, so that you can request to see only the owners (or non-owners) of your organization.&lt;/p&gt;

&lt;h3 id="repository-collaborators"&gt;Repository collaborators&lt;/h3&gt;

&lt;p&gt;We now allow you to add collaborators directly to organization-owned repositories, just like we always have for user-owned repositories.&lt;/p&gt;

&lt;p&gt;The collaborator APIs now support organization-owned repositories:&lt;/p&gt;

&lt;ul&gt;

&lt;li&gt;The &lt;a href="/v3/repos/collaborators/#add-collaborator"&gt;Add user as a collaborator&lt;/a&gt; API works for organization-owned repositories. We’ve also added a &lt;code&gt;permission&lt;/code&gt; parameter to it (currently valid for organization-owned repositories only), so that you can specify what level of access the collaborator should have on the repository.&lt;/li&gt;

&lt;li&gt;In the &lt;a href="/v3/repos/collaborators/#list"&gt;List collaborators&lt;/a&gt; API, the response includes a &lt;code&gt;permissions&lt;/code&gt; attribute describing the permissions that each collaborator has on your organization’s repositories.&lt;/li&gt;

&lt;/ul&gt;

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

&lt;p&gt;Starting today, these API enhancements are available for developers to preview. At the end of the preview period, these enhancements will become official components of the GitHub API.&lt;/p&gt;

&lt;p&gt;While these enhancements are in their preview period, you’ll need to provide the following &lt;a href="/v3/media/"&gt;custom 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.ironman-preview+json

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

&lt;p&gt;During the preview period, we may change aspects of these enhancements. 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="send-us-your-feedback"&gt;Send us your feedback&lt;/h2&gt;

&lt;p&gt;We would love to hear your thoughts on these enhancements. 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-06-24:/changes/2015-06-24-licenses-api-update/</id>

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

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

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

<author>

<name>mislav</name>

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

</author>

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

<content type="html">&lt;p&gt;We are expanding the &lt;a href="/v3/licenses"&gt;Licenses API&lt;/a&gt; to make it more useful for auditing license usage across all repositories owned by a user or organization.&lt;/p&gt;

&lt;p&gt;Before, license information was only returned for 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;Now, license information will also be included in reponses from endpoints that list multiple repositories, such as &lt;a href="/v3/repos/#list-organization-repositories"&gt;List organization repositories&lt;/a&gt;:&lt;/p&gt;

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

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

&lt;p&gt;As before, 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;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-06-17:/changes/2015-06-17-organizations-endpoint/</id>

<title type="html">List all organizations</title>

<published>2015-06-17T00:00:00Z</published>

<updated>2015-06-17T00:00:00Z</updated>

<author>

<name>keavy</name>

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

</author>

<link rel="alternate" href="http://developer.github.com/changes/2015-06-17-organizations-endpoint/" />

<content type="html">&lt;p&gt;We’ve added a &lt;a href="/v3/orgs#list-all-organizations"&gt;new API method&lt;/a&gt; to list all organizations:&lt;/p&gt;

&lt;pre class="terminal"&gt;

$ curl https://api.github.com/organizations

[

{

"login": "github",

"id": 9919,

"url": "https://api.github.com/orgs/github",

"repos_url": "https://api.github.com/orgs/github/repos",

"events_url": "https://api.github.com/orgs/github/events",

"members_url": "https://api.github.com/orgs/github/members{/member}",

"public_members_url": "https://api.github.com/orgs/github/public_members{/member}",

"avatar_url": "https://avatars.githubusercontent.com/u/9919?v=3",

"description": "GitHub, the company."

},

...

]

&lt;/pre&gt;

&lt;p&gt;As always, if you have any questions or feedback, please &lt;a href="https://github.com/contact?form%5Bsubject%5D=API+-+Listing+Organizations"&gt;drop us a line&lt;/a&gt;.&lt;/p&gt;

</content>

</entry>

<entry>

<id>tag:developer.github.com,2015-06-11:/changes/2015-06-11-pages-a-records/</id>

<title type="html">GitHub Pages' A Records Added to Meta API</title>

<published>2015-06-11T00:00:00Z</published>

<updated>2015-06-11T00:00:00Z</updated>

<author>

<name>leereilly</name>

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

</author>

<link rel="alternate" href="http://developer.github.com/changes/2015-06-11-pages-a-records/" />

<content type="html">&lt;p&gt;The &lt;a href="/v3/meta/"&gt;Meta API&lt;/a&gt; now includes the A record IP addresses for &lt;a href="https://pages.github.com/"&gt;GitHub Pages&lt;/a&gt;.&lt;/p&gt;

&lt;pre class="terminal"&gt;

$ curl https://api.github.com/meta

&lt;/pre&gt;

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

&lt;span class="s2"&gt;"verifiable_password_authentication"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"github_services_sha"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"23c6105183b626cf74c045f6d53af7a178bfdb4c"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"hooks"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;

&lt;span class="s2"&gt;"192.30.252.0/22"&lt;/span&gt;

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

&lt;span class="s2"&gt;"git"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;

&lt;span class="s2"&gt;"192.30.252.0/22"&lt;/span&gt;

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

&lt;span class="s2"&gt;"pages"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;

&lt;span class="s2"&gt;"192.30.252.153/32"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;

&lt;span class="s2"&gt;"192.30.252.154/32"&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;These IP addresses are used to &lt;a href="https://help.github.com/articles/tips-for-configuring-an-a-record-with-your-dns-provider/"&gt;configure A records with your DNS provider for GitHub Pages&lt;/a&gt;. These addresses have changed a few times in the past. This API always provides the current addresses so that you can automate the process of keeping your DNS records up to date.&lt;/p&gt;

&lt;p&gt;If you have any questions, please &lt;a href="https://github.com/contact?form%5Bsubject%5D=GitHub+Pages+A+Records+Added+to+API"&gt;get in touch&lt;/a&gt;. We’ll be happy to help.&lt;/p&gt;

</content>

</entry>

<entry>

<id>tag:developer.github.com,2015-06-10:/changes/2015-06-10-breaking-changes-to-organization-permissions-coming-on-june-24/</id>

<title type="html">Breaking changes to organization permissions coming on June 24</title>

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

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

<author>

<name>jakeboxer</name>

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

</author>

<link rel="alternate" href="http://developer.github.com/changes/2015-06-10-breaking-changes-to-organization-permissions-coming-on-june-24/" />

<content type="html">&lt;p&gt;Back in January, we &lt;a href="/changes/2015-01-07-prepare-for-organization-permissions-changes/"&gt;encouraged developers to update their applications&lt;/a&gt; to prepare for &lt;a href="/changes/2014-12-08-organization-permissions-api-preview/"&gt;upcoming API changes&lt;/a&gt; related to managing organization members and repositories. In order to support the upcoming &lt;a href="https://github.com/blog/2020-improved-organization-permissions/"&gt;improvements to organization permissions&lt;/a&gt;, these changes will become official parts of GitHub API v3 on &lt;strong&gt;June 24&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;If your application relies on any of the affected functionality (described below), be sure to &lt;strong&gt;update your code before June 24&lt;/strong&gt; to account for these changes.&lt;/p&gt;

&lt;h2 id="breaking-changes-coming-on-june-24"&gt;Breaking changes coming on June 24&lt;/h2&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;December’s announcement&lt;/a&gt; for full details on the changes.)&lt;/p&gt;

&lt;p&gt;In January, we &lt;a href="/changes/2015-01-07-prepare-for-organization-permissions-changes/"&gt;announced a migration period&lt;/a&gt; allowing API consumers to opt in to these changes. If you haven’t already opted in to these changes, you still do so as described below. On June 24, these changes will become official parts of GitHub API v3. At that time, these changes will apply to all API consumers.&lt;/p&gt;

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

&lt;p&gt;During these final days of 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,2015-05-26:/changes/2015-05-26-repository-redirects-are-coming/</id>

<title type="html">Repository redirects are coming to API v3 in July</title>

<published>2015-05-26T00:00:00Z</published>

<updated>2015-05-26T00:00:00Z</updated>

<author>

<name>jasonrudolph</name>

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

</author>

<link rel="alternate" href="http://developer.github.com/changes/2015-05-26-repository-redirects-are-coming/" />

<content type="html">&lt;p&gt;Last month, we announced the &lt;a href="/changes/2015-04-17-preview-repository-redirects/"&gt;upcoming repository redirect behavior for the API&lt;/a&gt;, and we made it available for developers to preview. Starting &lt;strong&gt;July 21, 2015&lt;/strong&gt;, the API will automatically provide these redirects for all API consumers.&lt;/p&gt;

&lt;p&gt;To learn more about repository redirects and how they will benefit your applications, be sure to check out the &lt;a href="/changes/2015-04-17-preview-repository-redirects/"&gt;original announcement&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;To start enjoying repository redirects right away, just provide the following 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.quicksilver-preview+json

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

&lt;p&gt;Thanks to everyone that tried out this enhancement during the preview period.&lt;/p&gt;

&lt;p&gt;As always, if you have any questions, please &lt;a href="https://github.com/contact?form%5Bsubject%5D=API+Repository+Redirects"&gt;get in touch&lt;/a&gt;. We love hearing from you.&lt;/p&gt;

</content>

</entry>

<entry>

<id>tag:developer.github.com,2015-04-21:/changes/2015-04-21-organization-hooks-api-finalized/</id>

<title type="html">Organization Webhooks API finalized</title>

<published>2015-04-21T00:00:00Z</published>

<updated>2015-04-21T00:00:00Z</updated>

<author>

<name>pengwynn</name>

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

</author>

<link rel="alternate" href="http://developer.github.com/changes/2015-04-21-organization-hooks-api-finalized/" />

<content type="html">&lt;p&gt;After &lt;a href="/changes/2014-12-03-preview-the-new-organization-webhooks-api/"&gt;four months in preview release&lt;/a&gt;, the &lt;a href="/v3/orgs/hooks"&gt;Organization Webhooks API&lt;/a&gt; is now considered stable and ready for production use. &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;During the preview period, you needed to provide a custom media type in the &lt;code&gt;Accept&lt;/code&gt; header when using the Organization Webhooks API:&lt;/p&gt;

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

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

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

media type, though providing an explicit &lt;a href="/v3/media"&gt;media type&lt;/a&gt; is recommended:&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;If you have any questions or feedback on this API, please &lt;a href="https://github.com/contact?form%5Bsubject%5D=Organization+Webhooks"&gt;get in touch&lt;/a&gt;.&lt;/p&gt;

</content>

</entry>

<entry>

<id>tag:developer.github.com,2015-04-20:/changes/2015-04-20-authorizations-api-response-changes-are-now-in-effect/</id>

<title type="html">Authorizations API response changes are now in effect</title>

<published>2015-04-20T00:00:00Z</published>

<updated>2015-04-20T00:00:00Z</updated>

<author>

<name>ptoomey3</name>

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

</author>

<link rel="alternate" href="http://developer.github.com/changes/2015-04-20-authorizations-api-response-changes-are-now-in-effect/" />

<content type="html">&lt;p&gt;Two months ago, we

&lt;a href="/changes/2015-02-20-migration-period-removing-authorizations-token"&gt;announced the migration period&lt;/a&gt;

for several &lt;a href="/changes/2014-12-08-removing-authorizations-token/"&gt;API changes related to managing OAuth authorizations&lt;/a&gt;.

As promised, the migration period concluded today, and these changes are

now in effect for all requests.&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 updated Authorizations API during the migration 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.mirage-preview+json

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

&lt;p&gt;Now that the migration 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;As always, if you have any feedback, please don’t hesitate to

&lt;a href="https://github.com/contact?form%5Bsubject%5D=Removing+token+from+Authorizations+API"&gt;get in touch with us&lt;/a&gt;.&lt;/p&gt;

</content>

</entry>

<entry>

<id>tag:developer.github.com,2015-04-17:/changes/2015-04-17-preview-repository-redirects/</id>

<title type="html">Preview repository redirects</title>

<published>2015-04-17T00:00:00Z</published>

<updated>2015-04-17T00:00:00Z</updated>

<author>

<name>jasonrudolph</name>

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

</author>

<link rel="alternate" href="http://developer.github.com/changes/2015-04-17-preview-repository-redirects/" />

<content type="html">&lt;p&gt;From time to time, repository names change. If you make a GitHub API request using a repository’s old name in the URL, the API has historically responded with &lt;code&gt;404 Not Found&lt;/code&gt;. To help API clients gracefully handle renamed repositories, the API will soon begin &lt;a href="/v3/#http-redirects"&gt;redirecting&lt;/a&gt; to the repository’s new location.&lt;/p&gt;

&lt;p&gt;You can preview these redirects now. In the coming weeks, we’ll announce the timeline for enabling these redirects for everyone.&lt;/p&gt;

&lt;h2 id="how-can-i-try-out-the-redirects"&gt;How can I try out the redirects?&lt;/h2&gt;

&lt;p&gt;Starting today, developers can preview the redirect functionality for relocated repositories. To access this redirect functionality during the preview period, you’ll need to provide the following 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.quicksilver-preview+json

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

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

&lt;h2 id="when-will-the-redirects-occur"&gt;When will the redirects occur?&lt;/h2&gt;

&lt;p&gt;To understand when these redirects would take place, you’ll want to understand how to identify a repository’s location. Repositories are located using the combination of the owner’s name and the repository’s name. For example, the &lt;a href="https://github.com/twbs"&gt;@twbs&lt;/a&gt; organization owns the popular &lt;a href="https://github.com/twbs/bootstrap"&gt;bootstrap repository&lt;/a&gt;. We identify this repository as &lt;a href="https://github.com/twbs/bootstrap"&gt;twbs/bootstrap&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The repository’s location changes in the following scenarios:&lt;/p&gt;

&lt;ul&gt;

&lt;li&gt;When the owner changes the repository name.&lt;/li&gt;

&lt;li&gt;When the owner renames their user account or organization account.&lt;/li&gt;

&lt;li&gt;When the owner transfers the repository to a new owner.&lt;/li&gt;

&lt;/ul&gt;

&lt;p&gt;Continuing our &lt;a href="https://github.com/twbs/bootstrap"&gt;twbs/bootstrap&lt;/a&gt; example, this repository used to be owned by the &lt;a href="https://github.com/twitter"&gt;@twitter&lt;/a&gt; organization, and it was therefore located at &lt;a href="https://github.com/twitter/bootstrap"&gt;twitter/bootstrap&lt;/a&gt;. With repository redirects, you’ll be able to make an API request using the repository’s old location and receive &lt;a href="/v3/#http-redirects"&gt;either a &lt;code&gt;301&lt;/code&gt; or &lt;code&gt;307&lt;/code&gt; HTTP redirect&lt;/a&gt;, depending on the type of request being made. You can then follow the redirect to the new location.&lt;/p&gt;

&lt;h2 id="send-us-your-feedback"&gt;Send us your feedback&lt;/h2&gt;

&lt;p&gt;We hope you’ll take these redirects for a spin and &lt;a href="https://github.com/contact?form%5Bsubject%5D=API+Repository+Redirects"&gt;let us know what you think&lt;/a&gt;. Happy redirecting!&lt;/p&gt;

</content>

</entry>

<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;Repositories 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 memberships.&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;&lt;strong&gt;UPDATE (2015-06-10):&lt;/strong&gt; As &lt;a href="/changes/2015-06-10-breaking-changes-to-organization-permissions-coming-on-june-24/"&gt;announced on June 10&lt;/a&gt;, these changes will become an official part of GitHub API v3 on June 24. (This post originally announced that these changes would come to GitHub API v3 on February 24.)&lt;/p&gt;

&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 June 24&lt;/strong&gt; to account for these changes.&lt;/p&gt;

&lt;h2 id="breaking-changes-coming-on-june-24"&gt;Breaking changes coming on June 24&lt;/h2&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 June 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;h2 id="migration-period"&gt;Migration period&lt;/h2&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;