Skip to main content
Product updates, organized newest first. For deeper details on each release, see the StackKits release notes on GitHub.
2026-06-12
Week of June 8 – June 12

StackKits v0.3.4

One release this week, focused on a native MCP surface, TechStack-managed install readiness, and public release hygiene.

New

  • Native MCP surface. StackKits now exposes a single user-facing stackkit MCP connection, with stackkit-mcp as the local adapter and stackkit-server /mcp as the protected durable endpoint after install. Agents and IDEs can connect to one stable name across local, SSH, and remote setups.
  • TechStack-managed install readiness. Release archives include the MCP and server pieces needed for kombify-TechStack managed installs, with bounded MCP rollout and Fresh Ubuntu phase gates so you can see exactly when each phase completes. See Install-only vs managed cloud and Deploy with the CLI or TechStack.
  • Agent discovery on stackkit.cc. The site now ships OpenMCP metadata, updated llms.txt, and installation guidance for local, SSH, and protected durable MCP paths, so coding agents can discover and connect to a StackKit on their own.

Fixed

  • Public release hygiene. Public release builds no longer depend on private internal modules, and the Docker image build no longer leaks private module-auth configuration into the released image.
  • Bounded release gates. Build timing, website checks, MCP smoke tests, and timeout-budget checks are now bounded by the 15-minute command policy, so a stuck step fails fast instead of hanging the release.
2026-06-05
Week of June 2 – June 5

StackKits v0.3.1 and v0.3.2

Two patch releases shipped this week, focused on Coolify routing, auth, installer reliability, and security.

New

  • Canonical live scenarios. Releases are now validated against three reference setups: local Coolify (SK-S1), kombify.me on Komodo (SK-S2), and custom-domain Coolify (SK-S3). Installer runs are split into bounded Start, Wait, and Verify phases so you can see exactly where a deploy is. See Choosing a kit.
  • Coolify managed routing. BaseKit on Coolify now bootstraps, reconciles, and exposes StackKit services through the managed proxy at predictable hostnames like base.<domain>, id.<domain>, photos.<domain>, and kuma.<domain>. See Deploy with the CLI or TechStack.

Improved

  • PocketID + TinyAuth on BaseKit. Provider registration and runtime checks were restored, so protected services again show PocketID login (with TinyAuth as the password-only fallback) instead of skipping straight to TinyAuth. See PocketID and TinyAuth.
  • Cloudflare DNS-01 for custom domains. Custom-domain Coolify rollouts now correctly pass Cloudflare Global API Key credentials to Traefik when CLOUDFLARE_EMAIL is set, while scoped API tokens continue to work as before. See Traefik.
  • Installer readiness. Live installer jobs hand off VM state before verification and wait for routed services and certificates in bounded phases, instead of relying on one long-running job.
  • Security updates. Go crypto and networking dependencies (golang.org/x/crypto, golang.org/x/net, and related modules) were updated and lint, static, and security checks restored to a clean state.

Fixed

  • Coolify proxy recovery. Fallback and reconciliation now correctly restore file-provider routing, dynamic config mounts, proxy TLS, service routes, host-gateway access, and dynamic-config sync.
  • Coolify endpoint contract. BaseKit keeps the persisted Coolify endpoint node-local at http://127.0.0.1:8000, while bootstrap and readiness probes can use a separate endpoint reachable from remote Docker targets.
  • Restore-drill metrics. Host CPU metrics now preserve legitimate zero values instead of dropping them as missing data.
  • Release archive validation. Smoke checks now validate the current Coolify platform contract from packaged contents instead of obsolete token API markers.