JDSS/mem0
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(n8n): publish under the scoped @mem0/n8n-nodes-mem0 name

Browse Source 
The unscoped `n8n-nodes-mem0` name is already taken on npm by an
unrelated publisher, so the CD workflow could never publish it. Move to
the `@mem0` scope, matching `@mem0/pi-agent-plugin` and
`@mem0/openclaw-mem0`, and add `publishConfig.access: public` since
scoped packages default to restricted.

n8n accepts scoped community packages: it strips the scope before
enforcing the `n8n-nodes-` prefix, the same shape as n8n's own
`@n8n/n8n-nodes-langchain`. Verified end to end on n8n 2.22.6 by
installing the packed tarball into the community-packages directory and
executing a workflow against node type `@mem0/n8n-nodes-mem0.mem0`.

The directory, workflow filenames, and the `n8n-nodes-mem0-v*` tag
prefix are unchanged. pnpm-lock.yaml needs no update: the pnpm v9 root
importer is anonymous and never recorded the package name.
This commit is contained in:
kartik-mem0
2026-07-29 17:01:49 +05:30
parent 7417f87252
commit a618939f00
6 changed files with 12 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
integrations/n8n-nodes-mem0/test/Mem0.node.test.ts
+1 -1
View File
@@ -20,7 +20,7 @@ function makeCtx(
opts: { continueOnFail?: boolean } = {},
): any {
const requests: any[] = [];
const node = { name: 'Mem0', type: 'n8n-nodes-mem0.mem0', typeVersion: 1 };
const node = { name: 'Mem0', type: '@mem0/n8n-nodes-mem0.mem0', typeVersion: 1 };
const ctx: any = {
getInputData: () => [{ json: {} }],
getCredentials: async () => ({ apiKey: 'm0-test', baseUrl: 'https://api.mem0.ai' }),