Repository navigation
fix(community-package,user): accept scoped names, drop verify, add delete transfer - #30
Merged
Merged
Conversation
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
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.
Spec drift fixes for community packages and users (upstream Public API 1.1.1, brief 07).
Community packages
installacceptsn8n-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/nameas one path segment (%2F); tests now cover scoped names on install too.verifyremoved: the spec droppedverifyfrom the install/update bodies, and the instance setting now controls unverified installs. The client no longer sends it.--verifystill parses so scripts don't break, but it is hidden and prints a deprecation on stderr (stdout/JSON unaffected).--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.--versionhelp mentions dist-tags (latest,beta).Users
--offsetdeprecated: GET /users declares nooffset. 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 newtransferIdquery 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 addstransferProjectId.global:admin,global:member,global:chatUseror 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 jsonwith--offset0 / 1 / 2 / 1000 returned the same first user and the samenextCursor. The server ignoresoffset(the cursor carries its own offset), so the flag was deprecated rather than kept.From the spec only, not tested on a live server:
verify, the body-less update,transferId, role slugs.%2F-encoded scoped names in the update/uninstall path is still unconfirmed.Tests
verifyin bodies,transferIdonly when set, list never sendsoffset.--verify/--offsetparse, warn on stderr, aren't sent, are hidden from help, and leave stdout JSON clean; delete confirmation text with and without a transfer;--yesrequired non-interactively; empty/padded transfer IDs rejected before transport.make docs+make checkgreen.🤖 Generated with Claude Code