Skip to content

chore(n8n): Release 1.0.1 through npm trusted publishing - #39

Merged
deanzaka merged 1 commit into
masterfrom
chore/n8n-1.0.1
Nov 18, 2026
Merged

deanzaka merged 1 commit into
masterfrom
chore/n8n-1.0.1

Conversation

@deanzaka

@deanzaka deanzaka commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • Bump n8n-nodes-taskade to 1.0.1 (package.json, package-lock.json, CHANGELOG.md). No change to the node.
  • Update the auth note in publish-n8n.yml: a token for a new package must cover all packages, and trusted publishing is now set up.

Why

1.0.0 went out on 2026-11-18 with a temporary npm token. The npm trusted publisher (taskade/integrations, publish-n8n.yml) is saved but shows "Pending validation": npm needs one publish through it before 2026-11-20 08:08, or it drops the connection. The NPM_TOKEN repository secret is already deleted, so this release must use OIDC.

After merge

Push the tag n8n-v1.0.1 on the merge commit. Then revoke the temporary npm token.

1.0.1 has no change to the node. It is the first release without an npm
token, which validates the trusted publisher that npm set up on 2026-11-18
(it must publish once before 2026-11-20).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@deanzaka
deanzaka merged commit ed52629 into master Nov 18, 2026
5 checks passed
@deanzaka
deanzaka deleted the chore/n8n-1.0.1 branch November 18, 2026 08:11
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