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

SUSE Linux Micro

Active
Operating Systems Latest Version: 6.2 Latest Release: N/A

SUSE Linux Micro is an ultra-lightweight, immutable OS for edge computing and containerized workloads.

Versions

9

Latest Version

6.2

Active Support

6

EOL

3

Lifecycle Timeline

Today
6.2
6.2
6.1
6.1
6.0
6.0
5.5
5.5
5.4
5.4
5.3
5.3
5.2
5.2
5.1
5.1
5.0
5.0
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
6.2Nov 4, 2025YesNov 30, 20296.2No
Active
6.1Nov 26, 2024YesNov 30, 20286.1No
Active
6.0Jun 6, 2024YesJun 30, 20286.0No
Active
5.5Oct 12, 2023YesOct 31, 20275.5No
Active
5.4Apr 20, 2023YesApr 30, 20275.4No
Active
5.3Oct 25, 2022YesOct 30, 20265.3No
Active
5.2Apr 14, 2022NoApr 30, 20265.2No
EOL
5.1Oct 26, 2021NoOct 31, 20255.1No
EOL
5.0Mar 30, 2021NoMar 31, 20225.0No
EOL

Frequently Asked Questions

Which versions of SUSE Linux Micro have reached end of life?
The following SUSE Linux Micro versions have reached end of life and no longer receive security updates: 5.2, 5.1, 5.0. It is recommended to upgrade to a supported version.
Is it safe to continue using SUSE Linux Micro 5.2?
SUSE Linux Micro 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 SUSE Linux Micro?
The latest version of SUSE Linux Micro is 6.2, released in the 6.2 release cycle.
How many versions of SUSE Linux Micro are currently supported?
SUSE Linux Micro currently has 6 actively supported version(s): 6.2, 6.1, 6.0, 5.5, 5.4, 5.3.
When does SUSE Linux Micro 6.2 reach end of life?
SUSE Linux Micro 6.2 is scheduled to reach end of life on Nov 30, 2029.
What should I do when SUSE Linux Micro reaches end of life?
When a SUSE Linux Micro 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.