[3alpha]

Context

Fix the SPEC-M03 warning reported by the package specification checks. The legacy upstreamRepo, upstreamVersion and upstreamArg fields are deprecated.

Approach

Replace the legacy fields with upstream: [{ repo, version, arg }]: n8n-io/n8n, n8n@2.46.5, UPSTREAM_VERSION.

Test instructions

Validate this branch with the SDK package-spec checker from the linked PR and confirm that no SPEC-M03 findings remain.

Verified locally:

• Loaded 1 package using the SDK, including merged variant manifests where present.
• SPEC-M03 findings: 1 → 0; total spec findings: 1 → 0; no new findings under other rules.
• Compared manifest schemas and effective compose against the default branch: no new schema failures or service runtime changes.
• git diff --check passes.

Container images were not built locally.

[tropibot]

Dappnode bot has built and pinned the built packages to an IPFS node, for commit: 59c7587

This is a development version and should only be installed for testing purposes.

1. Package n8n.dnp.dappnode.eth

Install link

Hash: /ipfs/QmfLskVDpBEKHbJR73dQQBG8d4dC6x125SKHYN8PpkamM6

(by dappnodebot/build-action)

[tropibot]

✅ Package harness passed

Baseline and candidate containers became stably running

Package	Verdict	Reason	Duration	Cleanup
n8n.dnp.dappnode.eth	✅ Passed	Candidate containers stable (candidate_containers_stable)	14m 24s	✅ Passed

Run overview

Context	Value
Pull request	dappnode/DAppNodePackage-n8n#264
Tested commit	59c7587efc34
Candidate artifact	Install on DAppNode · /ipfs/QmfLskVDpBEKHbJR73dQQBG8d4dC6x125SKHYN8PpkamM6
Baseline request	automatic
Worker	dappnode-near-5
Run ID	gh-pr-264-59c7587efc34-365eb61b6cd4f0d5
Execution	2026-11-09T11:51:15.856713838+00:00 → 2026-11-09T12:05:40.144462748+00:00 (✅ Completed)

Baseline vs candidate

Check	Baseline	Candidate
Version	0.1.4	0.1.5
Install	✅ Passed · 1m 37s	✅ Passed · 11m 54s
Hard check	✅ Passed · 3 stable samples	✅ Passed · 3 stable samples
Containers	1 observed	1 observed
Stabilization	10s	10s
Log collection	✅ Passed · 1 container	✅ Passed · 1 container

Container comparison

• Added: none
• Removed: none
• Baseline inventory: DAppNodePackage-n8n.n8n.dnp.dappnode.eth
• Candidate inventory: DAppNodePackage-n8n.n8n.dnp.dappnode.eth
• Baseline non-running states: none
• Candidate non-running states: none
• Deterministic regressions: ✅ none

Container inventory

Baseline

Container	Service	State	Image	Created
DAppNodePackage-n8n.n8n.dnp.dappnode.eth	n8n	✅ Running	n8n.n8n.dnp.dappnode.eth:0.1.4	1794225172

Candidate

Container	Service	State	Image	Created
DAppNodePackage-n8n.n8n.dnp.dappnode.eth	n8n	✅ Running	n8n.n8n.dnp.dappnode.eth:0.1.5	1794225891

Runtime analysis _advisory

⚠️ Suspicious — Heuristic and Nexus analysis: The candidate upgraded from 2.29.8 to 2.46.5, completed all listed migrations, started the scheduler, and exposed the editor successfully. The prior missing-Python-runner warning remains unchanged. New candidate-only evidence shows one concrete telemetry event being dropped and several upgrade-related configuration deprecations; no new crash, failed migration, or core startup failure is evident.

Analyzer	Status	Summary
Composite	⚠️ Suspicious	Heuristic and Nexus analysis: The candidate upgraded from 2.29.8 to 2.46.5, completed all listed migrations, started the scheduler, and exposed the editor successfully. The prior missing-Python-runner warning remains unchanged. New candidate-only evidence shows one concrete telemetry event being dropped and several upgrade-related configuration deprecations; no new crash, failed migration, or core startup failure is evident.
Heuristic	✅ Clean	No configured candidate-only suspicious signature was found
Nexus	⚠️ Suspicious	The candidate upgraded from 2.29.8 to 2.46.5, completed all listed migrations, started the scheduler, and exposed the editor successfully. The prior missing-Python-runner warning remains unchanged. New candidate-only evidence shows one concrete telemetry event being dropped and several upgrade-related configuration deprecations; no new crash, failed migration, or core startup failure is evident.
Baseline evidence	✅ Clean	No configured suspicious signature was found
Candidate evidence	✅ Clean	No configured suspicious signature was found

Severity	Container	Finding	Evidence
⚠️ Warning	DAppNodePackage-n8n.n8n.dnp.dappnode.eth	This candidate-only message confirms an actual loss of a startup telemetry event. It does not appear to affect n8n availability, but it degrades runtime observability and instance-start reporting.	Telemetry event "Instance started" carries no user_id, so PostHog drops it. Pass user_id in the event properties at the emit site.
⚠️ Warning	DAppNodePackage-n8n.n8n.dnp.dappnode.eth	These deprecations are absent from the baseline and appear after the upgrade. The service still starts, so this is not a current outage, but the deprecated variables and changing defaults create a likely future configuration and runtime-compatibility regression risk.	There are deprecations related to your n8n setup: WEBHOOK_URL -> N8N_WEBHOOK_URL; N8N_UNVERIFIED_PACKAGES_ENABLED default will change; N8N_RUNNERS_MODE internal mode is deprecated; N8N_RUNNERS_TASK_TIMEOUT and N8N_COMPRESSION_NODE_MAX_ZIP_ENTRIES defaults will be reduced.

Cleanup and diagnostics

Check	Result
Cleanup	✅ Passed
Leftover packages	none
Cleanup error	none

✅ No run errors were recorded.

---

_{Deterministic checks decide the verdict. Runtime log analysis is advisory. TropiBot publishes bounded summaries and never posts raw logs.}