New files from Fly.io Launch

[Pascalchinedu]

Summary

Related Linear tickets, Github issues, and Community forum posts

Review / Merge checklist

• PR title and summary are descriptive. (conventions)
• Docs updated or follow-up ticket created.
• Tests included.
• PR Labeled with release/backport (if the PR is an urgent fix that needs to be backported)

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Fly.io seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[n8n-assistant]

Hey @Pascalchinedu,

Thank you for your contribution. We appreciate the time and effort you’ve taken to submit this pull request.

Before we can proceed, please ensure the following:
• Tests are included for any new functionality, logic changes or bug fixes.
• The PR aligns with our contribution guidelines.

Regarding new nodes:
We no longer accept new nodes directly into the core codebase. Instead, we encourage contributors to follow our Community Node Submission Guide to publish nodes independently.

If your node integrates with an AI service that you own or represent, please email [email protected] and we will be happy to discuss the best approach.

About review timelines:
This PR has been added to our internal tracker as "GHC-5621". While we plan to review it, we are currently unable to provide an exact timeframe. Our goal is to begin reviews within a month, but this may change depending on team priorities. We will reach out when the review begins.

Thank you again for contributing to n8n.

[cubic-dev-ai]

1 issue found across 2 files

Prompt for AI agents (all 1 issues)

Understand the root cause of the following 1 issues and fix them.


<file name="Dockerfile">

<violation number="1" location="Dockerfile:28">
`pnpm install` runs before the workspace metadata and packages are copied, so the `workspace:*` dependencies (e.g., `@n8n/eslint-config`) can’t resolve and the Docker build fails. Copy `pnpm-workspace.yaml` and the workspace package manifests (or the full repo) before running `pnpm install`.</violation>
</file>

---

Since this is your first cubic review, here's how it works:

• cubic automatically reviews your code and comments on bugs and improvements
• Teach cubic by replying to its comments. cubic learns from your replies and gets better over time
• Ask questions if you need clarification on any suggestion

_{Reply to cubic to teach it or ask questions. Re-run a review with @cubic-dev-ai review this PR}

[cubic-dev-ai]

pnpm install runs before the workspace metadata and packages are copied, so the workspace:* dependencies (e.g., @n8n/eslint-config) can’t resolve and the Docker build fails. Copy pnpm-workspace.yaml and the workspace package manifests (or the full repo) before running pnpm install.

Prompt for AI agents

Address the following comment on Dockerfile at line 28:

<comment>`pnpm install` runs before the workspace metadata and packages are copied, so the `workspace:*` dependencies (e.g., `@n8n/eslint-config`) can’t resolve and the Docker build fails. Copy `pnpm-workspace.yaml` and the workspace package manifests (or the full repo) before running `pnpm install`.</comment>

<file context>
@@ -0,0 +1,49 @@
+    apt-get install --no-install-recommends -y build-essential node-gyp pkg-config python-is-python3
+
+# Install node modules
+COPY .npmrc package.json pnpm-lock.yaml ./
+RUN pnpm install --frozen-lockfile --prod=false
+
</file context>