Skip to content

BaseHarbor v0.4.25

Release notes prepared for 15 October 2026.

Start with only what your app needs

Run a supported local workload on Docker or rootless Podman without a mandatory management installation or login. Request SQL, cache, secrets, storage, identity or HTTPS when needed; BaseHarbor resolves their genuine dependencies.

Less configuration, clearer plans

Start with version, app.name and app.environment. BaseHarbor assigns and retains the application identity; omit app.id from authored YAML.

CLI, JSON, MCP and HTTP share provider plans and footprint information. Plans explain affected applications, dependencies, access and retained or deleted data. Unmeasured resource use remains explicitly unknown.

Change services without losing track of data

Add, remove and re-enable supported services. Shared consumers keep their required providers; default retirement preserves owned data, credentials and recovery state. SQL/Valkey can switch between shared and application placement, with separate existing data stores rather than automatic data copying. The original application runtime owner remains available for verification after switching to shared placement and later withdrawing its consumers.

Alternative-less, destructive or unknown consequences require Achtung and two current-plan confirmations. Deleting owned data requires separate consent; --yes does not replace these decisions.

Safer recovery and remote operation

Backup restoration retains the original application identity and checks the current archive, owners and selected authentication/telemetry material before resetting state. Interrupted cleanup retains the information needed to retry.

Backend reconciliation retains the Identity trust and credential files already delivered to running workloads.

Managed OIDC uses actual HTTPS callback routes. Remote reactivation preserves its immutable publication; Node disconnect uses the same approval and authority checks across CLI, MCP and HTTP. Podman volume deletion preserves foreign containers using the volume.

Compatibility

  • Docker and native rootless Podman/Quadlet are the implemented runtimes.
  • Remote application delivery currently supports application-scoped SQL, cache and durable key-value; other remote capabilities remain explicitly unsupported. Local OIDC/OTLP file references are not remote material delivery.
  • Unsupported provider transitions are reported before execution; confirmations do not create missing adapters.
  • No migration for developer-authored application IDs is provided.
  • The compact capability wizard, onboarding and new Console UX follow in later releases.

Dependency maintenance updates reviewed image/Action pins and Pages tooling. Release builds use the patched Go 1.26.9 toolchain; the Go 1.25 language floor is retained. The preparation checkpoint records current runtime, consumer and security qualification. Complete pre-release approval is separate. See the documentation for configuration and supported paths.