Skip to content

Publish community nodes with independent version tags - #996

Merged
zlareb1 merged 1 commit into
mainfrom
fix/n8n-independent-publication
Nov 19, 2026
Merged

zlareb1 merged 1 commit into
mainfrom
fix/n8n-independent-publication

Conversation

@zlareb1

@zlareb1 zlareb1 commented Nov 19, 2026 •

Copy link
Copy Markdown
Member

Changelog category (leave one):

  • Build/Testing/Packaging Improvement

Changelog entry

The community node package can publish independently with a tag matching its package version.

Why

The package has its own version, but its publisher only runs on stable server tags. Add n8n-vX.Y.Z tags and reject a package tag unless it exactly matches the stable version in its manifest. Keep stable server tags as an existing publication route.

Scope and risk

Changes the publication trigger, tag validation, publishing instructions and guard tests. The publisher keeps its existing check dependency, hosted runner, locked tools, environment, OIDC permissions and provenance. A mismatched or prerelease package tag fails before publication. Package source and version stay unchanged.

Compatibility, rollout and rollback

  • Wire: none.
  • Operator steps: after this change merges and CI passes, push a package tag on the reviewed commit. Existing npm package ownership and trusted-publisher configuration must permit publication; this change supplies no credentials or account settings.
  • Rollback: revert the workflow and instructions. Already published versions remain immutable.

Tests

  • Ruff lint and format, Prettier, Python AST/YAML parsing and diff whitespace checks pass.
  • Ten guard cases execute the workflow's actual Bash with temporary package manifests, covering matching/mismatched package versions, prereleases, malformed versions and the existing stable server tag. Local admission refused before the cases could run; they remain unrun.
  • All required checks passed in CI on the pushed head. No package publication is claimed.

AI assistance in the code (leave one; writing this description with AI is fine):

  • AI-generated: Codex wrote the diff. A fresh independent review of the pushed head found no issues.

  • I can explain every line of this diff and how it interacts with the rest of Loom.

Checklist

  • Required CI passes; broad local suites were not run.
  • No generated files, migrations, plugin payloads, frontend or wire changes.
  • Publishing instructions describe the tag and account prerequisites.
  • Commits are signed off.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
@zlareb1
zlareb1 merged commit 217b544 into main Nov 19, 2026
56 checks passed
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