InsForge

v2.1.4-compute Bugfix

This release fixes issues for SREs watching stability and regressions.

Published 1mo AI Agents & Assistants

View tool

✓ No known CVEs patched

Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

ai ai-agents coding deno embeddings insforge

+7 more

nextjs oauth2 pgvector postgresql realtime vectors websockets

Summary

AI summary

Fixed network name validation failures by shortening names to APP_KEY values.

Full changelog

Companion to cloud-backend release with PR #495.

Bug

OSS forwarded network: ${projectId}-network (~44 chars) to cloud-backend → forwarded to Fly → 422 "Validation failed: Name not a valid network name" on prod's strict-validator Fly org.

Fix

makeNetwork() now returns process.env.APP_KEY (~8 chars, e.g. d9byq46t) — short enough for Fly's validator on every org, still unique per project so 6PN isolation is preserved.

Live e2e proof on prod

| Network value | Length | Result |
|---|---|---|
| Old ${projectId}-network | 44 chars | 422 |
| New <APP_KEY> | 8 chars | 201 |

Deploy

Pull the new image, redeploy your OSS instance. APP_KEY env var is already set per-instance (it's the project's URL slug) — no new config needed.

🤖 Generated with Claude Code

View diff on GitHub

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Share on X Share on Bluesky

Track InsForge

Get notified when new releases ship.

About InsForge

All releases →

Related context

Related tools

Earlier breaking changes

v2.1.8 Restricts raw SQL permission to project_admin role only.