Organizations on github.com with an enterprise plan can now create 5 custom repository roles, an increase from the previous limit of 3. This increase will also appear in GitHub Enterprise Server 3.9.
For more information about creating and assigning custom roles for repositories, see "About custom repository roles".
You can now create access tokens with limited scope using the new granular access tokens functionality in npm. With granular access tokens, you can:
Tokens with least privileges protects your npm packages from accidental or malicious misuse of your token. These tokens also allow you to manage your npm org and teams from a CI/CD pipeline. Granular access tokens are specifically built for automation and do not require 2FA. We recommend using granular access tokens with least privileges while you automate publishing and org management activities.
Enterprise owners can join organizations in their enterprise via the enterprise account Organizations page: https://github.com/enterprises/<enterprise> as either a member or an admin. This feature has graduated from beta to general availability.
To learn more, please read our article about managing your role within an organization your enterprise owns.
Enterprise owners can now remove enterprise members from their GitHub Enterprise via the People view within their enterprise account: https://github.com/enterprises/<enterprise>/people. This feature has graduated from beta to general availability.
To learn more, read about removing a member from your GitHub Enterprise.
Enterprises that use Enterprise Managed Users (EMUs) to authenticate their accounts via Azure Active Directory can now use Azure AD location-based Conditional Access policies to protect the use of PATs and SSH keys. This requires the use of a new OpenID Connect-based application rather than a SAML integration. To learn more, read about enforcing Azure AD Conditional Access for PATs and SSH keys.
Note: this feature is currently in public beta for new and existing Azure AD EMU enterprises.
For more information:
Enterprise owners can now prevent organization owners from inviting outside collaborators to repositories in their enterprise. The "Repository outside collaborators" policy includes an additional option, "Enterprise admins only", which restricts the ability to invite outside collaborators only to users with admin permissions to the enterprise. For more info, see "Enforcing a policy for inviting outside collaborators to repositories".
Enterprise owners can now access reports about dormant users on GitHub Enterprise Cloud. To learn more, read about managing dormant users.
Note: this feature is currently in beta.
GitHub Enterprise owners can now remove enterprise members from their GitHub Enterprise via the People view within their enterprise account: https://github.com/enterprises/<enterprise>/people.
To learn more, read about removing a member from your GitHub Enterprise.
Enterprise owners can now join organizations within their enterprise via the enterprise account Organizations page: https://github.com/enterprises/<enterprise>.
To learn more, please read our article about managing your role within an organization your enterprise owns.
