docker-plugin_daemon - watcher.go:73: [ERROR]list installed plugins failed: plugin_unique_identifier is not valid #45

New Issue

Closed

opened 2026-02-16 00:19:19 -05:00 by yindo · 12 comments

yindo commented 2026-02-16 00:19:19 -05:00

Owner

Copy Link

Copy Source

Originally created by @jasonchaos on GitHub (Mar 17, 2025).

Self Checks

• This is only for bug report, if you would like to ask a question, please head to Discussions.
• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
• Please do not modify this template :) and fill in all the required fields.

Dify version

1.0.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Whenever I restart Docker container services (before the restart, all features work normally), I get an "Internal Server Error" when trying to edit models in the workflow. By debugging the network, I found that the API endpoint http://localhost/console/api/workspaces/current/model-providers/langgenius/tongyi/tongyi/models/parameter-rules?model=deepseek-v3 returns an error.

After investigating the issue, I discovered that the docker-plugin_daemon-1 container logs continuously show the error: watcher.go:73: [ERROR]list installed plugins failed: plugin_unique_identifier is not valid.

I have already set FORCE_VERIFYING_SIGNATURE to false in the .env file in the Docker directory and restarted the Docker containers, but the problem still persists.

✔️ Expected Behavior

docker-plugin_daemon-1 No error should occur.

❌ Actual Behavior

docker-plugin_daemon-1 watcher.go:73: [ERROR]list installed plugins failed: plugin_unique_identifier is not valid.

Originally created by @jasonchaos on GitHub (Mar 17, 2025). ### Self Checks - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.0.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Whenever I restart Docker container services (before the restart, all features work normally), I get an "Internal Server Error" when trying to edit models in the workflow. By debugging the network, I found that the API endpoint http://localhost/console/api/workspaces/current/model-providers/langgenius/tongyi/tongyi/models/parameter-rules?model=deepseek-v3 returns an error. After investigating the issue, I discovered that the docker-plugin_daemon-1 container logs continuously show the error: watcher.go:73: [ERROR]list installed plugins failed: plugin_unique_identifier is not valid. I have already set FORCE_VERIFYING_SIGNATURE to false in the .env file in the Docker directory and restarted the Docker containers, but the problem still persists. ### ✔️ Expected Behavior docker-plugin_daemon-1 No error should occur. ### ❌ Actual Behavior docker-plugin_daemon-1 watcher.go:73: [ERROR]list installed plugins failed: plugin_unique_identifier is not valid.  

yindo added the good first issue label 2026-02-16 00:19:19 -05:00

yindo closed this issue 2026-02-16 00:19:19 -05:00

yindo commented 2026-02-16 00:19:20 -05:00

Author

Owner

Copy Link

Copy Source

@dosubot[bot] commented on GitHub (Mar 17, 2025):

Hello, @jasonchaos! I'm here to help you with any bugs, questions, or contributions. Let's work on solving this issue together.

To resolve the "plugin_unique_identifier is not valid" error in the docker-plugin_daemon-1 logs, you can follow these steps:

1. Execute these SQL commands in the dify_plugin database to clear any invalid plugin entries:

   delete from plugin_installations where plugin_unique_identifier is not null;
   delete from plugin_declarations where plugin_unique_identifier is not null;
   delete from ai_model_installations where plugin_unique_identifier is not null;
   delete from plugins where plugin_unique_identifier is not null;
   

2. Clear the following plugin directories to remove any corrupted or invalid plugin data:

   • /app/storage/cwd/plugins/plugin
   • /app/storage/cwd/plugins/plugin-working
   • /app/storage/cwd/plugins/persistence
   • /app/storage/cwd/plugins/plugin-root

3. Update the manifest.yaml file and any .yaml files under the /provider path in your plugin project to ensure the author field is set to your GitHub ID.

4. Repackage the plugin and reinstall it to ensure all configurations are correct.

5. Restart the plugin daemon service to apply the changes.

These steps should help resolve the error and the resulting "Internal Server Error" when editing models in the workflow ^[1][2].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

@dosubot[bot] commented on GitHub (Mar 17, 2025): <!-- Greeting --> Hello, @jasonchaos! I'm here to help you with any bugs, questions, or contributions. Let's work on solving this issue together. <!-- Answer --> To resolve the "plugin_unique_identifier is not valid" error in the docker-plugin_daemon-1 logs, you can follow these steps: 1. Execute these SQL commands in the dify_plugin database to clear any invalid plugin entries: ```sql delete from plugin_installations where plugin_unique_identifier is not null; delete from plugin_declarations where plugin_unique_identifier is not null; delete from ai_model_installations where plugin_unique_identifier is not null; delete from plugins where plugin_unique_identifier is not null; ``` 2. Clear the following plugin directories to remove any corrupted or invalid plugin data: - `/app/storage/cwd/plugins/plugin` - `/app/storage/cwd/plugins/plugin-working` - `/app/storage/cwd/plugins/persistence` - `/app/storage/cwd/plugins/plugin-root` 3. Update the `manifest.yaml` file and any `.yaml` files under the `/provider` path in your plugin project to ensure the `author` field is set to your GitHub ID. 4. Repackage the plugin and reinstall it to ensure all configurations are correct. 5. Restart the plugin daemon service to apply the changes. These steps should help resolve the error and the resulting "Internal Server Error" when editing models in the workflow ^{[[1]](https://github.com/langgenius/dify/issues/14918)}^{[[2]](https://github.com/langgenius/dify-docs/blob/main/jp/plugins/faq.md)}. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- ^{Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/2601aef5-eb69-43bb-8c3f-097f83eb1d0b?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/2601aef5-eb69-43bb-8c3f-097f83eb1d0b?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/2601aef5-eb69-43bb-8c3f-097f83eb1d0b?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/2601aef5-eb69-43bb-8c3f-097f83eb1d0b?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/2601aef5-eb69-43bb-8c3f-097f83eb1d0b?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/2601aef5-eb69-43bb-8c3f-097f83eb1d0b?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/2601aef5-eb69-43bb-8c3f-097f83eb1d0b?feedback_type=other)}

yindo commented 2026-02-16 00:19:20 -05:00

Author

Owner

Copy Link

Copy Source

@jasonchaos commented on GitHub (Mar 17, 2025):

What I've Tried:
I've already attempted to fix this error through the following methods:

1. Executed these SQL commands in the dify_plugin database to clear any invalid plugin entries;
2. Clear the following plugin directories to remove any corrupted or invalid plugin data;
   However, after reinstalling plugins and restarting Docker, the same issue occurs again. I need a permanent solution to completely resolve this problem. @dosu

@jasonchaos commented on GitHub (Mar 17, 2025): What I've Tried: I've already attempted to fix this error through the following methods: 1. Executed these SQL commands in the dify_plugin database to clear any invalid plugin entries; 2. Clear the following plugin directories to remove any corrupted or invalid plugin data; However, after reinstalling plugins and restarting Docker, the same issue occurs again. I need a permanent solution to completely resolve this problem. @dosu

yindo commented 2026-02-16 00:19:20 -05:00

Author

Owner

Copy Link

Copy Source

@dosubot[bot] commented on GitHub (Mar 17, 2025):

To permanently resolve the "plugin_unique_identifier is not valid" error, ensure that you modify the author field in the manifest.yaml file of your plugin project and in the .yaml files under the /provider path to match your GitHub ID. After making these changes, repackage the plugin and install the new plugin package. This should help in resolving the issue permanently ^[1][2].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

@dosubot[bot] commented on GitHub (Mar 17, 2025): <!-- Answer --> To permanently resolve the "plugin_unique_identifier is not valid" error, ensure that you modify the `author` field in the `manifest.yaml` file of your plugin project and in the `.yaml` files under the `/provider` path to match your GitHub ID. After making these changes, repackage the plugin and install the new plugin package. This should help in resolving the issue permanently ^{[[1]](https://github.com/langgenius/dify-docs/blob/main/jp/plugins/faq.md)}^{[[2]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/plugins/faq.md)}. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- ^{Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/8af848f8-ca79-431a-9901-191f0af84180?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/8af848f8-ca79-431a-9901-191f0af84180?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/8af848f8-ca79-431a-9901-191f0af84180?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/8af848f8-ca79-431a-9901-191f0af84180?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/8af848f8-ca79-431a-9901-191f0af84180?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/8af848f8-ca79-431a-9901-191f0af84180?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/8af848f8-ca79-431a-9901-191f0af84180?feedback_type=other)}

yindo commented 2026-02-16 00:19:20 -05:00

Author

Owner

Copy Link

Copy Source

@jasonchaos commented on GitHub (Mar 17, 2025):

I am not using unverified third-party or self-developed plugins. I am only using the official plugins provided in the Marketplace. After following your instructions to modify the yaml file and restart the containers, the problem still persists with the same error.

Although temporarily clearing the plugin data from the database and removing plugin files from the directories, then reinstalling the previously cleared plugins through the Marketplace seems to work initially, the issue reoccurs after restarting Docker.

What should I do to permanently solve this problem?@dosu

@jasonchaos commented on GitHub (Mar 17, 2025): I am not using unverified third-party or self-developed plugins. I am only using the official plugins provided in the Marketplace. After following your instructions to modify the yaml file and restart the containers, the problem still persists with the same error. Although temporarily clearing the plugin data from the database and removing plugin files from the directories, then reinstalling the previously cleared plugins through the Marketplace seems to work initially, the issue reoccurs after restarting Docker. What should I do to permanently solve this problem?@dosu  

yindo commented 2026-02-16 00:19:20 -05:00

Author

Owner

Copy Link

Copy Source

@crazywoola commented on GitHub (Mar 17, 2025):

Have you try this one. https://github.com/langgenius/dify/issues/16009

@crazywoola commented on GitHub (Mar 17, 2025): Have you try this one. https://github.com/langgenius/dify/issues/16009

yindo commented 2026-02-16 00:19:21 -05:00

Author

Owner

Copy Link

Copy Source

@exitNA commented on GitHub (Mar 18, 2025):

I followed the steps, but it still reported an error. However, I accidentally found that changing the name in mainifest.yaml to lowercase worked. @dosu.

@exitNA commented on GitHub (Mar 18, 2025): I followed the steps, but it still reported an error. However, I accidentally found that changing the `name` in `mainifest.yaml` to lowercase worked. @dosu.

yindo commented 2026-02-16 00:19:21 -05:00

Author

Owner

Copy Link

Copy Source

@Yeuoly commented on GitHub (Mar 18, 2025):

I am not using unverified third-party or self-developed plugins. I am only using the official plugins provided in the Marketplace. After following your instructions to modify the yaml file and restart the containers, the problem still persists with the same error.

Although temporarily clearing the plugin data from the database and removing plugin files from the directories, then reinstalling the previously cleared plugins through the Marketplace seems to work initially, the issue reoccurs after restarting Docker.

What should I do to permanently solve this problem?@dosu

It looks like you used self developed plugins as shown in your screenshot jasonchaos/xx, I'm not sure what you have modified, could you pls provides your db records in plugin_installations table?

@Yeuoly commented on GitHub (Mar 18, 2025): > I am not using unverified third-party or self-developed plugins. I am only using the official plugins provided in the Marketplace. After following your instructions to modify the yaml file and restart the containers, the problem still persists with the same error. > > Although temporarily clearing the plugin data from the database and removing plugin files from the directories, then reinstalling the previously cleared plugins through the Marketplace seems to work initially, the issue reoccurs after restarting Docker. > > What should I do to permanently solve this problem?[@dosu](https://github.com/dosu) > >  > >  It looks like you used self developed plugins as shown in your screenshot `jasonchaos/xx`, I'm not sure what you have modified, could you pls provides your db records in `plugin_installations` table?

yindo commented 2026-02-16 00:19:21 -05:00

Author

Owner

Copy Link

Copy Source

@jasonchaos commented on GitHub (Mar 18, 2025):

I am not using unverified third-party or self-developed plugins. I am only using the official plugins provided in the Marketplace. After following your instructions to modify the yaml file and restart the containers, the problem still persists with the same error.
Although temporarily clearing the plugin data from the database and removing plugin files from the directories, then reinstalling the previously cleared plugins through the Marketplace seems to work initially, the issue reoccurs after restarting Docker.
What should I do to permanently solve this problem?@dosu

It looks like you used self developed plugins as shown in your screenshot jasonchaos/xx, I'm not sure what you have modified, could you pls provides your db records in plugin_installations table?

The screenshot shows that following @sodu's suggestion in point 3:

"Update the manifest.yaml file and any .yaml files under the /provider path in your plugin project to ensure the author field is set to your GitHub ID."

I modified the relevant yaml files and database fields within Docker to change them to my GitHub ID. The plugins were downloaded from the official Marketplace.

@jasonchaos commented on GitHub (Mar 18, 2025): > > I am not using unverified third-party or self-developed plugins. I am only using the official plugins provided in the Marketplace. After following your instructions to modify the yaml file and restart the containers, the problem still persists with the same error. > > Although temporarily clearing the plugin data from the database and removing plugin files from the directories, then reinstalling the previously cleared plugins through the Marketplace seems to work initially, the issue reoccurs after restarting Docker. > > What should I do to permanently solve this problem?[@dosu](https://github.com/dosu) > >  > >  > > It looks like you used self developed plugins as shown in your screenshot `jasonchaos/xx`, I'm not sure what you have modified, could you pls provides your db records in `plugin_installations` table? The screenshot shows that following @sodu's suggestion in point 3: >> "Update the manifest.yaml file and any .yaml files under the /provider path in your plugin project to ensure the author field is set to your GitHub ID." I modified the relevant yaml files and database fields within Docker to change them to my GitHub ID. The plugins were downloaded from the official Marketplace.

yindo commented 2026-02-16 00:19:21 -05:00

Author

Owner

Copy Link

Copy Source

@jasonchaos commented on GitHub (Mar 18, 2025):

Have you try this one. langgenius/dify#16009

If clearing plugin settings is necessary to make plugins work properly again, then why can I immediately use plugins normally after cleaning and reinstalling them as suggested by sodu? Moreover, clearing plugin settings causes significant inconvenience for me as I would need to reconfigure many things.

@jasonchaos commented on GitHub (Mar 18, 2025): > Have you try this one. [langgenius/dify#16009](https://github.com/langgenius/dify/issues/16009) If clearing plugin settings is necessary to make plugins work properly again, then why can I immediately use plugins normally after cleaning and reinstalling them as suggested by sodu? Moreover, clearing plugin settings causes significant inconvenience for me as I would need to reconfigure many things.

yindo commented 2026-02-16 00:19:21 -05:00

Author

Owner

Copy Link

Copy Source

@filwu8 commented on GitHub (Mar 22, 2025):

I also encountered this problem. It kept showing that a plug-in was being installed for several days. I installed dozens of plug-ins and had no idea which one failed to install.

There is no error in the log, and all plugins are working properly.

@filwu8 commented on GitHub (Mar 22, 2025): I also encountered this problem. It kept showing that a plug-in was being installed for several days. I installed dozens of plug-ins and had no idea which one failed to install.  There is no error in the log, and all plugins are working properly.

yindo commented 2026-02-16 00:19:22 -05:00

Author

Owner

Copy Link

Copy Source

@Yeuoly commented on GitHub (Mar 30, 2025):

Have you try this one. langgenius/dify#16009

If clearing plugin settings is necessary to make plugins work properly again, then why can I immediately use plugins normally after cleaning and reinstalling them as suggested by sodu? Moreover, clearing plugin settings causes significant inconvenience for me as I would need to reconfigure many things.

I'm not sure what suggestions sudo gives you, but in your case, this error occurs only if the plugin unique identifier dose not meet ^(?:([a-z0-9_-]{1,64})\/)?([a-z0-9_-]{1,255}):([0-9]{1,4})(\.[0-9]{1,4}){1,3}(-\w{1,16})?@[a-f0-9]{32,64}$, I cannot tell why if I do not know what you have modified and what's the ID is

I made this change https://github.com/langgenius/dify-plugin-daemon/pull/163/files to better error message

@Yeuoly commented on GitHub (Mar 30, 2025): > > Have you try this one. [langgenius/dify#16009](https://github.com/langgenius/dify/issues/16009) > > If clearing plugin settings is necessary to make plugins work properly again, then why can I immediately use plugins normally after cleaning and reinstalling them as suggested by sodu? Moreover, clearing plugin settings causes significant inconvenience for me as I would need to reconfigure many things. I'm not sure what suggestions sudo gives you, but in your case, this error occurs only if the plugin unique identifier dose not meet `^(?:([a-z0-9_-]{1,64})\/)?([a-z0-9_-]{1,255}):([0-9]{1,4})(\.[0-9]{1,4}){1,3}(-\w{1,16})?@[a-f0-9]{32,64}$`, I cannot tell why if I do not know what you have modified and what's the ID is I made this change https://github.com/langgenius/dify-plugin-daemon/pull/163/files to better error message

yindo commented 2026-02-16 00:19:22 -05:00

Author

Owner

Copy Link

Copy Source

@Lucky-watermelon commented on GitHub (Jul 28, 2025):

I followed the steps, but it still reported an error. However, I accidentally found that changing the in to lowercase worked. @dosu.name``mainifest.yaml

good

@Lucky-watermelon commented on GitHub (Jul 28, 2025): > I followed the steps, but it still reported an error. However, I accidentally found that changing the in to lowercase worked. [@dosu](https://github.com/dosu).`name``mainifest.yaml` good

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

build/fix-serverless-runtime-error-propagation

gh-pages

build/test-document2

build/test-document

build/onboarding-ui

build/slim-extract

codex/depot-builds

codex/mac-runner-benchmark

feat/storage-path-prefix

feat/multi-db-user

feat/slim-action

deploy/dev

feat/dify-cli

feat/add-e2e

build/pg-bouncer

codex/add-multimodal-rerank-and-embedding-apis

refactor/local-runtime

build/multimodal-embeddings

codex/refactor-routine.submit-label-handling

codex/refactor-service-layer-based-on-provided-plan

feat/trigger-response

feat/trigger

build/trigger

deploy/trigger-dev

codex/remove-claude-code-reviewer-from-github-ci

codex/add-manifest-check-to-upload-endpoint

feat/no-root-dockerfile

fix/json-schema

fix/blocking-anthorized-langgenius

454-bump-cli-template

build/datasource

feat/datasource

bump-cloud-kit

feat/rag-tag

fix/change-session-not-found-to-400

feat/plugin-readme

add-claude-github-actions-1756274550417

docs/comprehensive-development-documentation

chore/remove-json-schema-validation-error

71cef04

fix/missing-parameter-type

fix/sessions-log

fix/template.env

bump/go-git

build/oauth

feat/oauth-refresh-token

feat/plugin-oauth

feat/tool-oauth-cli

build/plugin-oauth

feat/readme-i18n

fix/memory-leak

feat/icon-dark

feat/default-icon

plugin_launch_concurent

feat/collect-active-requests

feat/dark-icon

feat/support-structured-llm-output

feat/dynamic-selector

fix/reduce-logs

feat/decode-plugin-package

feat/db-extras

fix/backwards-invocation-overflow

feat/length-prefixed-chunking

fix/http-request-reader-header

chore/unify-configurations

fix/hardcoded-serverless-runtime-timeout

fix/cmd

fix/signature

refactor/implement-gen-routes

fix/redis-lock

refactor/codegen

feat/add-authorized-category

chore/style

feat/run-plugin-cli

reduce/run-once

feat/reinstall-serverless-runtime

feat/support-setup-process

fix/apply-stdio-buffer-size

chore/add-warning-messages-to-installed-bucket

feat/repo

enhance/stdio

feat/make-buffer-size-configurable

fix/moderation-init

fix/only-validate-profile-on-quick-mode

feat/support-quick-init-plugins

refactor/oauth-parameters

feat/oauth

refactor/simplify-plugin-invocation

test/integration-test-for-plugins

fix/backwards-compatible-to-llm-result-chunk

feat/auto-scale

enhance/reduce-ci-tests

fix/cli-ci

enhance/removes-llm-result-prompt-messages

fix/disable-benchmark-logs

benchmark/local-runtime

chore/remove-useless-benchmark

feat/benchmark

feat/fetch-app-info

fix/windows-remap-assets

fix/skip-hidden-file

feat/stream-tool-blob-message

fix/path-travel

feat/template-add-ci

enhance/version-compare

feat/sign-apple-os-cli

feat/support-minimal-dify-version-required

refactor/stdip

feat/add-serverless-connector-launching-timeout

fix/remove-prompt_messages-from-llm-result-chunk

feat/standardize-plugin-sdk-versions

chore/update-docs-and-refine-wording

update/readme-cli

fix/infinity-environment-setup

fix/cbor-unmarshaling

fix/use-aws-iam-baseendpoint

fix/lost-query-params-in-endpoint

fix/tiktoken

cohre/update-readme

fix/redis-tests

fix/friendly-identity

fix/marshal-any-map

chore/upgrade-ants

fix/graceful-precompile

enhance/tiktoken

feat/graceful-shutdown

fix/close-serverless-response

fix/correct-cli-guide

fix/plugin-active-log

fix/remove-proxy-args-from-uv

fix/endpoint-hook-url

fix/ci-credentials

feat/disable-gevent

fix/add-gcc

fix/hardcoded-endpoint-timeout

fix/bump-cli-sdk-version

fix/deadloop-when-redis-disconnect

fix/enhence/speed-up-environment-setup

enhance/introduce-uv

fix/change-default-db

fix/deadlock

readme

chore/env.example

feat/add-action-in-url

fix/add-more-pip-args

fix/optimize-local-heartbeat

optimize/db-init

fix/optimize-internal-server-error

fix/increase-default-plugin-max-execution-timeout

fix/force-patch-older-version

enhance/increase-installing-process

LICENSE

fix/set-user-id-to-unrequired

fix/max-launching-concurrent

improve/error-handing-in-serverless

refactor/json-unmarshaler-enhancement

fix/add-pip-mirror-url

enhance/serverless-connector

0.6.5

0.6.4

0.6.3

0.6.2

0.6.1

0.6.0

0.5.9

0.5.8

0.5.7

0.5.6

0.5.5

0.5.4

0.5.3

0.5.2

0.5.1

0.5.0

0.4.1

0.4.0

0.3.3

0.3.2

0.3.1

0.3.0

0.3.0b1

0.2.0

0.1.3

0.1.2

0.1.1

0.1.0

0.0.10

0.0.9

0.0.8

0.0.7

0.0.6

0.0.5

0.0.4

0.0.3

0.0.2

0.0.1

0.0.1-beta.23

0.0.1-beta.22

0.0.1-beta.21

0.0.1-beta.20

0.0.1-beta.19

0.0.1-beta.18

0.0.1-beta.17

0.0.1-beta.16

0.0.1-beta.15

0.0.1-beta.14

0.0.1-beta.13

0.0.1-beta.12

0.0.1-beta.11

0.0.1-beta.10

0.0.1-beta.9

0.0.1-beta.8

0.0.1-beta.7

0.0.1-beta.6

0.0.1-beta.5

0.0.1-beta.4

0.0.1-beta.3

0.0.1-beta.2

0.0.1-beta.1

Labels

Clear labels

Windows

bug

cmd

documentation

enhancement

go

good first issue

plugin-daemon

pull-request

Mirrored from GitHub Pull Request

question

No Label good first issue

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

yindo

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: langgenius/dify-plugin-daemon#45