Google has changed how it distributes certain source code by moving away from Git tags and instead offering access through Google Drive. This shift was highlighted by GrapheneOS in a post discussing the implications for developers and security researchers who rely on traditional version control methods.

The change affects how source code is retrieved, potentially impacting automated build systems and verification processes that depend on Git tag signatures. Developers may now need to download archives directly from Google Drive links rather than cloning repositories with tagged releases.

Hacker News users discussed various concerns about this approach, including reduced transparency and potential security risks. Some commenters noted that Google Drive distribution makes it harder to verify code integrity through established cryptographic means.

GrapheneOS specifically called attention to this change, emphasizing that it represents a departure from standard open source practices. The discussion generated significant interest with 403 points and 168 comments on the platform.