Dify 1.13.3

1.13.3

v1.13.3

Added 1
  • Add variable-reference support for model parameters in LLM, Question Classifier, and Variable Extractor nodes
Fixed 9
  • Fix StreamsBroadcastChannel replay and concurrency issues to keep frontend/backend event delivery stable
  • Fix pasted nodes retaining Loop/Iteration metadata
  • Prevent HumanInput nodes from being pasted into invalid containers
  • Restore prompt message transformation logic
  • Correct max_retries=0 handling for executor-driven HTTP Request execution
  • Preserve citation metadata in web responses
🚀 What's New in v1.13.3?

Our latest patch release, v1.13.3, focuses on stability and correctness across workflow execution, streaming, and knowledge retrieval. Here's a quick look at the most important updates:

🎬 New Features
  • Workflow Configuration: Added variable-reference support for model parameters in LLM, Question Classifier, and Variable Extractor nodes by @scdeng in #33082.
🛠️ Bug Fixes
  • Streaming Reliability: Fixed StreamsBroadcastChannel replay and concurrency issues to keep frontend/backend event delivery stable by @QuantumGhost in #34030 and #34061.
  • Workflow Editor Behavior: Fixed pasted nodes retaining Loop/Iteration metadata and prevented HumanInput nodes from being pasted into invalid containers by @majiayu000 and @hjlarry in #29983 and #34077.
  • Runtime Execution: Restored prompt message transformation logic and corrected max_retries=0 handling for executor-driven HTTP Request execution by @QuantumGhost, @fatelei, and @kurokobo in #33666, #33619, and #33688.
  • Knowledge Retrieval: Preserved citation metadata in web responses, fixed crashes when dataset icon metadata is missing, corrected hit-count query filtering, and restored indexed document chunk previews by @Theysua, @copilot-swe-agent, and @fatelei in #33778, #33907, #33757, and #33942.
🔧 Under the Hood
  • Patch Stability: This release prioritizes targeted fixes for workflow runtime behavior, real-time streaming, and knowledge base usability for teams upgrading from v1.13.2.
Upgrade Guide

[!IMPORTANT] The Sandbox image used by Dify v1.13.3 expects the following Python and Node.js paths. If you upgraded from an older Docker Compose deployment and already have docker/volumes/sandbox/conf/config.yaml, update it on the host machine:

python_path: /opt/python/bin/python3
nodejs_path: /usr/local/bin/node

Do not edit the file inside the sandbox container. The directory docker/volumes/sandbox/conf is mounted into the container as /conf, so host changes persist after container restarts.

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
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.3

  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
New Contributors

Full Changelog: https://github.com/langgenius/dify/compare/1.13.2...1.13.3

View original

Upgraded? How did it go?

Discussion