Skip to content

fix(community-package,user): accept scoped names, drop verify, add delete transfer - #30

Merged
SomeoneWithOptions merged 1 commit into
mainfrom
fix/community-package-user
Oct 22, 2026
Merged

SomeoneWithOptions merged 1 commit into
mainfrom
fix/community-package-user

Conversation

@SomeoneWithOptions

Copy link
Copy Markdown
Owner

Spec drift fixes for community packages and users (upstream Public API 1.1.1, brief 07).

Community packages

  • Scoped names: install accepts n8n-nodes-<name> and @<scope>/n8n-nodes-<name> (spec: "Scoped names use the @[author]/n8n-nodes- form"). Empty scope, a bare prefix and nested paths are still rejected before any request. Update/uninstall already escape @scope/name as one path segment (%2F); tests now cover scoped names on install too.
  • verify removed: the spec dropped verify from the install/update bodies, and the instance setting now controls unverified installs. The client no longer sends it. --verify still parses so scripts don't break, but it is hidden and prints a deprecation on stderr (stdout/JSON unaffected).
  • Update without --version: the spec marks the PATCH body optional, so it still sends no body and n8n updates to the latest allowed version. Help and the confirmation prompt now say so. --version help mentions dist-tags (latest, beta).

Users

  • --offset deprecated: GET /users declares no offset. The client no longer sends it; the CLI flag is hidden, ignored and points to --cursor.
  • user delete --transfer-to-project PROJECT_ID: sends the new transferId query param. An empty or whitespace-padded value is rejected before the request. The confirmation prompt states what happens to the user's workflows and credentials: deleted without the flag, moved to the named project with it. JSON output adds transferProjectId.
  • Role help: lists global:admin, global:member, global:chatUser or a custom role slug. There is no enum, so nothing broke.

Verification

Checked on the live instance (--context admin, read-only):

  • n8n user list --limit 1 --output json with --offset 0 / 1 / 2 / 1000 returned the same first user and the same nextCursor. The server ignores offset (the cursor carries its own offset), so the flag was deprecated rather than kept.

From the spec only, not tested on a live server:

  • scoped install names, dropping verify, the body-less update, transferId, role slugs.
  • No install/update/uninstall or user delete was run live. Server acceptance of %2F-encoded scoped names in the update/uninstall path is still unconfirmed.

Tests

  • Client: scoped install body, scoped update/uninstall escaped paths, no verify in bodies, transferId only when set, list never sends offset.
  • CLI: deprecated --verify / --offset parse, warn on stderr, aren't sent, are hidden from help, and leave stdout JSON clean; delete confirmation text with and without a transfer; --yes required non-interactively; empty/padded transfer IDs rejected before transport.
  • make docs + make check green.

🤖 Generated with Claude Code

@SomeoneWithOptions
SomeoneWithOptions merged commit 329e1bb into main Oct 22, 2026
4 checks passed
@SomeoneWithOptions
SomeoneWithOptions deleted the fix/community-package-user branch October 22, 2026 01:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant