langgenius/dify-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-plugins.git synced 2026-07-22 01:55:36 -04:00
Code Issues 119 Packages Projects Releases Wiki Activity

[PR #1634] [MERGED] bump base64_codec plugin to version 1.0.1 #1738

New Issue
Closed
opened 2026-02-22 18:06:45 -05:00 by yindo · 0 comments
yindo commented 2026-02-22 18:06:45 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-plugins/pull/1634
Author: @bowenliang123
Created: 11/27/2025
Status: ✅ Merged
Merged: 11/28/2025
Merged by: @crazywoola

Base: main ← Head: bump-base64_codec-plugin-1.0.1

📝 Commits (1)

  • 98b625d bump base64_codec plugin to version 1.0.1

📊 Changes

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

View changed files

➕ bowenliang123/base64_codec/base64_codec-1.0.1.difypkg (+0 -0)

📄 Description

Plugin Submission Form

1. Metadata

Author: bowenliang123

Github Repository: https://github.com/bowenliang123/base64_codec

Dify Marketplace: https://marketplace.dify.ai/plugins/bowenliang123/base64_codec

2. Submission Type

  • New plugin submission
  • Version update for existing plugin

3. Description

  • update description of the parameter "output_file", showing the hints for multiple files support

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

6. Privacy Protection Information

Based on Dify Plugin Privacy Protection Guidelines:

Data Collection

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/1634 **Author:** [@bowenliang123](https://github.com/bowenliang123) **Created:** 11/27/2025 **Status:** ✅ Merged **Merged:** 11/28/2025 **Merged by:** [@crazywoola](https://github.com/crazywoola) **Base:** `main` ← **Head:** `bump-base64_codec-plugin-1.0.1` --- ### 📝 Commits (1) - [`98b625d`](https://github.com/langgenius/dify-plugins/commit/98b625d1f8a5c1d40a8663d702a4b3dfcb2540bf) bump base64_codec plugin to version 1.0.1 ### 📊 Changes **1 file changed** (+0 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `bowenliang123/base64_codec/base64_codec-1.0.1.difypkg` (+0 -0) </details> ### 📄 Description # Plugin Submission Form ## 1. Metadata <!-- Please provide the following metadata of your plugin to make it easier for the reviewer to check the changes. - Plugin Author : The author of the plugin which is defined in your manifest.yaml - Plugin Name : The name of the plugin which is defined in your manifest.yaml - Repository URL: The URL of the repository where the source code of your plugin is hosted --> **Author:** [bowenliang123](https://github.com/bowenliang123) **Github Repository:** https://github.com/bowenliang123/base64_codec **Dify Marketplace:** https://marketplace.dify.ai/plugins/bowenliang123/base64_codec ## 2. Submission Type - [ ] New plugin submission - [ ] Version update for existing plugin ## 3. Description <!-- Please briefly describe the purpose of the new plugin or the updates made to the existing plugin --> - update description of the parameter "output_file", showing the hints for multiple files support ## 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 ## 6. Privacy Protection Information Based on Dify Plugin Privacy Protection [Guidelines](https://docs.dify.ai/plugins/publish-plugins/publish-to-dify-marketplace/plugin-privacy-protection-guidelines): ### Data Collection <!-- Does your plugin collect any user personal data? If yes, please list what types of user personal data are being collected according to the Plugin Privacy Protection Guidelines (for example: Email address, IP address, Age, etc) --> ### Privacy Policy - [ ] 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 18:06:45 -05:00
yindo closed this issue 2026-02-22 18:06:45 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Plugin Request
Plugin Request
Plugin Request
bug
duplicate
enhancement
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-plugins#1738
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?