[PR #2058] [MERGED] bump mem0ai plugin to version 0.2.8 #2046

New Issue

2026-02-22T18:15:23-05:00

yindo commented

2026-02-22 18:15:23 -05:00

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-plugins/pull/2058
Author: @beersoccer
Created: 2/12/2026
Status: ✅ Merged
Merged: 2/12/2026
Merged by: @crazywoola

Base: main ← Head: bump-mem0ai-plugin-0.2.8

📝 Commits (1)

9764e68 bump mem0ai plugin to version 0.2.8

📊 Changes

1 file changed (+0 additions, -0 deletions)

View changed files

➕ beersoccer/mem0ai/mem0ai-0.2.8.difypkg (+0 -0)

📄 Description

Plugin Submission Form

Last updated: 2026-02-12

1. Metadata

Plugin Author: beersoccer
Plugin Name: mem0ai
Repository URL: https://github.com/beersoccer/mem0_dify_plugin

2. Submission Type

New plugin submission
Version update for existing plugin

3. Description

This submission updates the Mem0 Dify plugin (self-hosted mode). Key changes are summarized below; detailed release notes and historical context are in CHANGELOG.md.

Key Updates

Stability under load: Pre-enqueue overload guard for async operations to prevent unbounded background task buildup
Safer defaults: Tuned default timeouts/concurrency and pgvector pool sizing (see CONFIG.md for current defaults)
PGVector robustness: Connection string encoding hardened for options=-c ... injection; pool waiting cap defaults align with overload threshold

All API keys and credentials are stored locally in the user's Dify instance configuration and are not shared with any third parties. The plugin only communicates with services configured by the user (their LLM, embedding, and database services).

Privacy Policy

I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines

Privacy Policy Location: PRIVACY.md is included in the plugin package and clearly explains:

Self-hosted mode operation and data storage
Information processed by the plugin
User's complete control over data
No third-party data sharing
User's responsibility for data security and compliance

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/langgenius/dify-plugins/pull/2058 **Author:** [@beersoccer](https://github.com/beersoccer) **Created:** 2/12/2026 **Status:** ✅ Merged **Merged:** 2/12/2026 **Merged by:** [@crazywoola](https://github.com/crazywoola) **Base:** `main` ← **Head:** `bump-mem0ai-plugin-0.2.8` --- ### 📝 Commits (1) - [`9764e68`](https://github.com/langgenius/dify-plugins/commit/9764e6808c9e18debb3ca3ce0ccb88046e0d72b0) bump mem0ai plugin to version 0.2.8 ### 📊 Changes **1 file changed** (+0 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `beersoccer/mem0ai/mem0ai-0.2.8.difypkg` (+0 -0) </details> ### 📄 Description # Plugin Submission Form Last updated: 2026-02-12 ## 1. Metadata  - **Plugin Author**: beersoccer - **Plugin Name**: mem0ai - **Repository URL**: https://github.com/beersoccer/mem0_dify_plugin ## 2. Submission Type - [ ] New plugin submission - [x] Version update for existing plugin ## 3. Description  This submission updates the Mem0 Dify plugin (self-hosted mode). Key changes are summarized below; detailed release notes and historical context are in [CHANGELOG.md](https://github.com/beersoccer/mem0_dify_plugin/blob/main/CHANGELOG.md). ### Key Updates - **Stability under load**: Pre-enqueue overload guard for async operations to prevent unbounded background task buildup - **Safer defaults**: Tuned default timeouts/concurrency and pgvector pool sizing (see `CONFIG.md` for current defaults) - **PGVector robustness**: Connection string encoding hardened for `options=-c ...` injection; pool waiting cap defaults align with overload threshold All API keys and credentials are stored locally in the user's Dify instance configuration and are not shared with any third parties. The plugin only communicates with services configured by the user (their LLM, embedding, and database services). ### Privacy Policy - [x] I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines **Privacy Policy Location**: `PRIVACY.md` is included in the plugin package and clearly explains: - Self-hosted mode operation and data storage - Information processed by the plugin - User's complete control over data - No third-party data sharing - User's responsibility for data security and compliance --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

yindo added the pull-request label 2026-02-22 18:15:23 -05:00

yindo closed this issue

2026-02-22 18:15:25 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: langgenius/dify-plugins#2046