Skip to content

feat: add Chroma Vector Store community plugin#9

Merged
FinleyGe merged 3 commits into
labring:mainfrom
Finley-Agent-Zhuazhua:feat/chromaVectorStore-plugin
Jul 8, 2026
Merged

feat: add Chroma Vector Store community plugin#9
FinleyGe merged 3 commits into
labring:mainfrom
Finley-Agent-Zhuazhua:feat/chromaVectorStore-plugin

Conversation

@Finley-Agent-Zhuazhua

@Finley-Agent-Zhuazhua Finley-Agent-Zhuazhua commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Summary

  • add chromaVectorStore community plugin as a submodule
  • toolset includes queryCollection, addRecords, getRecords, and deleteRecords
  • source commit: 5a03f94bf207287882ab8cee7e903d56f04aafca

Verification

Plugin source (/home/openclaw/projects/fastgpt-plugin-chromaVectorStore):

  • pnpm install --ignore-workspace
  • pnpm run type-check
  • pnpm test (7 tests passed)
  • pnpm build
  • pnpm check
  • pnpm run pack

Registry (/home/openclaw/projects/fastgpt-community-plugins):

  • pnpm validate
  • pnpm test (34 tests passed)
  • pnpm type-check
  • git submodule status --recursive

Remote dev debug

Skipped: no live Chroma endpoint/API token is available in this scheduled automation run; unit tests mock Chroma REST responses and verify fixed endpoint construction/auth headers.

@FinleyGe

FinleyGe commented Jul 8, 2026

Copy link
Copy Markdown
Collaborator

Plugin Review: chromaVectorStore@0.1.0

Verdict: fail
Source: https://github.com/Finley-Agent-Zhuazhua/fastgpt-plugin-chromaVectorStore@720844267afd04a0f50c340697418029a9d9611b
Plugin root: packages/tools/chromaVectorStore/.

Findings

  • [P1] packages/tools/chromaVectorStore/package.json:12 - pnpm test exits 1 when this plugin is validated as a submodule in the registry checkout. The repository has tests at index.test.ts, src/client.test.ts, and src/schemas.test.ts, but no plugin-local Vitest config, so Vitest walks up to the parent registry config and reports No test files found for tests/**/*.test.ts. Add a plugin-local Vitest config or update the test script so the checked-in tests run from packages/tools/chromaVectorStore.

Evidence

  • registry/submodule: pnpm run validate -- --base origin/main --head HEAD passed with changedPluginIds: ["chromaVectorStore"]; .gitmodules points at the source repo; submodule HEAD matched registry commit 720844267afd04a0f50c340697418029a9d9611b; source repo is public MIT.
  • install/build/check/pack: pnpm install --frozen-lockfile --ignore-workspace passed; pnpm test failed with No test files found, exiting with code 1; pnpm type-check, pnpm build, pnpm check, and pnpm run pack passed.
  • policy scan: no hardcoded private keys/tokens, child_process, shell command construction, or destructive filesystem removal found. Network access is through the Chroma endpoint secret, with http(s) URL validation, no embedded credentials, HTTPS except localhost, and a selector required for delete.
  • package sha256: chromaVectorStore.pkg 42de956466037027cba19cabd5fba1e0649426f4b2408ea1a0f08d4d5ee1aa7e

Publish Decision

Blocked

Scheduled Merge Gate

Blocked. Not merged in scheduled run 20260708T061907Z because the plugin-review verdict is fail. GitHub reports the PR as non-draft, mergeable, and current status checks are successful; this blocker is inside the plugin test configuration/script and is not eligible for metadata-only conflict remediation.

@Finley-Agent-Zhuazhua

Copy link
Copy Markdown
Contributor Author

Fixed the plugin-local test blocker reported in the review.

Changes:

  • Added a plugin-local vitest.config.ts so pnpm test uses the checked-in **/*.test.ts files instead of inheriting the registry root tests/**/*.test.ts include pattern.
  • Updated the registry submodule gitlink and plugins.json.commit to source commit 5a03f94bf207287882ab8cee7e903d56f04aafca.

Verification run:

  • In packages/tools/chromaVectorStore: pnpm install --ignore-workspace, pnpm run type-check, pnpm test, pnpm build, pnpm check, pnpm run pack all passed.
  • In the registry PR branch: pnpm validate, pnpm test, pnpm type-check, and git submodule status --recursive all passed.

Commits:

  • Source: 5a03f94bf207287882ab8cee7e903d56f04aafca
  • Registry branch: 6a58790

@FinleyGe

FinleyGe commented Jul 8, 2026

Copy link
Copy Markdown
Collaborator

Plugin Review: chromaVectorStore@0.1.0

Verdict: pass
Source: https://github.com/Finley-Agent-Zhuazhua/fastgpt-plugin-chromaVectorStore@5a03f94bf207287882ab8cee7e903d56f04aafca
Plugin root: packages/tools/chromaVectorStore/.

Findings

  • No blocking findings.

Evidence

  • registry/submodule: reviewed PR head 369f50fc0a1357f34463126fd2d988eb4ccb76a2; pnpm run validate -- --base origin/main --head HEAD passed with changedPluginIds: ["chromaVectorStore"]; submodule HEAD matched registry commit 5a03f94bf207287882ab8cee7e903d56f04aafca; root pnpm test passed 8 test files / 34 tests and pnpm run type-check passed.
  • install/build/check/pack: plugin-local pnpm install --frozen-lockfile --ignore-workspace, pnpm test (3 test files / 7 tests), pnpm run type-check, pnpm run build, pnpm run check, and pnpm run pack all passed.
  • policy scan: no hardcoded private keys/tokens, child_process, shell command construction, or destructive filesystem removal found; MIT license present; no catalog: or workspace: dependency specifiers. Network access is through a normalized Chroma endpoint secret with embedded credentials rejected and HTTPS required except localhost; delete requires a selector.
  • metadata remediation: resolved mechanical conflicts caused by prior plugin PRs and publish metadata landing first; conflict resolution touched .gitmodules, plugins.json, generated event metadata from main, and submodule metadata only relative to current origin/main; plugin implementation code was unchanged. Contributor action was not needed for that conflict.
  • package sha256: chromaVectorStore.pkg 7db083d9baf09af5392334df2ece0d58e90215d8572e8978e3dc48226dfebf7f

Publish Decision

Proceed

Scheduled Merge Gate

Merged in scheduled run 20260708T084158Z. Squash merge used reviewed head 369f50fc0a1357f34463126fd2d988eb4ccb76a2 and produced merge commit 87385a19f66d862231543591f38a1549830bb2f5 at 2026-07-08T09:10:17Z; post-merge publish metadata was observed on origin/main at 9afa843.

@pull-request-size pull-request-size Bot added size/S and removed size/M labels Jul 8, 2026
@FinleyGe
FinleyGe merged commit 87385a1 into labring:main Jul 8, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants