This is a new hazard which maybe started inconveniencing AOSP builds a lot in the past six months, maybe Google don’t want to make it too easy for us.
The /e/OS cycle is roughly monthly but it does tend to lag Android by a significant period (/e/OS testing of a build cannot start till the relevant security updates are released).
The Release notes are found Releases · e / os / 🚀 Releases · GitLab and the link will point to the most recent, with “history” below.
The main answers to your questions and predicament will need some careful reading of https://source.android.com/docs/security/bulletin/. You can see that the cycle here is based on a monthly cycle but …
- around 1st for “security patch level vulnerability details”
- I was going to continue around 5th for “framework”, roughly what we had about ~ May to October.
However if you read for November we see mentioned 1st Nov : security patch level vulnerability details, then a section of FAQ and then what is new to me:
Version Date Notes
1.0 November 3, 2025 Bulletin Published
1.1 November 14, 2025 Bulletin updated
When /e/OS 3.3 comes out we can expect a “November 2025 AOSP Security patch”.
To be more specific in what I guess is your situation. If you unlocked your Fairphone Android when Android SPL was 5-October-2025 then /e/OS 3.3 with Android SPL 1-November-2025 (or any other date forward of this) will be safe to lock.