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

Clear app versioning mgmt and support draft version testing for all types of application #5800

New Issue
Closed
opened 2026-02-21 18:12:39 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 18:12:39 -05:00
Owner
Copy Link
Copy Source

Originally created by @Colstuwjx on GitHub (Sep 25, 2024).

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Currently, a workflow or advanced-chat type application would be able to trigger draft version test before publishing the changes to end users. However, non-workflow type application did NOT support this feature, e.g. chat completion or agent chat type application.

Besides, the current versioning features seems like very simple and might not be suitable for enterprise production usage. There are two pain points:

  • lack of change commit message of each version, which means we can NOT know each version change by one line message;
  • lack of change diff or changed blocks / nodes diff show, which means we can NOT make sure it's expected change and release to production while we click "publish"

2. Additional context or comments

Without some required changes for the version mgmt and release mgmt, I'm afraid that it might be risky to open the access for end users on production environment dify site. A good example that we can learn from is Apollo config center, it has implemented cross environment config sync and also gray deployment before the version goes live: https://www.apolloconfig.com/#/en/README?id=features

Do we have a roadmap for enhancing the version mgmt and release mgmt ?
Thanks.

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @Colstuwjx on GitHub (Sep 25, 2024). ### Self Checks - [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 (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. Currently, a workflow or advanced-chat type application would be able to trigger draft version test before publishing the changes to end users. However, non-workflow type application did NOT support this feature, e.g. chat completion or agent chat type application. Besides, the current versioning features seems like very simple and might not be suitable for enterprise production usage. There are two pain points: - lack of change commit message of each version, which means we can NOT know each version change by one line message; - lack of change diff or changed blocks / nodes diff show, which means we can NOT make sure it's expected change and release to production while we click "publish" ### 2. Additional context or comments Without some required changes for the version mgmt and release mgmt, I'm afraid that it might be risky to open the access for end users on production environment dify site. A good example that we can learn from is Apollo config center, it has implemented cross environment config sync and also gray deployment before the version goes live: https://www.apolloconfig.com/#/en/README?id=features Do we have a roadmap for enhancing the version mgmt and release mgmt ? Thanks. ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 18:12:39 -05:00
yindo closed this issue 2026-02-21 18:12:39 -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 💪 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#5800
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?