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

Weaviate

Active
Databases Latest Version: 1.38.0 Latest Release: Jun 5, 2026

Weaviate is an open-source, AI-native vector database for building semantic search and generative AI applications.

Versions

12

Latest Version

1.38.0

Active Support

3

EOL

9

Lifecycle Timeline

Today
1.38
1.38
1.37
1.37
1.36
1.36
1.35
1.35
1.34
1.34
1.33
1.33
1.32
1.32
1.31
1.31
1.30
1.30
1.29
1.29
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
1.38Jun 5, 2026YesNo1.38.0No
Active
1.37Apr 16, 2026YesNo1.37.7No
Active
1.36Feb 24, 2026YesNo1.36.17No
Active
1.35Dec 18, 2025NoYes1.35.23No
EOL
1.34Nov 5, 2025NoYes1.34.20No
EOL
1.33Sep 25, 2025NoYes1.33.18No
EOL
1.32Jul 15, 2025NoYes1.32.27No
EOL
1.31May 30, 2025NoYes1.31.22No
EOL
1.30Apr 3, 2025NoYes1.30.23No
EOL
1.29Feb 17, 2025NoYes1.29.11No
EOL
1.28Dec 11, 2024NoYes1.28.16No
EOL
1.27Oct 16, 2024NoYes1.27.27No
EOL

Frequently Asked Questions

Which versions of Weaviate have reached end of life?
The following Weaviate versions have reached end of life and no longer receive security updates: 1.35, 1.34, 1.33, 1.32, 1.31, 1.30, 1.29, 1.28 (and 1 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Weaviate 1.35?
Weaviate 1.35 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 Weaviate?
The latest version of Weaviate is 1.38.0, released in the 1.38 release cycle.
How many versions of Weaviate are currently supported?
Weaviate currently has 3 actively supported version(s): 1.38, 1.37, 1.36.
When does Weaviate 1.38 reach end of life?
Weaviate 1.38 does not have a specific end-of-life date announced yet.
What should I do when Weaviate reaches end of life?
When a Weaviate 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.