📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-plugins/pull/1086
Author: @kenneth-bro
Created: 8/14/2025
Status: ✅ Merged
Merged: 8/14/2025
Merged by: @crazywoola

Base: main ← Head: feat/news

📝 Commits (1)

5e570fa fix: news

📊 Changes

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

View changed files

➕ investoday/news/investoday-news-1.0.2.difypkg (+0 -0)

📄 Description

Plugin Submission Form

1. Metadata

Plugin Author: investoday
Plugin Name: investoday-news
Repository URL: https://github.com/kenneth-bro/dify-plugin-investoday-apis.git

2. Submission Type

[] New plugin submission
Version update for existing plugin

3. Description

update

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

No personal data is collected by these plugins.
Only necessary API invocation metadata may be logged for service optimization and troubleshooting.
All financial market data is fetched via the user’s own API key; API keys are user-managed and not stored by the plugins.

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/1086 **Author:** [@kenneth-bro](https://github.com/kenneth-bro) **Created:** 8/14/2025 **Status:** ✅ Merged **Merged:** 8/14/2025 **Merged by:** [@crazywoola](https://github.com/crazywoola) **Base:** `main` ← **Head:** `feat/news` --- ### 📝 Commits (1) - [`5e570fa`](https://github.com/langgenius/dify-plugins/commit/5e570facd2f54ef12df410d951009a82ecd5dbc0) fix: news ### 📊 Changes **1 file changed** (+0 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `investoday/news/investoday-news-1.0.2.difypkg` (+0 -0) </details> ### 📄 Description # Plugin Submission Form ## 1. Metadata - Plugin Author: investoday - Plugin Name: investoday-news - Repository URL: https://github.com/kenneth-bro/dify-plugin-investoday-apis.git ## 2. Submission Type - [] New plugin submission - [x] Version update for existing plugin ## 3. Description update ## 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 ## 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 - No personal data is collected by these plugins. - Only necessary API invocation metadata may be logged for service optimization and troubleshooting. - All financial market data is fetched via the user’s own API key; API keys are user-managed and not stored by the plugins. ### 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>