← ← Back to all products
Jekyll
Active
Tools & MonitoringLatest Version: 4.4.1Latest Release: Jan 29, 2025
Jekyll is a static site generator that transforms plain text into static websites and blogs.
Support summary
Jekyll 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
2
0 lts
Versions
5
Latest Version
4.4.1
Active Support
2
EOL
3
Lifecycle Timeline
Today ↓
4
4
3
3
2
2
1
1
0
0
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 4 | Aug 20, 2019 | Yes | No | 4.4.1 | No | Active |
| 3 | Oct 26, 2015 | No | No | 3.10.0 | No | Active |
| 2 | May 6, 2014 | No | Oct 27, 2015 | 2.5.3 | No | EOL |
| 1 | May 6, 2013 | No | May 7, 2014 | 1.5.1 | No | EOL |
| 0 | Oct 19, 2008 | No | May 7, 2014 | 0.9.0 | No | EOL |
Data sources
Sources
Frequently Asked Questions
Which versions of Jekyll have reached end of life?
The following Jekyll versions have reached end of life and no longer receive security updates: 2, 1, 0. It is recommended to upgrade to a supported version.
Is it safe to continue using Jekyll 2?
Jekyll 2 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 Jekyll?
The latest version of Jekyll is 4.4.1, released in the 4 release cycle.
How many versions of Jekyll are currently supported?
Jekyll currently has 2 actively supported version(s): 4, 3.
When does Jekyll 4 reach end of life?
Jekyll 4 does not have a specific end-of-life date announced yet.
What should I do when Jekyll reaches end of life?
When a Jekyll 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.