API v3, which has been operational for nearly a year, is set to fully replace its predecessors, API v1 and API v2, as they will be terminated on June 1st, 2012, marking a shift towards a unified codebase for enhanced reliability and security. This transition reflects a significant increase in API consumers and aligns with ambitious future plans, emphasizing documentation as a key component with the motto "it's not shipped if it's not documented." API v3 introduces versioning via a custom GitHub mime type and discontinues basic auth with tokens, instead offering OAuth tokens through the Authorizations API, which permits setting OAuth scopes per token and adding notes for functionality clarity. Users are encouraged to follow updates on the @githubapi Twitter account and the API documentation's Git repository, and to provide feedback if essential features from API v2 are missing.