Skip to content

Update dependency langgenius/dify to v1 #12

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

Update dependency langgenius/dify to v1 #12

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 28, 2025 •
edited
Loading

This PR contains the following updates:

Package Update Change
langgenius/dify major 0.15.3 -> 1.1.2

Release Notes

langgenius/dify (langgenius/dify)

v1.1.2

Compare Source

✨ What’s New in v1.1.2? ✨

Thanks for keeping up with Dify! This patch delivers some important fixes to boost the stability and security of your operations.

[!Important]

This update includes a critical fix for an XSS vulnerability. Cloud users are not affected by this issue.

This version disables the SVG rendering in the message. If you are using our Community Edition and meet all of the following conditions, we recommend that you upgrade to the current version immediately:

  1. Your service is exposed to the internet.
  2. You provide external WebApps.
  3. You have not configured SERVICE_API_URL and FILES_URL on different domains.
🛠️ Fixes & Improvements

  • Security: Resolved an XSS vulnerability related to rendering SVGs, closing a security gap with help from @​iamjoel in #​16433.

  • Knowledge Base Cleanup: Fixed an issue where the OpenAPI interface couldn't delete metadata, thanks to @​StrayDragon in #​16365. Now clearing out old or unnecessary metadata is straightforward.

  • GitHub Plugin Installation: Resolved an import DSL issue that blocked the installation of the GitHub plugin, thanks to @​junjiem in #​16362. This patch ensures smoother plugin integrations.

  • Metadata Migration Check: Added a check for built-in fields during old metadata migration to ensure completeness and accuracy, contributed by @​JohnJyong in #​16371. Your metadata migrations have stepped up in robustness.

  • Literal Syntax Error Handling: Fixed errors related to literal_eval function usage, courtesy of @​svcvit in #​16297. These changes help keep your code from breaking due to syntax evaluation.

This update is all about refining the edges and enhancing the user experience—an essential pit-stop on our road to new features and capabilities. Keep those contributions and feedback coming, and let's make Dify even better, together! 🚀

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

  2. Get the latest code from the release branch:

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

What's Changed
New Contributors

Full Changelog: langgenius/dify@1.1.1...1.1.2

v1.1.1

Compare Source

✨ What’s New in v1.1.1? ✨

We've got some cool updates and fixes in v1.1.1 to keep things running smoother and shinier. Let's dive in:

⚙️ Enhancements

Big thanks to all contributors for making v1.1.1 even better! Keep diving into those projects and creating cool things!

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

  2. Get the latest code from the release branch:

    git checkout 1.1.1

  3. Update Python dependencies:

    cd api
poetry install

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

    poetry run flask db upgrade

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

What's Changed
New Contributors

Full Changelog: langgenius/dify@1.1.0...1.1.1

v1.1.0

Compare Source

🚀 What's New in v1.1.0

Welcome to v1.1.0! This release packs a punch with significant improvements, enhancements, and the introduction of some much-awaited features. Here's what we've got:

🚀 New Features
  • Metadata Filtering for Knowledge Retrieval by @​JohnJyong in #​15982 and #​16063. Metadata filtering enhances the retrieval and accuracy of relevant data in knowledge bases by leveraging custom metadata attributes. This makes finding the right data quicker and more precise. To get more information, please read our blog.
    image
🛠️ Enhancements
🐞 Bug Fixes
Miscellaneous

This release aims to strengthen our platform's reliability, security, and usability, and we are keen on hearing your feedback. Happy coding with v1.1.0!

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

  2. Get the latest code from the release branch:

    git checkout 1.1.0

  3. Update Python dependencies:

    cd api
poetry install

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

    poetry run flask db upgrade

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

What's Changed
New Contributors

Full Changelog: langgenius/dify@1.0.1...1.1.0

v1.0.1

Compare Source

🎉 Welcome to v1.0.1! 🎉

We've leveled up to v1.0.1, bringing a bunch of improvements, new features, and fixes. Here’s the lowdown without the bloat:

🛠️ Fixes & Improvements

  • Cache Mechanics for Plugin Models: Reducing redundancy through improved caching, championed by @​Yeuoly in #​14968 and #​14898.

  • Connectors & Workflows: Improved data source handling: Fixed iteration logs, edges in copied nodes, and one-step run operations with updates in #​14855 by @​iamjoel, #​12692 by @​ihaichao, and #​14724 by @​zxhlyh.

  • Visual & UX Refinements: Interface upgrades across the board with zoom handling, dataset selection revamps, and fullscreen toggles improved by @​WTW0313, @​marsDes, and others.

  • Stability & Reliability: Tackled pesky bugs—be it with document extracts, chat components, or execution metadata—to make your experience smooth. Solutions from @​hjlarry, @​jiangbo721, and more.

You might have already met these errors, we fixed them in this version.

core.plugin.manager.exc.PluginDaemonInternalServerError: PluginDaemonInternalServerError: no available node, plugin not found
Error: PluginDaemonInternalServerError: killed by timeout
<Site at 0x7ffaec0a8c50> is not bound to a Session
TypeError: expected string or bytes-like object, got 'NoneType'
...
🌐 Internationalization

For a more detailed dive into each update, feel free to browse through the PRs. We’re all about improving and adapting, so keep the feedback coming. Now go explore what’s new, and as always, happy coding! 🚀

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，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 1.0.1

  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

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/langgenius-dify-1.x branch 2 times, most recently from 3ed9581 to 2a32258 Compare March 18, 2025 13:09
@renovate renovate bot force-pushed the renovate/langgenius-dify-1.x branch from 2a32258 to cf6e5d1 Compare March 20, 2025 10:26
@renovate renovate bot force-pushed the renovate/langgenius-dify-1.x branch from cf6e5d1 to c373b6c Compare March 21, 2025 16:26
@renovate renovate bot deleted the renovate/langgenius-dify-1.x branch March 23, 2025 13:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@andex-tokyo andex-tokyo

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@andex-tokyo