Repository navigation
chore: adopt n8n template 2.2 package and release safeguards - #9
Merged
Merged
Conversation
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
1 participant
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.
Adopt reviewed n8n template guidance pinned at
596e784cfe69cd8894529b8a81c491921cde9773: scanner 0.38.0 with nested compiler aliases, source/constructor hygiene, release-tag guards, publication verification, optional notification tooling, and isolated development-port guidance. Keep node functionality and package version unchanged. The builder configuration uses GPT-6-Luna with Medium reasoning as requested; machine-specific session instructions are excluded from AGENTS.md.Validation: template-only checks passed 68 tests across 9 files on Node 24.18.0 and 22.23.2 with npm 11.19.0, plus formatting, lint, strict typecheck, source review, build, scanner source/built checks, package/load checks and isolated packed install. The tag guard also passed from a fresh detached checkout of the actual annotated v0.1.1 release tag. Hosted actions/checkout behavior and publication remain unqualified; no notification or release was triggered.
Review and merge this PR first using a merge commit to preserve the stack ancestry. Avoid squash merging; otherwise Revenue must be rebased before retargeting it to main. Revenue PR #10 uses this branch as its base while this PR is pending.