Skip to content

Fulling v2.0.0

Latest

Choose a tag to compare

@Che-Zhu Che-Zhu released this 11 May 08:10

Fulling v2.0.0

Fulling v2.0.0 is the release snapshot for the v2 control-plane work.

This release is not intended to claim the full future platform surface. It
stabilizes the current agentic sandbox foundation so main can move on to 3.0
development with a clean historical branch.

Release Positioning

Fulling v2 is a browser-based AI development environment with:

  • project creation from scratch
  • GitHub App based repository import
  • isolated Kubernetes sandboxes
  • browser terminal and file manager access
  • live HTTPS runtime URLs
  • optional PostgreSQL databases
  • persisted background reconciliation for resource and project-task work
  • global skill enablement and uninstall fan-out through ProjectTask

Not 2.0 Scope

The following surfaces remain future product work and are intentionally not
presented as complete v2.0 features:

  • MCP management
  • template marketplace
  • top-level integrations marketplace
  • fully automated production deployment
  • generalized deploy providers

The codebase contains early hooks and placeholders for some of these ideas, but
they should be treated as 3.0 development inputs rather than 2.0 guarantees.

Key Changes Since v1.0

  • Replaced the older GitHub OAuth repository flow with GitHub App installation
    metadata and installation-token based import.
  • Made PostgreSQL optional, so projects can start with only a sandbox.
  • Added ProjectTask as the task-plane abstraction for asynchronous project
    work such as repository clone and skill operations.
  • Added global skill enablement and uninstall semantics backed by durable
    per-project install/uninstall tasks.
  • Introduced lib/platform/ as the first step toward explicit control-plane
    boundaries.
  • Updated documentation around the control plane, reconciliation model, and
    intended architecture evolution.

Branch and Tag Plan

  • Release branch: release/2.0
  • Release tag: v2.0.0
  • Ongoing development branch: main for 3.0 work

Use release/2.0 for v2 stabilization fixes only. Use main for product and
architecture changes that belong to the next major version.