You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/changes/2015-01-07-prepare-for-organization-permissions-changes.md
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,9 +5,11 @@ created_at: 2015-01-07
5
5
author_name: jakeboxer
6
6
---
7
7
8
-
Last month, we [released a preview][org-permissions-preview] 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 **update your code before February 24** to account for these changes.
8
+
**UPDATE (2015-06-10):** As [announced on June 10][2015-06-10-update], 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.)
9
9
10
-
### Breaking changes coming on February 24
10
+
Last month, we [released a preview][org-permissions-preview] 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 **update your code before June 24** to account for these changes.
11
+
12
+
## Breaking changes coming on June 24
11
13
12
14
If your application uses any of the following APIs, then you are affected by this change:
13
15
@@ -18,9 +20,9 @@ If your application uses any of the following APIs, then you are affected by thi
18
20
19
21
If your application uses these APIs, we urge you to update your application as soon as possible. (Read [last month's announcement][org-permissions-preview] for more details on the changes.)
20
22
21
-
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.
23
+
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.
22
24
23
-
###Migration period
25
+
## Migration period
24
26
25
27
During the migration period, you can opt-in to these changes using the following custom media type in the `Accept` header:
26
28
@@ -33,3 +35,4 @@ We want to make these updates as smooth as possible for everyone, and we hope th
title: Breaking changes to organization permissions coming on June 24
4
+
created_at: 2015-06-10
5
+
author_name: jakeboxer
6
+
---
7
+
8
+
Back in January, we [encouraged developers to update their applications][org-permissions-finalization] to prepare for [upcoming API changes][org-permissions-preview] related to managing organization members and repositories. In order to support the upcoming [improvements to organization permissions][direct-org-membership-blog-post], these changes will become official parts of GitHub API v3 on **June 24**.
9
+
10
+
If your application relies on any of the affected functionality (described below), be sure to **update your code before June 24** to account for these changes.
11
+
12
+
## Breaking changes coming on June 24
13
+
14
+
If your application uses any of the following APIs, then you are affected by this change:
15
+
16
+
- APIs for managing your organization's admins through the Owners team
17
+
- The [List your repositories][list-your-repos] API
18
+
- The [List your organizations][list-your-organizations] API
19
+
- The [List user organizations][list-user-organizations] API
20
+
21
+
If your application uses these APIs, we urge you to update your application as soon as possible. (Read [December's announcement][org-permissions-preview] for full details on the changes.)
22
+
23
+
In January, we [announced a migration period][org-permissions-finalization] 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.
24
+
25
+
## Migration period
26
+
27
+
During these final days of the migration period, you can opt in to these changes using the following custom media type in the `Accept` header:
28
+
29
+
application/vnd.github.moondragon+json
30
+
31
+
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 [get in touch with us][contact]!
Copy file name to clipboardExpand all lines: content/v3/orgs.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ With the new Organization Permissions API (described below), this method will on
19
19
20
20
<divclass="alert">
21
21
<p>
22
-
We're currently offering a migration period allowing applications to opt in to the Organization Permissions API. This functionality will <a href="/changes/2015-02-24-more-time-to-prepare-for-the-breaking-changes-to-organization-permissions/">soon</a> apply to all API consumers. Please see the <a href="/changes/2015-01-07-prepare-for-organization-permissions-changes/">blog post</a> for full details.
22
+
We're currently offering a migration period allowing applications to opt in to the Organization Permissions API. This functionality will apply to all API consumers <a href="/changes/2015-06-10-breaking-changes-to-organization-permissions-coming-on-june-24/">beginning June 24, 2015</a>. Please see the <a href="/changes/2015-01-07-prepare-for-organization-permissions-changes/">blog post</a> for full details.
23
23
</p>
24
24
25
25
<p>
@@ -45,7 +45,7 @@ With the new Organization Permissions API (described below), this method will on
45
45
46
46
<divclass="alert">
47
47
<p>
48
-
We're currently offering a migration period allowing applications to opt in to the Organization Permissions API. This functionality will <a href="/changes/2015-02-24-more-time-to-prepare-for-the-breaking-changes-to-organization-permissions/">soon</a> apply to all API consumers. Please see the <a href="/changes/2015-01-07-prepare-for-organization-permissions-changes/">blog post</a> for full details.
48
+
We're currently offering a migration period allowing applications to opt in to the Organization Permissions API. This functionality will apply to all API consumers <a href="/changes/2015-06-10-breaking-changes-to-organization-permissions-coming-on-june-24/">beginning June 24, 2015</a>. Please see the <a href="/changes/2015-01-07-prepare-for-organization-permissions-changes/">blog post</a> for full details.
Copy file name to clipboardExpand all lines: content/v3/orgs/members.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ Name | Type | Description
27
27
28
28
<divclass="alert">
29
29
<p>
30
-
We're currently offering a migration period allowing applications to opt in to the Organization Permissions API. This functionality will <a href="/changes/2015-02-24-more-time-to-prepare-for-the-breaking-changes-to-organization-permissions/">soon</a> apply to all API consumers. Please see the <a href="/changes/2015-01-07-prepare-for-organization-permissions-changes/">blog post</a> for full details.
30
+
We're currently offering a migration period allowing applications to opt in to the Organization Permissions API. This functionality will apply to all API consumers <a href="/changes/2015-06-10-breaking-changes-to-organization-permissions-coming-on-june-24/">beginning June 24, 2015</a>. Please see the <a href="/changes/2015-01-07-prepare-for-organization-permissions-changes/">blog post</a> for full details.
Copy file name to clipboardExpand all lines: content/v3/repos.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ list the authenticated user's organization-owned repositories.
24
24
25
25
<divclass="alert">
26
26
<p>
27
-
We're currently offering a migration period allowing applications to opt in to the Organization Permissions API. This functionality will <a href="/changes/2015-02-24-more-time-to-prepare-for-the-breaking-changes-to-organization-permissions/">soon</a> apply to all API consumers. Please see the <a href="/changes/2015-01-07-prepare-for-organization-permissions-changes/">blog post</a> for full details.
27
+
We're currently offering a migration period allowing applications to opt in to the Organization Permissions API. This functionality will apply to all API consumers <a href="/changes/2015-06-10-breaking-changes-to-organization-permissions-coming-on-june-24/">beginning June 24, 2015</a>. Please see the <a href="/changes/2015-01-07-prepare-for-organization-permissions-changes/">blog post</a> for full details.
0 commit comments