Repository navigation
docs: add maintainer credit for Dify plugin 0.2.1 - #5
Merged
Merged
Conversation
11 of 14 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Credit J.Jason (@JJasonSun) in the README and user-facing plugin/provider descriptions. Prepare version 0.2.1 without changing the existing plugin identity.
README and plugin/provider descriptions + Maintainer: J.Jason (@JJasonSun) author/name: derekwang2002/call_e (unchanged)Evidence
After: The 0.2.1 package includes the requested credit in all three places; 101 tests, compilation, and
git diff --checkpass.derekwang2002/call_eidentity. Only README, manifest, and provider metadata differ from 0.2.0; runtime source files and tool definitions are byte-for-byte unchanged. Manifest and project versions both equal 0.2.1.Merge Danger
Door: two-way
This changes attribution text and release metadata. Keep the published 0.2.0 package; release 0.2.1 as a separate asset/version.
Blast Radius: descriptions
No credential, call, workflow-output, or idempotency behavior changes. Real calls and Cloud installation were not rerun for this metadata-only update.