📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-plugins/pull/1837
Author: @Flying-Tom
Created: 1/1/2026
Status: ❌ Closed

Base: main ← Head: bump-daily-hot-plugin-0.1.1

📝 Commits (1)

fce8ede bump daily-hot plugin to version 0.1.1

📊 Changes

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

View changed files

➕ Flying-Tom/daily-hot/daily-hot-0.1.1.difypkg (+0 -0)

📄 Description

Plugin Submission Form

1. Metadata

Plugin Author: @Flying-Tom
Plugin Name: daily-hot
Repository URL: https://github.com/Flying-Tom/Dify-DailyHot

2. Submission Type

New plugin submission
Version update for existing plugin

3. Description

Daily-Hot is a Dify plugin that aggregates trending topics from 40+ sources via the DailyHotApi and exposes them through a lightweight Python runner for downstream querying.

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/1837 **Author:** [@Flying-Tom](https://github.com/Flying-Tom) **Created:** 1/1/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `bump-daily-hot-plugin-0.1.1` --- ### 📝 Commits (1) - [`fce8ede`](https://github.com/langgenius/dify-plugins/commit/fce8ede114217c2a36199c3b8f822f6d8e266ce8) bump daily-hot plugin to version 0.1.1 ### 📊 Changes **1 file changed** (+0 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `Flying-Tom/daily-hot/daily-hot-0.1.1.difypkg` (+0 -0) </details> ### 📄 Description # Plugin Submission Form ## 1. Metadata  - **Plugin Author**: @Flying-Tom - **Plugin Name**: daily-hot - **Repository URL**: https://github.com/Flying-Tom/Dify-DailyHot ## 2. Submission Type - [x] New plugin submission - [ ] Version update for existing plugin ## 3. Description  Daily-Hot is a Dify plugin that aggregates trending topics from 40+ sources via the DailyHotApi and exposes them through a lightweight Python runner for downstream querying. ## 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  ### 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>