Repository navigation
Bump bundled Weaviate to 1.39.13 to align with Dify 1.18.0 - #462
Merged
Merged
Conversation
- Update Chart.yaml/Chart.lock dependency and values.yaml image tag - Add storage.name PVC prefix and RBAC config options from upstream chart
BorisPolonsky
added a commit
that referenced
this pull request
Oct 30, 2026
## Summary - Upgrade default image tags (`api`, `web`, `agentBackend`, `localSandbox`) from 1.17.0 to 1.18.0 - Dify 1.18.0 requires an authenticated local sandbox, so: - `shellctlAuthToken` now defaults to `global.internalApiKey` when unset — consistent with other auth values (e.g. `agentBackend.auth.apiToken`, `sandbox.auth.apiKey`) - Local sandbox now enforces the auth token via an explicit `shellctl serve --require-auth-token` command, configurable through the new `localSandbox.command` value - `global.internalApiKey` defaults to a non-empty placeholder so the fallback yields a valid shared token on fresh installs (set your own value in production) - Sync `values.schema.json` for the new `localSandbox.command` value ## Upgrade note - 1.18.0 DB migrations are not automatically reversible — back up your database before running `helm upgrade` - **Bundled Weaviate 1.27 → 1.39.13 (#462) requires a manual stepped migration (no minor-skipping, PVCs renamed)** — follow the [Weaviate server migration path](https://docs.dify.ai/en/self-host/deploy/troubleshooting/weaviate-server-migration-path) before upgrading
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.
Why
Dify 1.17.1 moved its bundled Weaviate from 1.27 to the 1.39 series
(langgenius/dify#38214), and 1.18.0 pinned 1.39.13 — where Weaviate's
bug and security backports land. This chart tracks that move.
Changes
values.yaml:storage.name: weaviate-data— PVC names are now prefixed(
weaviate-data-weaviate-0), replacingstorage.fullnameOverrideauthorization.rbac(disabled by default)skip_client_id_check,namespace_claim,global_principal_claimUpgrade notes
Weaviate does not support skipping minor versions — existing 1.27
volumes must be stepped through every minor with graceful stops before
reaching 1.39. Fresh installs and external Weaviate deployments are
unaffected.