Repository navigation
Keep n8n standalone and remove monorepo build/release support - #4
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
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 requested that its integration remain outside the monorepo. Keep
Deepkeepai/n8n-nodes-deepkeepas the active source and npm publisher.integrations/n8nfrom the active tree.The standalone repository remains public/unarchived with active CI and Release
workflows. Public npm metadata for 0.2.9 still points to the standalone repository.
No standalone files, workflows, registry settings, package versions, or credentials
were changed. Comparing the monorepo snapshot with standalone main found only
README and repository/issue metadata differences, not unported application code.
History And Environment Boundary
This is a normal forward deletion, not a Git history rewrite. Imported n8n ancestry
and namespaced tags remain because published PyPI/GHCR releases reference shared
source commits. No tags are moved or deleted.
The unused monorepo
release-n8nenvironment has zero secrets, variables, anddeployments. Delete it only after this code exclusion is merged and verified;
it has not yet been deleted. No npm registry-trust migration is established.
Validation
git diff --checkpassed.