Repository navigation
Publish community nodes with independent version tags - #996
Merged
Merged
Conversation
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.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.
Changelog category (leave one):
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.Ztags 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
Tests
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