[PR #444] [CLOSED] update linebot plugin to version 0.0.5 #930

Closed
opened 2026-02-22 17:42:57 -05:00 by yindo · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-plugins/pull/444
Author: @kevintsai1202
Created: 5/4/2025
Status: Closed

Base: mainHead: bump-linebot-plugin-0.0.5


📝 Commits (2)

  • f265a6f bump linebot plugin to version 0.0.5
  • e954251 Delete kevintsai/linebot/linebot.difypkg

📊 Changes

2 files changed (+0 additions, -0 deletions)

View changed files

kevintsai/linebot/linebot-0.0.5.difypkg (+0 -0)
kevintsai/linebot/linebot.difypkg (+0 -0)

📄 Description

Plugin Submission Form

1. Metadata

Update linebot

2. Submission Type

  • New plugin submission
  • Version update for existing plugin

3. Description

Fix/New Feature: When group_id (LINE group chat), room_id (chat room) exist, Session uses group_id or room_id to save conversation_id. The effect is that group chats on Dify will maintain the same conversation. thanks to [@ryantsai]([https://github.com/ryantsai]](https://github.com/ryantsai%5D)
New Feature: When the message contains markdown, send to LINE as FlexMessage. Can be adjusted in Plugin parameters, default is off. thanks to [@ryantsai]([https://github.com/ryantsai]](https://github.com/ryantsai%5D)
New Feature: Image upload uses Dify API URL parameterization, supports community edition scenarios. thanks to [@ryantsai]([https://github.com/ryantsai]](https://github.com/ryantsai%5D)

4. Checklist

  • I have read and followed the Publish to Dify Marketplace guidelines
  • I have read and comply with the Plugin Developer Agreement
  • I confirm my plugin works properly on both Dify Community Edition and Cloud Version
  • I confirm my plugin has been thoroughly tested for completeness and functionality
  • My plugin brings new value to Dify

5. Documentation Checklist

Please confirm that your plugin README includes all necessary information:

  • Step-by-step setup instructions
  • Detailed usage instructions
  • All required APIs and credentials are clearly listed
  • Connection requirements and configuration details
  • Link to the repository for the plugin source code

Privacy Policy

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

🔄 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/444 **Author:** [@kevintsai1202](https://github.com/kevintsai1202) **Created:** 5/4/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `bump-linebot-plugin-0.0.5` --- ### 📝 Commits (2) - [`f265a6f`](https://github.com/langgenius/dify-plugins/commit/f265a6f64a0269dbbac5325393c51145ba85dafd) bump linebot plugin to version 0.0.5 - [`e954251`](https://github.com/langgenius/dify-plugins/commit/e954251471b2ffa76ee7882f99b4bcf25f8aab1b) Delete kevintsai/linebot/linebot.difypkg ### 📊 Changes **2 files changed** (+0 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `kevintsai/linebot/linebot-0.0.5.difypkg` (+0 -0) ➖ `kevintsai/linebot/linebot.difypkg` (+0 -0) </details> ### 📄 Description # Plugin Submission Form ## 1. Metadata Update linebot - **Plugin Author**: kevintsai - **Plugin Name**: linebot - **Repository URL**: https://github.com/kevintsai1202/difyplugin ## 2. Submission Type - [ ] New plugin submission - [x] Version update for existing plugin ## 3. Description Fix/New Feature: When group_id (LINE group chat), room_id (chat room) exist, Session uses group_id or room_id to save conversation_id. The effect is that group chats on Dify will maintain the same conversation. thanks to [@ryantsai]([https://github.com/ryantsai]](https://github.com/ryantsai%5D) New Feature: When the message contains markdown, send to LINE as FlexMessage. Can be adjusted in Plugin parameters, default is off. thanks to [@ryantsai]([https://github.com/ryantsai]](https://github.com/ryantsai%5D) New Feature: Image upload uses Dify API URL parameterization, supports community edition scenarios. thanks to [@ryantsai]([https://github.com/ryantsai]](https://github.com/ryantsai%5D) ## 4. Checklist - [x] I have read and followed the Publish to Dify Marketplace guidelines - [x] I have read and comply with the Plugin Developer Agreement - [x] I confirm my plugin works properly on both Dify Community Edition and Cloud Version - [x] I confirm my plugin has been thoroughly tested for completeness and functionality - [x] My plugin brings new value to Dify ## 5. Documentation Checklist Please confirm that your plugin README includes all necessary information: - [x] Step-by-step setup instructions - [x] Detailed usage instructions - [x] All required APIs and credentials are clearly listed - [x] Connection requirements and configuration details - [x] Link to the repository for the plugin source code ### 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 --- <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 17:42:57 -05:00
yindo closed this issue 2026-02-22 17:42:58 -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#930