Skip to content

v0.14.2

Latest
Compare
Choose a tag to compare
@laipz8200 laipz8200 released this 23 Dec 11:18
· 36 commits to main since this release
e88ea71

✨ What’s New in v0.14.2? ✨

We’re thrilled to announce the release of v0.14.2, packed with new features and critical enhancements. Here’s everything new in this update:

🚀 New Features

retry
  • Workflow Retry Functionality: We've enhanced workflow resilience with a retry feature by @zxhlyh. Your nodes will make repeat attempts if they face execution errors, minimizing disruptions.

  • Order Support in Models: Now you can specify the order between text and files when using models like Gemini and Claude, thanks to the work of @laipz8200. This gives you precise control over data flow.

  • Azure GPT-4o-2024-11-20 Model: Thanks to @agungbesti, this powerful model is now part of our lineup, offering advanced capabilities for your needs.

  • Gemini-2.0-flash-thinking-exp-1219: Explore this cutting-edge model brought to you by @hjlarry—designed to enhance your application capabilities.

✨ Enhancements

  • HTTP Request Node File Type Detection: Improved by @tancheng33 to ensure better handling of file uploads.

  • Memory Optimization: Reduced memory usage from 800+ MB to 500+ MB, thanks to the optimizations by @yihong0618.

  • Partial Success Status in App Logs: With the help of @Nov1c444, we’ve introduced a new log metric to capture partial successes across app operations.

  • Workflow Parallel Depth Limit Configuration: Gain more control over concurrency in your workflows with this new setting by @laipz8200.

We owe a huge thank you to all the contributors for their hard work and dedication. Your continuous support and input drive our improvement.

As always, keep the feedback coming, and happy building with Dify! 🚀

Upgrade Guide

Docker compose deployments

Warning

The files in the docker-legacy directory will soon stop being maintained and will be removed from the repository. If you are still using them, please switch to the new version as soon as possible.

  1. Back up your customized docker-compose YAML file (optional)

    cd docker
    cp docker-compose.yaml docker-compose.yaml.$(date +%s).bak
  2. Get the latest code from the main branch

    git checkout main
    git pull origin main
  3. Stop the service,Command, please execute in the docker directory

    docker compose down
  4. Back up data

    tar -cvf volumes-$(date +%s).tgz volumes
  5. Upgrade services

    docker compose up -d

Source Code deployments

  1. Stop API server, Worker and Web frontend Server.

  2. Get the latest code from the release branch:

    git checkout 0.14.2
  3. Update Python dependencies:

    cd api
    poetry install
  4. Then, let's run the migration script:

    poetry run flask db upgrade
  5. Finally, run API server, Worker and Web frontend Server again.


What's Changed

New Contributors

Full Changelog: 0.14.1...0.14.2