n8n-io/n8n

The variable is honoured regardless of NODE_ENV, so it also applies to production builds and the published Docker image. Never set it on an instance reachable by anyone you would not give a shell to. It also disables the crash journal, so a dev container that was killed rather than shut down gracefully does not pay the 10 second crash-loop penalty on its next boot.

This is a public repository. When working on security fixes, never expose the attack vector or vulnerability type in any public-facing artifact. Attackers monitor open-source repos for signals like branch names, commit messages, PR titles, test descriptions, and Linear URLs.

Security improvements, whether driven by enterprise requirements or internal standards, must NEVER add friction to the common-case building experience. When designing security-related features (defaults, behaviors, flows, error handling), apply these checks:

Transactions: transaction orchestration belongs in the persistence layer. Don't reach for .manager / .manager.transaction(...) or createQueryBuilder(...) in business logic. Use the sanctioned primitive in @n8n/db: inject the abstract TransactionRunner and wrap the unit of work in txRunner.run(ctx, async (ctx) => …). The callback receives an OperationContext carrying the active transaction; thread that ctx into the repository methods you call. run requires a context — pass an empty {} at the operation entry point, and reuse the one you were handed everywhere below it (a context that already car

Secrets on the command line: if a developer opted into anonymous dev metrics (scripts/dev-metrics), pnpm command arguments are recorded. Arguments of secret-carrying words (config, login, publish, token) — whether a subcommand or baked into a flag — are dropped, and the home dir is stripped from paths, but other args are sent as-is — so never put secrets in a command. Pass sensitive values via environment variables, which are never captured.

The schema reference is auto-generated — do not edit by hand. CI fails when a migration changes the schema but the docs weren't regenerated; when that happens, run pnpm db:schema:docs and commit the result.

Write your PR description, issue, and forum posts in your own words. Do not paste raw model output.

You must understand every line you submit and be able to explain what it does and how it fits the rest of the system, without the AI. If you cannot, do not open the PR yet.

Reuse immutable hoisted mock<T>(...) fixtures. Do not replace typed entity mocks with as unknown as T.

Don't use the deprecated ApplicationError class anywhere — it's a compatibility shim kept only so community nodes keep resolving. Use one of these instead, picking by cause:

Both seed profiles delete their own prior output, so a re-run replaces it. That clear step deletes anything named [seed] and any empty team project, whoever made them, so do not point either at a shared instance. The viewer is unauthenticated and serves the whole table: keep it on loopback.