AI Tool Updates 8 min read Published 2026-11-11

n8n 3.1.0 is still a prerelease: Agent publishing and the Assistant’s proxy scope

Official tags describe a release channel; they do not prove which version your instance or Cloud account is running. Check the version first, then confirm which saved Agent version is active and whether the failing Assistant request falls within PR #41901’s proxy scope.

n8n n8n 3.1.0 Prerelease AI Agents Agent version publishing HTTP_PROXY Assistant

Service eligibility and regional restrictions

PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.

Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.

Key Takeaways

As of November 11, 2026, the stable tag pointed to 2.47.3, while 3.1.0 and 3.2.0 were prereleases. A release tag does not prove that an instance has upgraded.
PR #41817 allows you to publish a selected saved Agent version and keep a newer draft. V1 published with V2 left in the editor is a hypothetical explanation of the PR test, not an instance test.
Unpublishing preserves the current draft; a switch happens only when a saved version is actually published. Agent publication versions are separate from workflow versions in Migration Report.
PR #41901 covers selected Assistant search, catalog, template and model-cost requests through environment proxies. It does not establish proxy behavior for the AI Assistant SDK or every node.

Separate release tags from the version on your instance

As of November 11, 2026, GitHub marked the stable tag as neither a prerelease nor a draft, and it pointed to 2.47.3. The n8n 3.1.0 and n8n 3.2.0 tags were marked as prereleases. This snapshot answers which channel the tags belong to; it does not tell you which version your instance is running.

The official n8n 2.47.0 and n8n 3.1.0 prerelease notes both list PRs #41817 and #41901. The stable 2.47.3 entry reviewed here does not confirm whether either change is included. Whether you self-host or use Cloud, check the version on your instance and its corresponding release record. Cloud rollout timing, plans, pricing and regional eligibility were not verified in this review.

Before adopting it, ask which saved Agent version is running

PR #41817 lets you select a saved version when publishing an Agent, even if the editor contains a newer draft. The key question is which version has been published and is running, not simply which draft was saved most recently.

Consider V1 and V2: assume V1 is published, then V2 is saved in the editor. If you publish V1 again, the running Agent uses V1 and V2 remains the current draft. This is the test scenario described in the PR, used here to explain the version relationship; it was not verified on PuppyIP or any live n8n instance.

Saving, publishing and unpublishing are separate states

Saving a new Agent draft does not automatically replace the published version. To run V2, explicitly publish V2; if you publish V1 again, the active version changes to the one you selected. The PR says runtime services follow the committed publication state.

Unpublishing stops the active publication but preserves the current draft. To understand what is running, check both the editor draft and the published version. Do not treat draft content or an unpublish action as proof that another version is live. Agent version behavior is separate from how the n8n 3.0 Migration Report handles workflow changes and versions.

Check whether the failed request matches the Assistant proxy fix

PR #41901 addresses some Assistant requests in self-hosted environments that ignored HTTP_PROXY or HTTPS_PROXY. It covers Brave Search, the models.dev model catalog, builder-template downloads and model-cost lookups in the Agent runtime.

The PR’s proxy-log check names api.search.brave.com and models.dev. If those hosts are in NO_PROXY, requests bypass the proxy and connect directly. First confirm that the failing action and request type match before using this PR as a diagnostic clue.

Do not extend the Assistant fix to all outbound traffic

Calls made through the AI Assistant SDK are explicitly outside PR #41901. The PR also does not establish that ordinary workflow nodes, every Agent runtime request, other protocols or every HTTP client use environment proxies.

If the failure comes from an unlisted node or SDK call, this release note is not enough to determine its proxy behavior. Check configuration and records for the relevant component and request; one Assistant request using a proxy does not show that all other outbound paths do the same.

Combine both checks before deciding whether to adopt the change

First, compare your instance version with the exact official tag and confirm whether its release record lists the relevant PR. The saved stable 2.47.3 tag does not prove that #41817 or #41901 is present in a particular instance, and it does not prove that either change is absent.

Next, confirm that the saved Agent version you intend to run is the version currently published. Then classify the network issue as a specific Assistant request and check its target host and NO_PROXY setting. These checks cover the release channel, Agent version and outbound request scope; one cannot stand in for the others. This review did not inspect or upgrade any Cloud account, n8n instance, workflow or credential.

Sources

Frequently Asked Questions

Does seeing a PR in release notes mean my instance has the feature?

No. A release tag identifies a version or channel’s release record; the stable 2.47.3 entry checked here does not prove whether #41817 or #41901 is included or excluded. Check your actual version and its release record.

Is n8n 3.1.0 a stable release?

No. In the GitHub tags saved on November 11, 2026, stable pointed to 2.47.3, while 3.1.0 and 3.2.0 were prereleases. Tags can change, so check them again before deciding.

Will publishing V1 overwrite or delete the V2 draft?

PR #41817 describes publishing selected V1 while preserving the newer V2 draft. Unpublishing also preserves the draft. V1 and V2 are a hypothetical explanation of the PR test scenario, not a test on a PuppyIP instance.

Does HTTP_PROXY route all n8n nodes and AI Assistant SDK requests?

That cannot be inferred. PR #41901 covers only the listed Assistant search, catalog, template and model-cost requests. AI Assistant SDK calls are explicitly out of scope, and there is no evidence here that every node or protocol uses the same proxy path.