Traceary

Catalog / Dify

1.11.3

v1.11.3

8 months agosecurityaddedfixedOriginal notes

🚀 What's New in v1.11.3?

Our latest release, v1.11.3, brings to you a slew of bug fixes and features focused on performance, functionality, and user experience. Here's a look at what's changed:

🎬 New Features

  • MCP Tool Enhancements: Added support for embeddedResource and made MCP tools display directly for quicker access by @IthacaDream and @fatelei in #30261 and #30019.
  • Batch Operations: Introduced re-index operation in document batch operations by @fatelei in #30275.
  • Agent and Workflow Updates: New AgentMaxIterationError and enhancements in app mode checks make workflows and agents more robust by @fatelei.
  • OAuth Integration: Frontend login now supports oauth_new_user flag by @zyssyz123 in #30370.
  • PDF Extraction: Improved RAG extractor to support image extraction from PDFs by @yangzq50 in #30399.
  • Storage and Archive: Added archive storage client and config settings by @hjlarry in #30422.
  • Translation and Internationalization: Added initial RSC support for translations for a global audience by @hyoban in #30596.

🛠️ Bug Fixes

  • Redis and Cache: Used pipelines to optimize Redis cache deletions, enhancing speed and reliability by @fatelei in #30159.
  • UI/UX Fixes: From preventing page crashes due to permission errors to fixing flicking button sizes, multiple UI-related issues have been addressed by various contributors.
  • Data Operations: Fixed dataset access errors and improved error handling in batch operations by @zhaobingshuang and others.
  • Performance: Released runtime state references under high load to prevent potential memory leaks by @SherlockShemol in #30236.
  • Security: Rectified CORS and SSL issues that could've affected bot integrations and Celery operations.
  • Internationalization: Korean translations and content were updated for accuracy by @sangyun-han in #30347.

🔧 Under the Hood

  • CI/CD and Build Enhancements: Enhanced GitHub actions and build processes for better reliability and less downtime by @bowenliang123 and @hyoban.
  • Code & Query Optimization: Addressed inefficiencies in SQL queries and data handling in workflows and the API, improving overall stability.

This release emphasizes streamlining backend operations, fortifying security, and enriching the user interface for a smoother, more productive experience. Thank you to all contributors for refining Dify and pushing our platform forward! 🛠️💡

Upgrade Guide

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 https://github.com/langgenius/dify/issues/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.11.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

These notes run past the length kept in the archive. The rest is on the publisher’s page.