Repository navigation
Upgrade Weaviate to 1.39.13 - #321
Open
dudanogueira wants to merge 1 commit into
Open
dudanogueira wants to merge 1 commit into
dudanogueira wants to merge 1 commit into
Conversation
Weaviate 1.39.13 is built with Go 1.26.10, which rejects certificate chains containing the leaked eMudhra intermediates (CVE-2026-111943). Add a note to the packaged compose file that existing weaviatedata volumes must be upgraded one minor version at a time.
|
@dudanogueira is attempting to deploy a commit to the LLMStack Team on Vercel. A member of the Team first needs to authorize it. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the Weaviate image in both compose files from 1.25.7 to 1.39.13.
Why
Weaviate 1.39.13 is built with Go 1.26.10. That Go release makes crypto/x509 reject certificate chains that contain eight leaked eMudhra intermediate certificates (CVE-2026-111943, golang/go#82345). The only patched Weaviate releases are 1.40.2, 1.39.13 and 1.38.22; nothing older than 1.38 will get the fix.
What changed
llmstack/docker-compose.yml(used by thellmstackCLI):semitechnologies/weaviate:1.25.7->1.39.13, plus a short comment about upgrading existing data.docker/docker-compose.dev.yml: same bump.No env or module changes are needed. All current settings are still valid in 1.39, and the bundled
weaviate-client4.7.1 works against it.Upgrade impact
This crosses several minor versions. Weaviate supports upgrading one minor version at a time. Users with an existing
weaviatedatavolume should step through the latest patch of each minor (1.26.x, 1.27.x, ... 1.38.x) before 1.39.13. See https://docs.weaviate.io/deploy/migration. New installs are unaffected.How tested
llmstack/docker-compose.yml. Ran LLMStack's own Weaviate destination code with weaviate-client 4.7.1 against it:_create_weaviate_clientWeaviateVectorStorecreate_index (default schema), batch add, hybrid query, get_nodes, delete, delete_indexWeaviatevector store (create, add, batch add, get, delete)