Fluffy uses a unified cohort release model. Every public component — the Core CLI, the Premium companion, the hosted Control Room, generated SDKs, and shared UI packages — is versioned and tagged under the exact same release number.
#v0.1.12 — September 8, 2026
- Added: Export standalone Pulumi deployments — Compile your accepted application infrastructure directly into a standalone Pulumi TypeScript project using
./core/fluffy-chainsaw eject --output ./exported-infra. This lets you run and maintain your cloud infrastructure independently without any Fluffy CLI dependencies. See the Ejection guide. - Added: Streamlined deployment progress — Live step countdowns, immediate error callouts, and direct Google Cloud console deep links when provisioning Cloud Run services and Cloud SQL instances. See the Deployment reference.
- Changed: Standardized Firestore database policy — Document storage configurations across Core, Premium, and Platform components now use unified database naming and consistent role bindings.
- Fixed: Preserve legacy sidecar configuration — Fixed an issue where custom local proxy ports and sidecar environment variables were omitted during standalone Pulumi export.
#v0.1.11 — September 4, 2026
- Added: Point-in-time database recovery — Automated continuous WAL archiving and point-in-time restore workflows for managed Cloud SQL Postgres databases, with non-destructive verification clones to test recovery points before replacing production state. See Database recovery.
- Added: Cryptographic deployment review gates — Added tamper-evident deployment acceptance tokens. Deployments can only proceed if the proposed Pulumi plan was signed and accepted via
--check. See Deployment actions. - Changed: Modularized Pulumi code generation — Decomposed monolithic Pulumi generation into domain-specific packages (
compute,databases,networking,secrets) insidecore/internal/deploy/pulumigofor faster builds and cleaner diffs. - Fixed: Local test harness isolation — Resolved race conditions in local automated test suites when rapidly provisioning and tearing down ephemeral tenant schemas.
#v0.1.10 — August 28, 2026
- Added: Managed secrets integration — Native integration with Google Cloud Secret Manager. Applications declare secret resources in
fluffy-chainsaw.yamland grant granularreadorlistactions to backend runtimes with automated injection. See the Secrets guide. - Added: Percentage and audience feature flags — Client and server-side feature flag evaluation with audience targeting, percentage rollouts, and millisecond rule synchronization. See Feature flags.
- Changed: Fail-fast local release pipeline — The local release script (
./release-fluffy) now stops immediately at the first failed build step, preventing partial deployment states. - Fixed: Proxy port contention — Local sidecar proxies now probe available network ports automatically when default ports are occupied by background processes.
#v0.1.0 — August 15, 2026
- Added: Declarative application manifest — Schema-validated architecture specification modeling runtimes, databases, storage buckets, pub/sub queues, and access grants in
fluffy-chainsaw.yaml. See the Manifest spec. - Added: Generated multi-language SDKs — Automated generation of typed gRPC client libraries for TypeScript, Go, and Python directly from declared manifest grants. See Generated SDKs.
- Added: Zero-config local development — Full local emulator environment launched with a single
./run-localcommand. See Local development. - Added: Direct GCP Pulumi provider — Cloud provisioning for Cloud Run, Cloud SQL, Cloud Storage, and Firebase Hosting. See the Deployment guide.
#Release policy
- Synchronized tags: We never publish independent version numbers for child repositories. All components update together under
vX.Y.Z. - Backward compatibility: Manifest schema changes are backward-compatible within minor versions. Deprecations provide at least one cohort warning before removal.
- Reproducible deployments: Production deployments are strictly pinned to immutable container digest hashes and approved plan artifacts.
For upcoming work and in-flight initiatives, see the Product roadmap.