Dify 1.17.1 needs a manual Weaviate upgrade path

Dify's 1.17.1 release bumps the bundled Weaviate vector database from 1.27.0 to 1.39.2, twelve minor versions in one jump. The release notes say skipping minor versions during a Weaviate upgrade isn't supported. Run docker compose pull and restart the way you normally would, and you walk straight past every one of those twelve steps.

That matters because the failure mode isn't a crash. Vector search degrades or breaks, and nothing in the logs points back to the version jump. Anyone self-hosting Dify needs to stage the Weaviate upgrade manually, version by version, before touching this release.

The same release also fixes five extraction bugs, and these are the ones I'd worry about more. CSV imports ran cells through pandas type inference, so a value like 00123 silently became 123.0 and empty cells turned into the literal string nan, sitting in your index as if it were real data. Notion imports emitted one Markdown table column per rich-text segment instead of per actual column, scrambling table structure. Rich text got truncated at the first formatting change, cutting off content mid-document with no error.

None of that gets fixed retroactively. Upgrading to 1.17.1 patches the extraction logic going forward, but anything already indexed under the old bugs stays corrupted until you re-import it. If you've been running Dify against CSV or Notion sources, that means finding and re-ingesting the affected documents yourself. There's no migration script mentioned, and the release notes don't say how to identify which documents were hit, so a manual audit of your source data against what's indexed is the only way to know.