Yesterday (2025-02-03), we released an early update based on the Android Security Bulletin backports of High/Critical severity vulnerabilities to older Android Open Source Project releases. The actual monthly AOSP and Pixel update was published today and we're building that now.

They do things based on the time in California (PST) and it takes many hours for AOSP tags to get pushed. We use UTC for our build timestamps and version numbers so the release we're building now is called 2025020500 even though it's still February 4th where we're building it.

Our releases after the monthly updates are built on the same day they release it. It takes them so long to push the code that by the time we get to start building, it's already the next day in UTC. Would be great if they pushed in parallel so we could start 6+ hours earlier...

They seem to push the Git tags one by one to multiple copies of each repository. The massive amount of time this takes could be a factor in why they've started releasing the monthly update the day after the security backports. Strange way of doing things and wastes our resources.