← ← Back to all products
Renovate CLI
Active
OtherLatest Version: 43.242.0Latest Release: Jun 24, 2026
Support summary
Renovate CLI currently has supported cycles. Track the next EOL date and validate upgrades before your change window.
What do EOL and support statuses mean?Next EOL
No announced EOL date is currently listed.
Supported cycles
1
0 lts
Versions
4
Latest Version
43.242.0
Active Support
1
EOL
3
Lifecycle Timeline
Today ↓
43
43
42
42
41
41
40
40
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 43 | Jan 29, 2026 | Yes | No | 43.242.0 | No | Active |
| 42 | Aug 14, 2025 | No | Jan 29, 2026 | 42.99.0 | No | EOL |
| 41 | Apr 30, 2025 | No | Aug 14, 2025 | 41.173.1 | No | EOL |
| 40 | Feb 22, 2025 | No | Aug 14, 2025 | 40.62.1 | No | EOL |
Data sources
Sources
Frequently Asked Questions
Which versions of Renovate CLI have reached end of life?
The following Renovate CLI versions have reached end of life and no longer receive security updates: 42, 41, 40. It is recommended to upgrade to a supported version.
Is it safe to continue using Renovate CLI 42?
Renovate CLI 42 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Renovate CLI?
The latest version of Renovate CLI is 43.242.0, released in the 43 release cycle.
How many versions of Renovate CLI are currently supported?
Renovate CLI currently has 1 actively supported version(s): 43.
When does Renovate CLI 43 reach end of life?
Renovate CLI 43 does not have a specific end-of-life date announced yet.
What should I do when Renovate CLI reaches end of life?
When a Renovate CLI version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.