Skip to content

Fix n8n scanner lint failures for 0.2.2 - #5

Merged
ivodraginov-cloud merged 1 commit into
mainfrom
fix/0.2.2-scan-compliance
Nov 11, 2026
Merged

ivodraginov-cloud merged 1 commit into
mainfrom
fix/0.2.2-scan-compliance

Conversation

@ivodraginov-cloud

Copy link
Copy Markdown
Contributor

Why

0.2.1 published cleanly from GitHub Actions with provenance, but npx @n8n/scan-community-package n8n-nodes-batchdata@0.2.1 failed. The official scanner uses @n8n/eslint-plugin-community-nodes 0.40.0 and sets allowInlineConfig: false, so the eslint-disable comments that n8n-node lint accepted were ignored.

Changes

  • Move InputError throws out of catch blocks in catalogEngine.ts.
  • Credential test prefers helpers.httpRequest and falls back to the legacy helper (the only one ICredentialTestFunctions typings expose).
  • Rename the Custom API Call operation from "Make a Custom API Call" to "Make".
  • Bump to 0.2.2.

n8n-node lint, build, and all 40 tests passed. A local run of the official scanner's source and tarball lint also passed.

After merge, tag 0.2.2 to publish with provenance and replace 0.2.1 as latest.

The official scanner (@n8n/scan-community-package) uses plugin 0.40.0
and ignores eslint-disable comments. Move InputError throws out of
catch blocks, prefer httpRequest in the credential test with a
legacy fallback, and rename the Custom API Call operation to "Make".
Local source and tarball scans now pass.
@ivodraginov-cloud
ivodraginov-cloud merged commit df4029c into main Nov 11, 2026
1 check passed
@ivodraginov-cloud
ivodraginov-cloud deleted the fix/0.2.2-scan-compliance branch November 11, 2026 17:05
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.

2 participants