Version jumps in self-hosted Dify that need more than pulling new images: the move to the plugin architecture in 1.0 and the Weaviate client change in 1.9.2.
Moving an older Community Edition onto the plugin architecture: backing up, extracting the models and tools in use, installing them as plugins with marketplace access, running database migrations, and planning for air-gapped installs.
What self-hosted Dify operators with their own Weaviate must do from Dify 1.9.2 onward: checking the Weaviate server version, stepping through minor server releases, the gRPC port change, and the compatibility matrix by Dify version.
The repeatable upgrade runbook for a Compose deployment: backing up volumes and env files, checking release notes, reapplying customized docker-compose.yaml changes, diffing .env.example, pulling images and running database migrations.
Upgrading a deployment that uses the bundled Weaviate to Dify 1.17.1: why the server must step from 1.27.0 through every minor release to 1.39.2, backing up the volume, stopping api and worker services, and verifying object counts at each rung.
Bringing an older Dify instance current when model providers stop working: legacy model type values, the data migration that now runs inside flask db upgrade, and testing provider credentials after the jump.
Upgrading Dify Enterprise on Kubernetes: matching chart and app versions, backing up PostgreSQL before helm upgrade, rollback with a database restore, and checking new values for plugin and sandbox components.
Upgrading the Dify Premium AMI on EC2: what the upgrade overwrites and keeps, backing up .env, envs and volumes, syncing the new docker directory, and restarting with the override file.
Controlling how plugins change under a running deployment: per-category auto-update (off, patch only, latest), the 15-minute marketplace upgrade check, pinning versions in regulated environments, and testing plugin upgrades before production.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.