Skip to content

Neon 0.2.2 preview — Cloud integration

Choose a tag to compare

@NewtTheWolf NewtTheWolf released this 09 Nov 18:46
· 10 commits to main since this release
48669a6

This release publishes Neon as kind: cloud in the Tabularis registry. It requires the cloud package acceptance changes in Core commit 56f79885ba7c22864345b4ec84f3c0cf4386be77 (PR #1445, still draft). Older hosts reject this package kind. SQL uses the existing executable JSON-RPC driver runtime.

Neon provider-workspace preview for Tabularis. This release requires Node.js 22+, Linux x64, and the provider-workspace Core build exposing plugin API 0.2.7. Stock Tabularis 0.31.0 is not sufficient. Required Core work: TabularisDB/tabularis#1445 (draft; no main-branch merge).

Includes the standalone manifest, reviewed screenshots in the source repository, a self-contained runtime/UI archive and SHA-256 checksums. Extracted-archive checks passed for JSON-RPC initialize/ping and local TypeScript Function validation without checkout/global dependency fallback. Runtime unit tests: 59 passed. UI/host tests: 93 passed. All plugin implementation and integration tests live in this independent repository; Core contains reusable provider APIs only.

Features: project/branch account onboarding, PostgreSQL metadata/SQL/CRUD/EXPLAIN, separate branch connections, Auth identity/role management, private assets text objects, Monaco JS/TS Function editing and validation, initial Function deployment/invocation, bounded Realtime snapshots, AI Gateway prompts and scoped usage/resource caps.

Known failure: Function source/environment updates can report completed/active metadata while the endpoint executes the previous revision. Independent SDK and HTTP controls reproduce it, including fresh GET/POST timestamps. Verify endpoints after updates. Existing Functions are not deleted/recreated to hide this failure.

Other preview limits include the fixed assets bucket, incomplete Auth administration, no partner OAuth client yet, prototype AI/Realtime caps and unavailable billing amounts where Neon does not expose them. See README for the supported scope. Registry submission is for review; this release is not a production-readiness claim.