EOL.Wiki EOL.Wiki
← ← Back to all products

Yocto

Active
Operating Systems Latest Version: 5.3 Latest Release: Dec 15, 2025

The Yocto Project provides tools and templates for creating custom Linux distributions for embedded systems.

Versions

14

Latest Version

5.3

Active Support

3

EOL

11

Lifecycle Timeline

Today
5.3
5.3
5.2
5.2
5.1
5.1
5.0
5.0
4.3
4.3
4.2
4.2
4.1
4.1
4.0
4.0
3.4
3.4
3.3
3.3
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
5.3Dec 15, 2025-Jun 15, 20265.3No
Active
5.2May 7, 2025-Dec 7, 20255.2.4No
EOL
5.1Oct 16, 2024-May 16, 20255.1.4No
EOL
5.0Apr 29, 2024-Apr 30, 20285.0.15
Yes
Active
4.3Nov 9, 2023-Jun 9, 20244.3.4No
EOL
4.2May 3, 2023-Nov 5, 20234.2.4No
EOL
4.1Oct 23, 2022-May 27, 20234.1.4No
EOL
4.0Apr 25, 2022-Apr 27, 20264.0.32
Yes
Active
3.4Oct 25, 2021-May 1, 20223.4.4No
EOL
3.3Apr 19, 2021-Apr 20, 20223.3.6No
EOL
3.2Nov 3, 2020-May 1, 20213.2.4No
EOL
3.1Apr 21, 2020-Apr 30, 20243.1.33
Yes
EOL
3.0Oct 22, 2019-Aug 1, 20203.0.4No
EOL
2.7May 1, 2019-Jun 1, 20202.7.4No
EOL

Frequently Asked Questions

Which versions of Yocto have reached end of life?
The following Yocto versions have reached end of life and no longer receive security updates: 5.2, 5.1, 4.3, 4.2, 4.1, 3.4, 3.3, 3.2 (and 3 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Yocto 5.2?
Yocto 5.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 Yocto?
The latest version of Yocto is 5.3, released in the 5.3 release cycle.
How many versions of Yocto are currently supported?
Yocto currently has 3 actively supported version(s): 5.3, 5.0, 4.0.
When does Yocto 5.3 reach end of life?
Yocto 5.3 is scheduled to reach end of life on Jun 15, 2026.
What should I do when Yocto reaches end of life?
When a Yocto 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.