Repository navigation
chore(n8n): Release 1.0.1 through npm trusted publishing - #39
Merged
Merged
Conversation
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>
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.
Summary
n8n-nodes-taskadeto 1.0.1 (package.json,package-lock.json,CHANGELOG.md). No change to the node.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. TheNPM_TOKENrepository secret is already deleted, so this release must use OIDC.After merge
Push the tag
n8n-v1.0.1on the merge commit. Then revoke the temporary npm token.