msoukhomlinov/n8n-nodes-hudu v2.12.2 on GitHub

[2.12.2] - 2026-09-13

All 21 lint errors cleared — the repo's own lint gate is green again (issue #50). Ten @n8n/community-nodes/require-node-api-error sites, five no-unused-vars bindings in ai-tools/runtime.ts, two description-casing errors, and three HuduAiTools node-shape errors (missing subtitle, continueOnFail() not handled, node-usable-as-tool).
Node-aware errors are preserved instead of re-wrapped. The top-level catch in Hudu.node.ts, assets.handler.ts, asset_passwords.handler.ts and both asset_layouts option loaders now rethrow an existing NodeApiError/NodeOperationError unchanged, so local validation and configuration failures are no longer misclassified as Hudu API failures and API failures keep their HTTP status and response context. The ruleset has no typed-rethrow exemption, so each rethrow carries a scoped, reasoned eslint-disable.
assetFieldUtils.ts validation branches throw NodeOperationError(node, …) and the helper takes a node: INode parameter, matching the n8n-Cloud-verifiable n8n-nodes-hudu-core edition.
.remember/** is excluded from lint — gitignored local tool scratch files are not package source.

public_photos descriptions name the slug field as id, matching IPublicPhoto.id and the API response (raised in review of #51). The casing rule's autofix would have written ID, which is not a key in the response.
The Publish workflow uses npm install instead of npm ci. package-lock.json is gitignored here, so npm ci always failed on a clean checkout — every Publish run from v2.8.1 to v2.12.1 stopped before build, lint and publish. This matches how n8n-nodes-hudu-core publishes.
The publish lint no longer fails on package.json shape rules. @n8n/node-cli (unpinned, no committed lockfile, so CI takes the newest) has extended the community-nodes recommended set onto package.json since 0.47, which activates no-runtime-dependencies and valid-peer-dependencies there. This edition cannot satisfy those two by design — it ships the LangChain runtime and declares @langchain/core + @n8n/ai-utilities as peers, which is exactly why it is not n8n-Cloud-verifiable. Both rules are now off for package.json only; every other rule still runs.