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

Feature request: Clarify future maintenance & upgrade plan for Dify 2.0.0, and provide downgrade support #20850

New Issue
Closed
opened 2026-02-21 20:09:22 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 20:09:22 -05:00
Owner
Copy Link
Copy Source

Originally created by @Xaple on GitHub (Dec 7, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

2.0.0-beta

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

cant upgrade

✔️ Expected Behavior

Currently I notice that the Dify project continues to release updates for 1.x versions, while 2.0.0 does not appear to receive recent upgrades, including fixes for the latest security vulnerabilities.

This leads to several uncertainties when using Dify 2.0.0 in production environments:

It is unclear whether 2.0.0 will continue to be officially maintained.

Recent security patches are only visible for 1.x, and no corresponding updates exist for 2.0.x.

If 2.0.0 is no longer actively maintained, is there a recommended safe downgrade path or compatibility guidelines?

These concerns affect users who have already migrated to 2.0.0 or are considering upgrading from 1.x.

Therefore, I would like to request clarification on the future roadmap for 2.0.0 and ask whether downgrade or migration tools could be provided.

❌ Actual Behavior

After upgrading to Dify 2.0.0-beta, I observed that:

No recent updates, patches, or security fixes have been released for the 2.0.x line.

Only the 1.x versions continue to receive maintenance and security updates.

There is no official documentation indicating whether 2.0.x is still actively maintained.

No downgrade instructions or compatibility notes are provided for users who may need to return to 1.x due to stability or security concerns.

This creates confusion about the long-term support status of Dify 2.0.0 and makes it difficult to determine whether it is safe to deploy in production environments.

Originally created by @Xaple on GitHub (Dec 7, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 2.0.0-beta ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce cant upgrade ### ✔️ Expected Behavior Currently I notice that the Dify project continues to release updates for 1.x versions, while 2.0.0 does not appear to receive recent upgrades, including fixes for the latest security vulnerabilities. This leads to several uncertainties when using Dify 2.0.0 in production environments: It is unclear whether 2.0.0 will continue to be officially maintained. Recent security patches are only visible for 1.x, and no corresponding updates exist for 2.0.x. If 2.0.0 is no longer actively maintained, is there a recommended safe downgrade path or compatibility guidelines? These concerns affect users who have already migrated to 2.0.0 or are considering upgrading from 1.x. Therefore, I would like to request clarification on the future roadmap for 2.0.0 and ask whether downgrade or migration tools could be provided. ### ❌ Actual Behavior After upgrading to Dify 2.0.0-beta, I observed that: No recent updates, patches, or security fixes have been released for the 2.0.x line. Only the 1.x versions continue to receive maintenance and security updates. There is no official documentation indicating whether 2.0.x is still actively maintained. No downgrade instructions or compatibility notes are provided for users who may need to return to 1.x due to stability or security concerns. This creates confusion about the long-term support status of Dify 2.0.0 and makes it difficult to determine whether it is safe to deploy in production environments.
yindo added the 💪 enhancement label 2026-02-21 20:09:22 -05:00
yindo closed this issue 2026-02-21 20:09:22 -05:00
yindo commented 2026-02-21 20:09:22 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Dec 8, 2025):

This is only for bug report, if you would like to ask a question, please head to Discussions.

@crazywoola commented on GitHub (Dec 8, 2025): This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general).
yindo commented 2026-02-21 20:09:23 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Dec 8, 2025):

2.0.0 is not the latest version, the 1.10.1-fix is the latest version.

We will release the 2.0.0 once we are ready.

Please read the instruction first before posting an feature request.

@crazywoola commented on GitHub (Dec 8, 2025): 2.0.0 is not the latest version, the 1.10.1-fix is the latest version. We will release the 2.0.0 once we are ready. Please read the instruction first before posting an feature request.
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 💪 enhancement
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#20850
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?