GrumPHP — support and end-of-life dates
GrumPHP 2 is the current release, released 2023-06-18, with no end-of-life date published upstream.
- 2 of its 3 tracked cycles have passed their EOL date (earliest tracked cycle 0)
Direct answer
GrumPHP 2 has no published end-of-life date. Data as of 2026-11-18.
All tracked cycles
| Cycle | Released | Active support ends | End of life (EOL) | Latest | Status |
|---|---|---|---|---|---|
| 2 | 2023-06-18 | — | not announced | 2.26.0 | No EOL date |
| 1 | 2020-09-25 | — | — | 1.16.0 | End of life |
| 0 | 2015-03-18 | — | — | 0.22.0 | End of life |
Upgrade path stated in the data
- No successor is stated in the upstream data for this product.
This is not a recommendation from DeprecateWatch. It repeats what the upstream source states, plus the newest cycle that is still inside its published support window.
Questions this page answers
Is GrumPHP 2 end of life?
No. GrumPHP 2 has no published end-of-life date in the source data.
How many GrumPHP versions are already end of life?
2 of the 3 cycles tracked here have passed their EOL date as of 2026-11-18.
Other Frameworks & libraries with upcoming deadlines
- Angular — next EOL 2026-11-28 (20)
- Ansible-core — next EOL 2026-11-30 (2.19)
- Ember — next EOL 2026-12-08 (6.8)
- NumPy — next EOL 2026-12-09 (2.2)
- Oracle APEX — next EOL 2026-12-31 (24.1)
- ROS 2 — next EOL 2026-12-31 (kilted)
- Spring Boot — next EOL 2026-12-31 (4.0)
- Spring Security — next EOL 2026-12-31 (7.0)
Source for the cycle table: endoflife.date/grumphp
read through the endoflife.date API on 2026-11-18. Machine-readable copy:
/api/eol.json (product key grumphp).