[Marketplace] Updating author, name and changelog resulted in duplicated plugin entries #510

Closed
opened 2026-02-22 17:31:17 -05:00 by yindo · 1 comment
Owner

Originally created by @LiaoYFBH on GitHub (Feb 9, 2026).

Hi Dify team,

I would like to ask for guidance regarding an unexpected duplicated plugin entry after a recent version update.

Background

A few days ago, I submitted a PR to update an existing plugin, mainly updating the changelog and author information:

This PR was successfully merged.

My original intention was to publish a new version of the same plugin. However, after the merge, I noticed that the plugin previously published under the lyf / ernie-paddle-aistudio-api namespace is now shown in the Marketplace as a separate standalone plugin, instead of being treated as an older version of the updated plugin.

As a result, the Marketplace currently shows two separate plugin entries that provide the same functionality:

  • lyf / ernie-paddle-aistudio-api (older plugin, standalone entry)
  • paddle-aistudio / ernie-paddle-aistudio (new plugin, actively maintained)
Image

Problem

Because the Marketplace treats different publisher / plugin_id paths as separate plugins, both entries are visible in search results. This causes user confusion, as users may mistakenly install the outdated lyf version.

At this point, my goal is to remove or retire the standalone plugin entry under the lyf / ernie-paddle-aistudio-api namespace, so that only the current plugin remains visible as the canonical one.

Main Question

Given this situation, I would like to ask:

What is the correct or supported way to delete, unpublish, or retire the old plugin under the lyf / ernie-paddle-aistudio-api namespace from the Marketplace?

Notes

  • The lyf / ernie-paddle-aistudio-api plugin is no longer maintained.
  • The paddle-aistudio / ernie-paddle-aistudio plugin is actively maintained and should be considered the canonical version.
  • I understand that full deletion may not be supported; I am mainly looking for official guidance on how this situation should be handled.

Thank you very much for your time and guidance.

Best regards

Originally created by @LiaoYFBH on GitHub (Feb 9, 2026). Hi Dify team, I would like to ask for guidance regarding an unexpected duplicated plugin entry after a recent version update. ### Background A few days ago, I submitted a PR to update an existing plugin, mainly updating the changelog and author information: - PR: https://github.com/langgenius/dify-plugins/pull/2024 This PR was successfully merged. My original intention was to publish a **new version of the same plugin**. However, after the merge, I noticed that the plugin previously published under the `lyf / ernie-paddle-aistudio-api` namespace is now shown in the Marketplace as a **separate standalone plugin**, instead of being treated as an older version of the updated plugin. As a result, the Marketplace currently shows two separate plugin entries that provide the same functionality: - `lyf / ernie-paddle-aistudio-api` (older plugin, standalone entry) - `paddle-aistudio / ernie-paddle-aistudio` (new plugin, actively maintained) <img width="1199" height="692" alt="Image" src="https://github.com/user-attachments/assets/b71acdb6-b035-40d4-ae59-38b123ad01b0" /> ### Problem Because the Marketplace treats different `publisher / plugin_id` paths as separate plugins, both entries are visible in search results. This causes user confusion, as users may mistakenly install the outdated `lyf` version. At this point, my goal is to **remove or retire the standalone plugin entry under the `lyf / ernie-paddle-aistudio-api` namespace**, so that only the current plugin remains visible as the canonical one. ### Main Question Given this situation, I would like to ask: **What is the correct or supported way to delete, unpublish, or retire the old plugin under the `lyf / ernie-paddle-aistudio-api` namespace from the Marketplace?** ### Notes - The `lyf / ernie-paddle-aistudio-api` plugin is no longer maintained. - The `paddle-aistudio / ernie-paddle-aistudio` plugin is actively maintained and should be considered the canonical version. - I understand that full deletion may not be supported; I am mainly looking for official guidance on how this situation should be handled. Thank you very much for your time and guidance. Best regards
yindo closed this issue 2026-02-22 17:31:19 -05:00
Author
Owner

@crazywoola commented on GitHub (Feb 11, 2026):

Removed :)

@crazywoola commented on GitHub (Feb 11, 2026): Removed :)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-plugins#510