Checked 20 October 2026 Self hosted

Dify 1.17.1: Check Weaviate Before You Update

Dify 1.17.1 is the latest official release. Existing installations that use the bundled Weaviate database need a staged Weaviate migration before the normal Dify update. A blind pull and restart can damage vector search.

The release specific warning

The bundled Weaviate version moves from 1.27.0 to 1.39.2. Dify states that skipping the intermediate minor versions is unsupported for an existing data volume. This warning applies to existing bundled Weaviate deployments. It does not apply to fresh installations, external Weaviate servers or other vector stores.

Open the official Weaviate migration runbook

Current release facts

  • Version: 1.17.1
  • Published: 10 September 2026
  • Database: the release includes three migrations applied by flask db upgrade.
  • Important boundary: one model type migration is intentionally not reversible, so the official release note says to back up the database first.
  • Knowledge base API keys: new keys can be limited to selected knowledge bases. Existing keys retain their previous workspace scope after the update.

These details come from the official release note, not from an assumed release schedule. Always check the release page again before updating because a newer tag may have been published after this page was checked.

Read the official Dify 1.17.1 release note

Choose the correct path

  1. Check the VECTOR_STORE value in your Dify Docker environment.
  2. If you have an existing bundled Weaviate volume, stop and complete the official staged migration first.
  3. Back up the database, Docker volumes and any locally modified configuration.
  4. Read the release note for environment variable and database migration changes.
  5. Use the versioned 1.17.1 tag instead of assuming that the current main branch is the release you intended to install.

Official Docker Compose sequence

After the Weaviate migration, if it applies, the 1.17.1 release note gives this Docker Compose sequence: 

cd docker
docker compose down
git fetch --tags
git checkout 1.17.1
docker compose pull
docker compose up -d

Do not turn this into a universal one line update command. The safe path depends on the vector store, the version you are upgrading from and whether the installation has local configuration changes.

What to verify after the update

  • All expected containers are healthy.
  • Existing model providers still load and can complete a basic request.
  • A known knowledge base query still returns the expected document.
  • A representative published workflow still runs from start to finish.
  • Newly scoped knowledge base API keys cannot access an unselected knowledge base.

If a separate staging host would reduce production risk, compare the deployment options in our Dify hosting comparison. The comparison links to official provider documentation and labels commercial links.