langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

[PR #16457] chore: update version to 1.1.2 in configuration and Docker files #28510

New Issue
Closed
opened 2026-02-21 20:43:35 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 20:43:35 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/langgenius/dify/pull/16457

State: closed
Merged: Yes

✨ What’s New in v1.1.2? ✨

Thanks for keeping up with Dify! This patch delivers some important fixes to boost the stability and security of your operations.

Important

This update includes a critical fix for an XSS vulnerability. Cloud users are not affected by this issue.

This version disables the SVG rendering in the message. If you are using our Community Edition and meet all of the following conditions, we recommend that you upgrade to the current version immediately:

  1. Your service is exposed to the internet.
  2. You provide external WebApps.
  3. You have not configured SERVICE_API_URL and FILES_URL on different domains.

🛠️ Fixes & Improvements

  • Security: Resolved an XSS vulnerability related to rendering SVGs, closing a security gap with help from @iamjoel in #16433.

  • Knowledge Base Cleanup: Fixed an issue where the OpenAPI interface couldn't delete metadata, thanks to @StrayDragon in #16365. Now clearing out old or unnecessary metadata is straightforward.

  • GitHub Plugin Installation: Resolved an import DSL issue that blocked the installation of the GitHub plugin, thanks to @junjiem in #16362. This patch ensures smoother plugin integrations.

  • Metadata Migration Check: Added a check for built-in fields during old metadata migration to ensure completeness and accuracy, contributed by @JohnJyong in #16371. Your metadata migrations have stepped up in robustness.

  • Literal Syntax Error Handling: Fixed errors related to literal_eval function usage, courtesy of @svcvit in #16297. These changes help keep your code from breaking due to syntax evaluation.

This update is all about refining the edges and enhancing the user experience—an essential pit-stop on our road to new features and capabilities. Keep those contributions and feedback coming, and let's make Dify even better, together! 🚀

**Original Pull Request:** https://github.com/langgenius/dify/pull/16457 **State:** closed **Merged:** Yes --- # ✨ What’s New in v1.1.2? ✨ Thanks for keeping up with Dify! This patch delivers some important fixes to boost the stability and security of your operations. > [!Important] > > This update includes a critical fix for an XSS vulnerability. Cloud users are not affected by this issue. > > This version disables the SVG rendering in the message. If you are using our Community Edition and meet all of the following conditions, we recommend that you upgrade to the current version immediately: > > 1. Your service is exposed to the internet. > 2. You provide external WebApps. > 3. You have not configured `SERVICE_API_URL` and `FILES_URL` on different domains. ## 🛠️ Fixes & Improvements - **Security**: Resolved an XSS vulnerability related to rendering SVGs, closing a security gap with help from @iamjoel in #16433. - **Knowledge Base Cleanup**: Fixed an issue where the OpenAPI interface couldn't delete metadata, thanks to @StrayDragon in #16365. Now clearing out old or unnecessary metadata is straightforward. - **GitHub Plugin Installation**: Resolved an import DSL issue that blocked the installation of the GitHub plugin, thanks to @junjiem in #16362. This patch ensures smoother plugin integrations. - **Metadata Migration Check**: Added a check for built-in fields during old metadata migration to ensure completeness and accuracy, contributed by @JohnJyong in #16371. Your metadata migrations have stepped up in robustness. - **Literal Syntax Error Handling**: Fixed errors related to `literal_eval` function usage, courtesy of @svcvit in #16297. These changes help keep your code from breaking due to syntax evaluation. This update is all about refining the edges and enhancing the user experience—an essential pit-stop on our road to new features and capabilities. Keep those contributions and feedback coming, and let's make Dify even better, together! 🚀
yindo added the pull-request label 2026-02-21 20:43:35 -05:00
yindo closed this issue 2026-02-21 20:43:35 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#28510
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?