You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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
Back up your customized docker-compose YAML file (optional)
cd docker cp docker-compose.yaml docker-compose.yaml.$(date +%s).bak
Get the latest code from the main branch
git checkout main git pull origin main
Stop the service. Please execute in the docker directory
docker compose down
Back up data
tar -cvf volumes-$(date +%s).tgz volumes
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
Stop the API server, Worker, and Web frontend Server.
Get the latest code from the release branch:
git checkout 1.11.3
Update Python dependencies:
cd api uv sync
Then, let's run the migration script:
uv run flask db upgrade
Finally, run the API server, Worker, and Web frontend Server again.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
🚀 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
embeddedResourceand made MCP tools display directly for quicker access by @IthacaDream and @fatelei in feat: MCP tool adds support for embeddedResource #30261 and feat: add mcp tool display directly #30019.oauth_new_userflag by @zyssyz123 in feat: add oauth_new_user flag for frontend when user oauth login #30370.🛠️ Bug Fixes
🔧 Under the Hood
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
Back up your customized docker-compose YAML file (optional)
Get the latest code from the main branch
Stop the service. Please execute in the docker directory
Back up data
tar -cvf volumes-$(date +%s).tgz volumesUpgrade services
Note
If you encounter errors like below
Please use the following command instead. For details, please read this #28706
Source Code Deployments
Stop the API server, Worker, and Web frontend Server.
Get the latest code from the release branch:
Update Python dependencies:
cd api uv syncThen, let's run the migration script:
Finally, run the API server, Worker, and Web frontend Server again.
What's Changed
process.env.NODE_ENVchecks withIS_PRODandIS_DEVconstants. by @lyzno1 in refactor: Replace directprocess.env.NODE_ENVchecks withIS_PRODandIS_DEVconstants. #30383--build-argin docker build by @darkelf21cn in fix: support to change NEXT_PUBLIC_BASE_PATH env using--build-argin docker build #29836graphfield optional via env variable LOGSTORE… by @scdeng in feat(logstore): makegraphfield optional via env variable LOGSTORE… #30554New Contributors
--build-argin docker build #29836graphfield optional via env variable LOGSTORE… #30554Full Changelog: 1.11.2...1.11.3
This discussion was created from the release v1.11.3.
Beta Was this translation helpful? Give feedback.
All reactions