InsForge edge functions now run on Deno Deploy v2. Deno is sunsetting Deno Subhosting, the platform they ran on before, on July 20, 2026. Version 2.2.2 moves your functions onto the new platform.
If you created your project on or after June 18, 2026, it already runs on Deno Deploy v2. No upgrade or redeploy needed, and the rest of this post does not apply to you.
What You Need to Do
For any project created before June 18, 2026, there are two steps, and the deadline is July 20:
- Upgrade your project to v2.2.2. Open the project in your dashboard and upgrade it. The upgrade pulls v2.2.2 along with the new function runtime.
- Re-deploy each edge function once. The redeploy is the step that moves a function off Deno Subhosting and onto Deno Deploy v2. A function you never redeploy stays on the old runtime.
Deno shuts down the Subhosting v1 API on July 20. The official notice doesn't say already-deployed functions keep serving past that date, so a function left on the old runtime may stop working. Re-deploy before the deadline to stay on the safe side.
Your Function URLs
Call your functions through the InsForge SDK and nothing changes. The SDK reads each function's URL from the backend, so it resolves the new address on its own.
If you hardcoded a raw function URL somewhere in your client, re-fetch it from the dashboard or the SDK after redeploying, then update the reference.
Get Help
If a redeploy fails, or a function behaves differently on the new runtime, reach out and we will get you sorted before the deadline: