upgrad from version 1.0.0 to version 1.9.2

[gongchangping]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

Content

Has anyone upgraded from version 1.0.0 to version 1.9.2? I directly overwritten all the files in version 1.9.2 with the files in version 1.0.0 that I am currently using, and it can be used directly after startup.
I followed the steps I took to upgrade from 0.15.3 to 1.0.0 and entered the docker-api-1 container (docker exec it docker-api-1 bash), executing the poetry run Flask extract plugins -- workers=20
poetry run flask install-plugins --workers=2
poetry run flask db upgrade
poetry run flask migrate-data-for-plugin
When prompted: bash: poetry: command not found
However, although I was unable to execute the above command, I entered the system and found that all of my previous data was there. Has the upgrade been completed in this situation? Do I complete the upgrade by directly overwriting all files from version 1.9.2 with files from version 1.0.0 that I am currently using? Has anyone told me

[dosubot[bot]]

Overwriting files alone is not enough to fully upgrade Dify from 1.0.0 to 1.9.2. You must run database and plugin migration commands to update the schema and plugin data—otherwise, you risk incomplete upgrades or subtle issues, even if your data appears present in the UI.

For Dify 1.3.0 and above, use uv run flask ... instead of poetry run flask ... inside the API container. The required commands are:

docker compose exec api uv run flask db upgrade
docker compose exec api uv run flask extract-plugins --workers=20
docker compose exec api uv run flask install-plugins --workers=2
docker compose exec api uv run flask migrate-data-for-plugin

If you’re still on a version where only poetry is available and it’s missing from the container, you’ll need to either temporarily install poetry inside the container or rebuild the image with poetry included to run the migration commands.

After running these, restart all services and check the UI and logs for errors or missing features. Always back up your database, Redis, vector DB, and persistent storage before starting the upgrade. For more details and troubleshooting, see the official migration guide and community upgrade discussions.

Simply overwriting files without running these migration commands is not sufficient for a complete upgrade, especially for major version jumps that involve database schema and plugin changes (source).

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}