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

[PR #7979] chore: update package versions to 0.8.0-beta1 #25892

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

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

State: closed
Merged: Yes

✨ What’s New in v0.8.0-beta1?✨

We are excited to announce the release of Dify 0.8.0-beta1! This version introduces a significant enhancement to workflow performance by enabling the parallel execution of nodes within workflows. This improvement allows workflows to run faster and more efficiently, optimizing the use of resources and reducing overall processing time.

🚀 Key Features

  • Parallel Execution of Nodes in Workflows: Nodes can now be executed in parallel within a workflow, greatly increasing the execution speed. This feature is especially beneficial for complex workflows that involve multiple steps or processes, allowing for quicker completion times and improved performance.

    image

Quick Start

To upgrade to this version, follow these steps:

  1. Clone the repository using the following command:

    git clone https://github.com/langgenius/dify.git

  2. Switch to the 0.8.0-beta1 branch:

    git checkout 0.8.0-beta1

  3. Then following the Deploy with Docker Compose > Starting Dify.

We hope you enjoy the new features and improvements in this release. As always, we welcome your feedback and contributions to make Dify even better!

**Original Pull Request:** https://github.com/langgenius/dify/pull/7979 **State:** closed **Merged:** Yes --- ## ✨ What’s New in v0.8.0-beta1?✨ We are excited to announce the release of Dify 0.8.0-beta1! This version introduces a significant enhancement to workflow performance by enabling the parallel execution of nodes within workflows. This improvement allows workflows to run faster and more efficiently, optimizing the use of resources and reducing overall processing time. ### 🚀 Key Features - **Parallel Execution of Nodes in Workflows**: Nodes can now be executed in parallel within a workflow, greatly increasing the execution speed. This feature is especially beneficial for complex workflows that involve multiple steps or processes, allowing for quicker completion times and improved performance. ![image](https://github.com/user-attachments/assets/98b209a1-d72e-4e8b-8bfe-7ca0babf27c4) ### Quick Start To upgrade to this version, follow these steps: 1. Clone the repository using the following command: ```bash git clone https://github.com/langgenius/dify.git ``` 2. Switch to the 0.8.0-beta1 branch: ```bash git checkout 0.8.0-beta1 ``` 3. Then following the [Deploy with Docker Compose > Starting Dify](https://docs.dify.ai/getting-started/install-self-hosted/docker-compose#starting-dify). We hope you enjoy the new features and improvements in this release. As always, we welcome your feedback and contributions to make Dify even better!
yindo added the pull-request label 2026-02-21 20:29:03 -05:00
yindo closed this issue 2026-02-21 20:29:10 -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#25892
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?