# Dify 1.11.3 — Release & Upgrade Intelligence
- **Product:** Dify (https://dify.ai)
- **Version:** 1.11.3
- **Released:** Jan 13, 2026
- **Impact Score:** 5/10
- **Breaking Changes:** Not verified
- **Canonical Analysis:** https://changelogs.us/dify/updates/1.11.3/

## Executive Summary (TL;DR)
Dify 1.11.3. Source highlight: 🚀 What's New in v1.11.3?

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

## Improvements
- **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.
- perf: using pipeline to delete redis cache
- refactor: restructure DatasetCard component for improved readability and maintainability

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