robo end of life dates — full support timeline
3 of 5 tracked robo releases have already reached end of life. The dates below are published support dates, not estimates.
Version support timeline
| Release | Released | End of life | Latest | Status |
|---|---|---|---|---|
| 5 | 2024-04-17 | not announced | 5.1.1 | supported |
| 4 | 2022-04-21 | not announced | 4.0.6 | supported |
| 3 | 2021-02-21 | ended | 3.0.12 | ended |
| 2 | 2019-10-29 | ended | 2.2.2 | ended |
| 1 | 2016-10-13 | ended | 1.5.0 | ended |
Who is affected
Anyone running an unsupported robo release. After end of life a version stops receiving security patches, which typically becomes an audit or compliance finding before it becomes an outage. Upgrading to a supported release is the migration path; the table above shows which releases still qualify.
Source
These dates are maintained by endoflife.date/robo, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next robo deadline
You are reading this because a robo release is losing support. The next one will arrive the same way — quietly, months before an auditor finds it. A free weekly email lists every robo and related deadline as it is announced, with exact dates and primary sources.
Watch robo deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.