SurgePilot v1.1.0

Highlights

• Product version identity is now governed from one repository source and propagated consistently
  through API/OpenAPI metadata, Runner output and bundles, the system API Catalog, and the Public
  API AI skill snapshot (#44).
• Contributor setup now uses a pinned, checksum-verified repository-managed toolchain with isolated
  state on Linux and macOS (#45).
• English, Simplified Chinese, and Japanese documentation navigation now links consistently back to
  the SurgePilot homepage (#43).
• Repository AI-development governance was simplified without changing product or runtime behavior
  (#42).

Install

For a new installation on a supported Linux host or macOS host with Docker Desktop:

curl -fsSL https://github.com/latentrun/SurgePilot/releases/download/v1.1.0/install.sh | sh
surgepilot up

Follow the v1.1.0 Quickstart
for prerequisites and first-run LAN configuration.

Upgrade

There is no automatic upgrade command, and the installer does not overwrite an existing
installation. To move an existing v1.0.0 deployment to v1.1.0, keep the deployment directory,
.env, .surgepilot/, and Compose project name; replace only release-owned files with the v1.1.0
bundle, then run the new surgepilot up. Review the
release transition guidance
before changing files.

Compatibility and breaking changes

• Tagged-deployment platform and Load Node requirements are unchanged from v1.0.0.
• Source contributors should run make setup; repository commands now select the pinned project
  runtimes without changing global runtime defaults.
• Product metadata now reports 1.1.0 consistently instead of component placeholder versions.
• Breaking changes: None for the tagged deployment, public API, persisted data, Runner protocol,
  or release asset format.

Full changelog

See all changes from v1.0.0 to v1.1.0.