Repository navigation
Update Ace Data Cloud nano-banana to 0.0.5: service discovery and key setup - #3404
crazywoola merged 3 commits into
Conversation
crazywoola
left a comment
crazywoola
left a comment
There was a problem hiding this comment.
Verified publication eligibility for cd46799: Pre Check Plugin and PR Risk Label both passed for this revision, and this PR is open and ready for review. Inspected the submitted manifest, README, and relevant tool/provider source: the plugin provides Nano Banana image generation, editing, and task retrieval, with no Web3 functionality found. This approval covers publication eligibility.
|
Thank you for your contributions to the Marketplace, and for the work you have put into these submissions. Looking at the full set of plugins published under acedatacloud (acedatacloud, face, fish, flux, gpt_image, grok, happyhorse, kling, midjourney, minimax, nano-banana, qwen-image, seedance, seedream, serp, suno, veo, wan), most of them are effectively the same kind of plugin: a thin wrapper around the same Ace Data Cloud API with the same credential — one plugin per upstream model or service, even though the gateway already exposes every model through a single OpenAI-compatible endpoint and one API key. As individual listings, they duplicate the same functionality and the same maintenance surface. Under our marketplace curation policy, a series of near-identical or template-cloned plugins from one author is not acceptable: it multiplies the maintenance work (every security fix, dependency bump and API change has to be repeated across all of them), and these listings occupy a large share of the marketplace page, which hurts discoverability for everyone. Could you please consolidate these into a single plugin within the next two weeks (by 2026-11-24)? Once the consolidated plugin is submitted, please close the remaining single-purpose submissions, and we will help deprecate the already-published individual listings so that users are pointed to the consolidated plugin. For gateway-style plugins specifically, please also note our listing bar going forward: "one OpenAI-compatible endpoint + one key" on its own is not sufficient for a new plugin. A gateway plugin should demonstrate at least one differentiated enhancement beyond plain proxying — for example model routing, metering/billing, fallback/disaster recovery, quality evaluation, or caching — otherwise it should be integrated into the consolidated multi-model plugin instead of being published separately. We will gladly prioritize the review of the consolidated submission. Thanks for your understanding, and thanks again for contributing to the Marketplace! |
Plugin Submission
Plugin information
acedatacloud)Submission type
What changed
Makes the independent service card explicitly identify Ace as the integration provider (
NanoBanana by Ace Data Cloud), adds an official supported Marketplace category tag, and links the credential form directly to Applications with the existing accepted four-field attribution format. English and Simplified Chinese guides retain the real dated screenshots and complete key/first-use flow. Runtime Python, tool identifiers, schemas, dependencies, permissions, network destination and existing logo bytes are unchanged. No breaking workflow changes or claim of third-party official endorsement.Source PR: AceDataCloud/NanoBananaDify#10 (merged). This PR adds exactly one new
.difypkg, retaining all existing versions and the stable plugin ID.Risk level
Required checks
.env, Git state, virtual environments, caches, tests, logs or IDE files.Security and privacy notes
The existing plugin sends the user's authorized inputs and API credential to fixed
https://api.acedata.cloud. API use follows current account service pricing. No arbitrary destination, shell, SQL, filesystem, browser automation, payment operation or new model fallback is introduced. Reference URLs are passed as inputs; the plugin does not fetch arbitrary references. The privacy policy describes data handling; screenshots redact identity and credentials. No new paid inference/media generation was sent for this release.Local validation
dify-plugin==0.9.1: 29 tests passed, including actual SDK registration; Ruff lint/format and diff checks passed.5a5abc069ab235c32f0d1fbf3e96c8ea0dd5cdf1466e8aaf0687c563304eb4c3; 701884 bytes.Reviewer notes
Ordinary installation of this new version and the new form/title screenshots have not been verified in a live workspace: the configured test Dify instance returns503. Historical real CE1.17.1 screenshots and existing same-task terminal/media/usage evidence remain dated in source; they are not claimed as new-version E2E. Dify Cloud is unverified. SDK/package checks do not replace host acceptance. The publisher will follow the normal signed Marketplace install/read-only history path after publication and workspace recovery, without a new paid generation.
The Developer Agreement box stays unchecked, as in the previously accepted updates (for example #3299); this PR does not sign or attest to a new agreement. If a separate human attestation is required, please identify the canonical agreement/action. AI assistance was used.
Release-guidance correction: AceDataCloud/NanoBananaDify#11 is merged. The packaged bilingual README now describes version behavior durably instead of claiming source approval is still pending. Only the two README files changed from this submission's first archive; runtime, permissions, schemas, dependencies and assets are byte-identical. The exact final archive was reloaded with the official SDK. No new version or duplicate submission was created.
Packaging cleanup: the release staging archive excludes non-runtime
.gitignoreand source-onlyCAPABILITIES.md; all retained files still match the verified merged source byte-for-byte. Existing runtime, dependencies, permissions and tutorial assets are unchanged. The cleaned archive was repackaged by the official CLI and loaded by the official SDK.