Skip to content

Add n8n node release workflow with npm provenance#17

Open
pmbrull wants to merge 2 commits intomainfrom
task/prepare-n8n-node-for-publishing-5473245f
Open

Add n8n node release workflow with npm provenance#17
pmbrull wants to merge 2 commits intomainfrom
task/prepare-n8n-node-for-publishing-5473245f

Conversation

@pmbrull
Copy link
Copy Markdown
Contributor

@pmbrull pmbrull commented Apr 1, 2026

Summary

  • Add dedicated release workflow (ai-sdk-release-n8n.yml) for publishing the n8n community node to npm with --provenance flag via OIDC trusted publishing, triggered by n8n-v* tags or workflow_call
  • Integrate n8n release into the main release workflow, sequenced after TypeScript SDK so the @openmetadata/ai-sdk dependency is available on npm
  • Add @n8n/node-cli as devDependency (required for n8n verified node process) and update CI to handle the eslint peer dependency conflict with --legacy-peer-deps
  • Add missing package metadata (author, repository.directory) for proper npm listing

Closes #498

Test plan

  • Verify CI passes (lint + build for n8n node)
  • Verify make check-versions still passes
  • After merge, test standalone release with make tag-n8n + push tag
  • Configure npm trusted publisher on npmjs.com: repo owner, repo name, workflow ai-sdk-release-n8n.yml
  • After first publish, verify provenance badge appears on npm package page

pmbrull and others added 2 commits April 1, 2026 08:56
Prepare the n8n community node for publishing to npm by adding:
- Release workflow (ai-sdk-release-n8n.yml) with OIDC-based provenance
  publishing, triggered by n8n-v* tags or workflow_call
- n8n release job in the main release workflow, sequenced after the
  TypeScript SDK to ensure the dependency is available on npm
- @n8n/node-cli devDependency (required for n8n verified node process)
- Package metadata: author field, repository directory for monorepo
- CI updated to use --legacy-peer-deps for @n8n/node-cli compatibility

Closes #498

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Address n8n verification requirements based on real review feedback:
- Use NodeConnectionTypes.Main instead of string literals
- Add usableAsTool: true for AI agent workflow compatibility
- Add icon to credential class with dedicated credential icon
- Create codex metadata (AISdkAgent.node.json) with categories and aliases
- End all description fields with period (n8n style requirement)
- Fix continueOnFail() to use NodeApiError.message consistently
- Update build script to copy credential icons and codex to dist/
- Add @n8n/scan-community-package to CI and post-publish verification

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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