Traceary

Catalog / Dify

1.7.2

v1.7.2

1 year agosecurityaddedfixedOriginal notes

✨ What’s New in v1.7.2? ✨

Alright folks, buckle up! Version 1.7.2 is here, packed with a ton of quality-of-life improvements, bug fixes, and some slick new features to make your Dify experience even smoother. This release has been a community effort, and we want to give a big shoutout to all the contributors, especially the new folks who jumped in – welcome to the party! 🎉

🚀 Major Feature: Workflow Visualization

A new relations panel allows you to visualize dependencies within your workflows. Big thanks to @Minamiyama for #21998! Now when you select any node and press Shift, you will see magic flowing lines.

🚀 Major Feature: Node Search

You can now easily find nodes in the workflow editor using the new search feature by @croatialu, @ZeroZ-lab, @HyaCiovo, @MatriQ, @lyzno1, @crazywoola in #23685.

⚙️ Enhancements

  • Notion Database Row Extraction: The Notion Database integration now extracts rows in their original order and appends the Row Page URL. Thanks @ThreeFish-AI! #22646
  • Workflow API Version Specification: You can now specify workflow versions in the workflow and chat APIs. Thanks, @qiaofenlin! #23188
  • Tool JSON Response: Datetime and UUID are now supported in tool JSON responses, making those integrations even more powerful. Kudos to @jiangbo721! #22738
  • API Documentation: The API documentation has been revamped with a modern design and improved UX. Thanks @lyzno1! #23490
  • Workflow Node Alignment: Get those workflows looking sharp with enhanced node alignment options. Thanks, @ZeroZ-lab! #23451
  • Service API File Preview Endpoint: A new endpoint to preview service API files, making it easier to manage and debug your services. Hat tip to @lyzno1! #23534
  • Testcontainers Tests: We're serious about stability! @NeatGuyCoding and others have been hard at work adding Testcontainers tests for various services (account, app, message, workflow etc.) ensuring our services are rock solid.

🛠️ Bug Fixes

  • Full-Text Search with Tencent Cloud VectorDB: Fixed an issue where metadata filters weren't being applied correctly in full-text search mode for Tencent Cloud VectorDB. Thanks, @dlmu-lq! #23564
  • Workflow Knowledge Retrieval Cache: Fixed a cache bug in workflow knowledge retrieval. Another one bites the dust, thanks to @yunqiqiliang! #23597
  • HTTP Request Component: Resolved a multipart/form-data boundary issue in the HTTP Request component. Thanks to @baonudesifeizhai for fixing this long-standing issue! #23008
  • Conversation Variable Sync: Fixed an issue where conversation variables weren't being synced for existing conversations. Thanks to @laipz8200 for hunting this down! #23649
  • Internationalization (i18n): Numerous i18n fixes and enhancements across the board. Shoutout to @lyzno1 and the i18n team for their dedication!
  • Edge Cases Handled: We squashed a number of edge-case bugs, thanks to the contributions of many in the community.

🛡️ Security

  • XSS Vulnerability: A big thank you to @lyzno1 for identifying and fixing an XSS vulnerability in the authentication check-code pages. #23295

Upgrade Guide

Docker Compose Deployments

  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. 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 the API server, Worker, and Web frontend Server.

  2. Get the latest code from the release branch:

    git checkout 1.7.2

  3. Update Python dependencies:

    cd api
uv sync

  4. Then, let's run the migration script:

    uv run flask db upgrade

  5. Finally, run the API server, Worker, and Web frontend Server again.

What's Changed

Full Changelog:

These notes run past the length kept in the archive. The rest is on the publisher’s page.