Skip to content

feat(container)!: Update image langgenius/dify-api to v1 #325

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
Open
renovate wants to merge 1 commit into
base: main
Choose a base branch
from
Open

feat(container)!: Update image langgenius/dify-api to v1 #325

renovate wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 1, 2025 •
edited
Loading

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Update Change
langgenius/dify-api major 0.6.11 → 1.11.2

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

langgenius/dify (langgenius/dify-api)

v1.11.2

Compare Source

🌟 What’s New in v1.11.2 🌟

Welcome to version 1.11.2! This release sees a significant number of improvements, especially around testing, fixes, and new integrations to enhance the robustness and flexibility of the platform. Here's the lowdown:

🚀 New Features
  • InterSystems IRIS Vector Database: We've added support for this database to bolster data handling capabilities. Big ups to @​TomoOkuyama! (#​29480)
  • Aliyun SLS Integration: Workflow execution logging can now leverage Aliyun's Simple Log Service, courtesy of @​adongfan. (#​28986)
  • Tunisian Arabic Support: We've expanded our language support with Tunisian Arabic. Shukran @​nourzakhama2003! (#​29306)
⚙️ Enhancements
  • Comprehensive Test Coverage: A slew of Jest tests have been added to various components, such as the ConfirmModal, AppCard, CustomizeModal, and more. Thanks to everyone involved, especially @​lyzno1! These enhance our confidence in releasing robust changes. (#​29627, #​29667, etc.)
  • Amplitude Tracking: Enhanced user behavior tracking across the platform for deeper insights, thanks to @​CodingOnStar. (#​29662)
  • Pipeline Setting Tests: Automated testing has been added to ensure any future changes to pipeline settings won't break your optimizations. (#​29478)
  • Responsive Chat Wrapper: We've optimized the chat interface for better usability across all device types. Props to @​hangboss1761. (#​29687)
🛠️ Bug Fixes
  • Unified Translation: Fixed various translation-related issues across multiple languages for a more coherent global experience. Thanks, @​ZeroZ-lab! (#​29759)
  • Security Enhancements: We've patched an XSS vulnerability with the Mermaid Graph and tackled SSRF and CSV injection issues. Kudos to @​zyssyz123 and @​laipz8200. (#​29811, #​29462)
  • Upload Fixes: If file uploads are disabled, they'll now be consistently so across the board. Big thanks to @​iamjoel. (#​29681)
  • API Key Validation: Ensures API keys in HTTPRequest nodes are never empty, thanks to @​AziizBg. (#​29950)
  • Miscellaneous Fixes: A whole host of tweaks ranging from workflow past version data synchronization to adjustment of padding for better alignment. Massive thanks to all who squashed these bugs! (#​30139, #​29999)
🎨 Code Quality & Maintenance
  • Refactor Marathon: We've massively refactored our API and web controllers to make future updates easier and more performant. Big thanks to @​asukaminato0721 for spearheading this. (#​29894, #​29888, etc.)
  • Jest and Webpack Optimizations: Improved Jest caching, configuration, and migration to Vitest/ESM in the web components for quicker, more reliable tests. Hats off to @​lyzno1 and @​hyoban. (#​29881, #​29974)
  • Documentation Cleanup: The Swagger UI is now disabled by default in production releases, being more cautious about what information hangs out there. Thanks @​laipz8200. (#​29723)

That's the round-up for v1.11.2! As always, a huge shoutout to all contributors who make these improvements possible. You rock! Now, go try the new release, and hit us up with feedback. 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. 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

[!NOTE]

If you encounter errors like below

2025/11/26 11:37:57 /app/internal/db/pg/pg.go:30
[error] failed to initialize database, got error failed to connect to `host=db_postgres user=postgres database=dify_plugin`: hostname resolving error (lookup db_postgres on 127.0.0.11:53: server misbehaving)

2025/11/26 11:37:57 /app/internal/db/pg/pg.go:34
[error] failed to initialize database, got error failed to connect to `host=db_postgres user=postgres database=postgres`: hostname > resolving error (lookup db_postgres on 127.0.0.11:53: server misbehaving)
2025/11/26 11:37:57 init.go:99: [PANIC]failed to init dify plugin db: failed to connect to `host=db_postgres user=postgres database=postgres`: hostname resolving error (lookup db_postgres on 127.0.0.11:53: server misbehaving)
panic: [PANIC]failed to init dify plugin db: failed to connect to `host=db_postgres user=postgres database=postgres`: hostname resolving error (lookup db_postgres on 127.0.0.11:53: server misbehaving)

Please use the following command instead. For details, please read this #​28706

docker compose --profile postgresql 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.11.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
New Contributors

Full Changelog: langgenius/dify@1.11.1...1.11.2

v1.11.1

Compare Source

[!IMPORTANT]

This version contains very important security updates, and we recommend that all users upgrade to this version as soon as possible.

This release is all about tightening up security, boosting performance, and squashing those pesky bugs. Let's dive into what's changed:

🛠️ Fixes and Improvements

  • React and Next.js Security Upgrades: We've bumped up react and react-dom to 19.2.3 to fix some CVE vulnerabilities. Next.js also got a security update, courtesy of @​douxc (PRs #​29532 and #​29545).

  • Credential Management: If you've been seeing empty available_credentials, that's sorted out now (thanks to @​fatelei in #​29521).

  • Description Length Limitation: Autogenerated descriptions will now be truncated to avoid the 400-character limit error, ensuring smoother submissions by @​shua-chen in #​28681.

  • Content Type Charset: Response content types now include charsets to keep your data formats consistent, by @​Pleasurecruise in #​29534.

  • Flask-Restx Attribute Error: The pesky AttributeError caused by validate=True in flask-restx is no more (fixed by @​Mairuis in #​29552).

  • Document Handling: Optimized the save_document_with_dataset_id function for better performance by @​fatelei in #​29550. Plus, we fixed an issue where external images in DOCX files were causing extraction failures (@​JohnJyong in #​29558).

  • Token Retrieval: No more errors when access_token is empty; it now gracefully returns None by @​kashira2339 in #​29516.

  • Hit-Test Failures: Resolved the hit-test failure when an attachment ID doesn’t exist by @​JohnJyong in #​29563.

🚀 New Features

  • Amplitude Integration: We’ve integrated the Amplitude API key into our layout and provider components for enhanced analytics. Big thanks to @​CodingOnStar in #​29546.

🧪 Testing

  • Container Integration Tests: Added integration tests for triggers to make sure everything runs smoothly in container environments by @​Stream29 in #​29527.

⚡ Performance Enhancements

  • Excel Extractor: We've optimized the performance and memory usage of the Excel extractor, making it faster and more efficient, by @​NieRonghua in #​29551.

Thanks to everyone who contributed to this release! Your feedback and contributions make all the difference. 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. 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

[!NOTE]

If you encounter errors like below

2025/11/26 11:37:57 /app/internal/db/pg/pg.go:30
[error] failed to initialize database, got error failed to connect to `host=db_postgres user=postgres database=dify_plugin`: hostname resolving error (lookup db_postgres on 127.0.0.11:53: server misbehaving)

2025/11/26 11:37:57 /app/internal/db/pg/pg.go:34
[error] failed to initialize database, got error failed to connect to `host=db_postgres user=postgres database=postgres`: hostname > resolving error (lookup db_postgres on 127.0.0.11:53: server misbehaving)
2025/11/26 11:37:57 init.go:99: [PANIC]failed to init dify plugin db: failed to connect to `host=db_postgres user=postgres database=postgres`: hostname resolving error (lookup db_postgres on 127.0.0.11:53: server misbehaving)
panic: [PANIC]failed to init dify plugin db: failed to connect to `host=db_postgres user=postgres database=postgres`: hostname resolving error (lookup db_postgres on 127.0.0.11:53: server misbehaving)

Please use the following command instead. For details, please read this #​28706

docker compose --profile postgresql 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.11.1

  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

Configuration

📅 Schedule: Branch creation - "on saturday" (UTC), 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 these updates again.

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

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

@github-actions
Copy link

github-actions bot commented Mar 1, 2025 •
edited
Loading 

--- kubernetes/apps/ai/dify/app Kustomization: flux-system/cluster-apps-ai-dify-app HelmRelease: ai-apps/dify-app

+++ kubernetes/apps/ai/dify/app Kustomization: flux-system/cluster-apps-ai-dify-app HelmRelease: ai-apps/dify-app

@@ -43,13 +43,13 @@

                 name: dify-env-configs
             - secretRef:
                 name: dify-env-secrets
             image:
               pullPolicy: Always
               repository: langgenius/dify-api
-              tag: 0.6.11
+              tag: 1.9.0
         replicas: 1
         strategy: Recreate
       web:
         containers:
           web:
             env:
@@ -74,13 +74,13 @@

                 name: dify-env-configs
             - secretRef:
                 name: dify-env-secrets
             image:
               pullPolicy: Always
               repository: langgenius/dify-api
-              tag: 0.6.11
+              tag: 1.9.0
         replicas: 1
         strategy: Recreate
     ingress:
       main:
         annotations:
           external-dns.alpha.kubernetes.io/target: external.

@github-actions
Copy link

github-actions bot commented Mar 1, 2025 •
edited
Loading 

--- HelmRelease: ai-apps/dify-app Deployment: ai-apps/dify-app

+++ HelmRelease: ai-apps/dify-app Deployment: ai-apps/dify-app

@@ -40,13 +40,13 @@

           value: api
         envFrom:
         - configMapRef:
             name: dify-env-configs
         - secretRef:
             name: dify-env-secrets
-        image: langgenius/dify-api:0.6.11
+        image: langgenius/dify-api:1.9.0
         imagePullPolicy: Always
         livenessProbe:
           failureThreshold: 3
           initialDelaySeconds: 0
           periodSeconds: 10
           tcpSocket:
--- HelmRelease: ai-apps/dify-app Deployment: ai-apps/dify-app-worker

+++ HelmRelease: ai-apps/dify-app Deployment: ai-apps/dify-app-worker

@@ -40,13 +40,13 @@

           value: worker
         envFrom:
         - configMapRef:
             name: dify-env-configs
         - secretRef:
             name: dify-env-secrets
-        image: langgenius/dify-api:0.6.11
+        image: langgenius/dify-api:1.9.0
         imagePullPolicy: Always
         name: main
         volumeMounts:
         - mountPath: /app/api/storage
           name: data
       volumes:

@renovate renovate bot force-pushed the renovate/langgenius-dify-api-1.x branch 2 times, most recently from 4e643ec to dc45ed1 Compare March 18, 2025 13:30
@renovate renovate bot force-pushed the renovate/langgenius-dify-api-1.x branch 3 times, most recently from 163407e to e7f957e Compare March 24, 2025 11:35
@renovate renovate bot force-pushed the renovate/langgenius-dify-api-1.x branch 2 times, most recently from 24062a2 to 9ef6e83 Compare April 9, 2025 12:10
@renovate renovate bot force-pushed the renovate/langgenius-dify-api-1.x branch 2 times, most recently from cd34520 to 647b4a2 Compare April 28, 2025 14:02
@renovate renovate bot force-pushed the renovate/langgenius-dify-api-1.x branch from 647b4a2 to 650083e Compare May 15, 2025 12:28
@renovate renovate bot force-pushed the renovate/langgenius-dify-api-1.x branch from 650083e to 287a626 Compare May 27, 2025 14:01
@renovate renovate bot force-pushed the renovate/langgenius-dify-api-1.x branch 2 times, most recently from 83653b7 to a0c7546 Compare June 16, 2025 11:29
@renovate renovate bot force-pushed the renovate/langgenius-dify-api-1.x branch 2 times, most recently from 6f14cf8 to 152f31e Compare July 2, 2025 11:45
@renovate renovate bot force-pushed the renovate/langgenius-dify-api-1.x branch from 152f31e to 1cfef78 Compare July 10, 2025 12:41
@renovate renovate bot force-pushed the renovate/langgenius-dify-api-1.x branch 2 times, most recently from ba3e095 to 92967ac Compare July 28, 2025 18:01
@renovate renovate bot force-pushed the renovate/langgenius-dify-api-1.x branch from 92967ac to 4f8e255 Compare August 11, 2025 09:52
@renovate renovate bot force-pushed the renovate/langgenius-dify-api-1.x branch from 4f8e255 to 1c00500 Compare August 27, 2025 11:13
@renovate renovate bot force-pushed the renovate/langgenius-dify-api-1.x branch from 1c00500 to c7b1e01 Compare September 6, 2025 20:12
@renovate renovate bot force-pushed the renovate/langgenius-dify-api-1.x branch from c7b1e01 to 219f1c6 Compare September 22, 2025 12:43
@renovate renovate bot force-pushed the renovate/langgenius-dify-api-1.x branch from 219f1c6 to 4190bb2 Compare September 29, 2025 14:53
@renovate renovate bot force-pushed the renovate/langgenius-dify-api-1.x branch from 4190bb2 to 92d8766 Compare October 21, 2025 20:48
@renovate renovate bot force-pushed the renovate/langgenius-dify-api-1.x branch from 92d8766 to f892a30 Compare November 13, 2025 20:44
@renovate renovate bot force-pushed the renovate/langgenius-dify-api-1.x branch from f892a30 to c74874c Compare November 26, 2025 17:38
@renovate renovate bot force-pushed the renovate/langgenius-dify-api-1.x branch 2 times, most recently from 9cf4a8c to 764fe46 Compare December 12, 2025 09:03
@renovate renovate bot force-pushed the renovate/langgenius-dify-api-1.x branch from 764fe46 to 8c8ec77 Compare December 25, 2025 13:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

renovate/container type/major

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant