v1.13.2

[QuantumGhost]

This patch release fixes several critical regressions and stability issues introduced in v1.13.1, including:

• a severe regression in prompt message transformation that caused multiple LLM-plugin invocation failures across
  LLM-related nodes, including LLM and Question Classifier.
• Knowledge Retrieval node execution failures caused by incompatible enum values
• improper Weaviate client cleanup

---

Upgrade Guide

Important

If you use custom CELERY_QUEUES, make sure workflow_based_app_execution is included.
If ENABLE_API_TOKEN_LAST_USED_UPDATE_TASK=true, also include api_token.

For background and details, see ⚠️ Important Upgrade Note and 🔧 Operational Note above.

Docker Compose Deployments

1. Back up your customized docker-compose YAML file (optional)

   cd docker
   cp docker-compose.yaml docker-compose.yaml.$(date +%s).bak

2. Get the latest code from the main branch

   git checkout main
   git pull origin main

3. Stop the service. Please execute in the docker directory

   docker compose down

4. Back up data

   tar -cvf volumes-$(date +%s).tgz volumes

5. Upgrade services

   docker compose up -d

Note

If you encounter errors like below

2025/11/26 11:37:57 /app/internal/db/pg/pg.go:30
[error] failed to initialize database, got error failed to connect to `host=db_postgres user=postgres database=dify_plugin`: hostname resolving error (lookup db_postgres on 127.0.0.11:53: server misbehaving)

2025/11/26 11:37:57 /app/internal/db/pg/pg.go:34
[error] failed to initialize database, got error failed to connect to `host=db_postgres user=postgres database=postgres`: hostname > resolving error (lookup db_postgres on 127.0.0.11:53: server misbehaving)
2025/11/26 11:37:57 init.go:99: [PANIC]failed to init dify plugin db: failed to connect to `host=db_postgres user=postgres database=postgres`: hostname resolving error (lookup db_postgres on 127.0.0.11:53: server misbehaving)
panic: [PANIC]failed to init dify plugin db: failed to connect to `host=db_postgres user=postgres database=postgres`: hostname resolving error (lookup db_postgres on 127.0.0.11:53: server misbehaving)

Please use the following command instead. For details, please read this #28706

docker compose --profile postgresql up -d

Source Code Deployments

1. Stop the API server, Worker, and Web frontend Server.

2. Get the latest code from the release branch:

   git checkout 1.13.2

3. Update Python dependencies:

   cd api
   uv sync

4. Then, let's run the migration script:

   uv run flask db upgrade

5. Finally, run the API server, Worker, and Web frontend Server again.

---

What's Changed

• chore: bump version to 1.13.2 (chore: bump version to 1.13.2 #33681) by @QuantumGhost
• fix: fix max_retries is hardcode (fix: fix max_retries is hardcode #33619) by @wangxiaolei
• fix(api): Preserving the content transform logic in fetch_prompt_messages (fix(api): Preserving the content transform logic in fetch_prompt_messages #33666) by @QuantumGhost
• feat: remove weaviate client del method (feat: remove weaviate client __del__ method #33593) by @wangxiaolei
• fix(api): make CreatorUserRole accept both end-user and end_user (chore: compatiable end-user and end_user #33638) by @wangxiaolei

Full Changelog: 1.13.1...1.13.2

---

This discussion was created from the release v1.13.2.