Appwrite Functions runtime version change impact on existing deployed functions

Question

When Appwrite updates the default Node.js runtime version for Functions, it is unclear whether existing deployed functions are automatically migrated to the new runtime or require a manual redeploy to continue operating.

This ambiguity affects dependency compatibility, environment variable handling, and cold‑start performance, especially for self‑hosted installations where administrators control upgrade timing.

What determines the migration path for existing functions when the platform runtime default changes? Is the behavior consistent across cloud and self‑hosted deployments, and where is this policy documented?

Tasadduq Burney · Answer

Existing deployed functions do not automatically migrate to a new runtime version when the platform updates its defaults. Each function remains pinned to the specific runtime version selected at the time of deployment until a manual redeploy occurs.

How Migration is Determined
The migration path is determined by the metadata associated with the deployment. When you deploy a function, Appwrite records the specific runtime (e.g., node-18, node-20). Even if the Appwrite team updates the global default for *new functions, existing functions continue to use their original environment to prevent breaking changes in dependencies or API compatibility.

Consistency Across Cloud and Self-Hosted
The behavior is consistent across both Appwrite Cloud and self-hosted installations:

Cloud: The platform manages the available runtime images. New functions use the latest default, but existing functions are untouched until manually updated or redeployed.
  Self-Hosted: Administrators control when runtime images are pulled to the local environment. Upgrading the Appwrite Docker images makes new runtimes available but does not trigger a migration of existing function containers.

Steps to Update a Runtime Version
To move an existing function to a newer runtime version, follow these steps:

Navigate to the Appwrite Console and select your specific function.
  Go to the Settings tab.
  Locate the Runtime dropdown and select the desired version.
  Save the settings and trigger a Redeploy (or use the CLI/SDK) to rebuild the function container with the new environment.

Assumptions and Uncertainty
This explanation assumes the function code is compatible with the target runtime (e.g., moving from Node.js 16 to 20 may require code changes for certain native modules). While the platform behavior is stable, the specific availability of a runtime version may vary based on the version of Appwrite you are running. You should verify the available runtimes in the Console before attempting an upgrade.

Appwrite Functions runtime version change impact on existing deployed functions

1 answer

Existing deployed functions do not automatically migrate to a new runtime version when the platform updates its defaults. Each function remains pinned to the specific runtime version selected at the time of deployment until a manual redeploy occurs.

How Migration is Determined

Consistency Across Cloud and Self-Hosted

Steps to Update a Runtime Version

Assumptions and Uncertainty

Your perspective belongs here.

0 question comments