v0.1.10

Fixed

• Deleting a service from one environment no longer deletes it
  everywhere. Deleting a service in the dashboard while viewing staging
  removed it from every environment, production's deployments and volume
  data included. Deleting is now per environment, like Railway: the confirm
  dialog says Delete from , and only that
  environment's deployments, volume data, domains, TCP proxy, variables and
  cron schedule go. The service itself goes with its last environment.
  Deleting from all environments is a separate option in the dialog that
  asks for the service's name. The settings-tab Delete buttons (services,
  functions, buckets) now confirm first, and the canvas and the project's
  Danger settings only list the services of the environment being viewed.
• Discarding a never-deployed service's pending changes removes it from that
  environment only.

Changed

• API (breaking): DELETE /api/services/{id} now requires
  ?allEnvironments=true and is refused without it, so an old client can't
  delete a service everywhere by mistake. The new DELETE /api/service-instances/{id} deletes a service from one environment
  (Member + sudo); its response says whether the service itself was deleted
  (serviceDeleted).
• The service.delete audit entry records the environment
  (environment, environmentName, serviceDeleted), or
  allEnvironments: true and the environments for a delete everywhere.

Install

New server (Ubuntu 22.04+ / Debian 12+):

curl -fsSL https://usemodula.org/install.sh | bash

Upgrade an existing instance: curl -fsSL https://usemodula.org/install.sh | sudo bash -s -- upgrade --version 0.1.10

CLI (Linux/macOS): curl -fsSL https://usemodula.org/install-cli.sh | bash

Verifying

SHA256SUMS is signed with the Ed25519 release key in deploy/release.pub.pem (SHA256SUMS.sig); the installer checks both automatically. It also lists the bundled third-party binaries (Caddy, BuildKit, Railpack, WAL-G, workerd), which the installer downloads from downloads.usemodula.org.

See the guide for docs.