GitHub public repositories begin identity checks: bot traffic surges, normal CI suffers as well.

Beating AI News Flash: On October 19, GitHub announced that it will temporarily require authentication for HTTPS download requests from certain public repositories. Once the system detects abnormal traffic, code that could originally be cloned and fetched without logging in may suddenly require a Token. CI builds and automated installation scripts that rely on anonymous downloads may also be interrupted as a result.

Similar issues already appeared in September. On September 2, developers reported in the GitHub community that CI servers repeatedly received `401` errors when pulling the public MariaDB repository, and even submodule updates could not be completed. Developers of the game server management tool AMP also said that a large number of users' installation processes were affected, and the team had to consider urgently modifying the program.

GitHub explained at the time that the platform is facing increasing bot traffic, and normal development requests may also be misjudged. This announcement further clarifies the scope of application of the temporary authentication measures.

GitHub recommends that developers configure authentication for automated tasks and avoid relying on anonymous HTTPS pulls. Authenticated HTTPS and SSH operations are not affected by this restriction.