SurgePilot v1.2.7

Highlights

• Database migration now uses the runtime dependencies already installed in the API image.
  Startup no longer tries to download development tools such as ruff or pytest before running
  migration, fixing failures when containers cannot reach Python package indexes. The same fix
  applies to source container startup. See issue #68.

Install

Install this exact release, then start it from an interactive terminal:

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

Image pulls and Runtime downloads still require their existing network access or validated local
artifacts; this fix does not make the entire installation process offline.

Upgrade

Official installed releases v1.0.0, v1.1.0, v1.2.3, v1.2.5, and v1.2.6 are within the supported
same-major upgrade range. Back up PostgreSQL, MinIO, and other persistent volumes. Stop or finish
active Runs and Load Node initialization work, run the installation command above, then run
surgepilot up. Startup refuses to migrate while supported work is active.

The transition is forward-only. If migration or health validation fails, fix the target problem
and retry the same surgepilot up. SurgePilot does not downgrade the database or automatically
start the previous release after migration begins.

Existing Load Nodes retain their previous Runtime version. Explicitly reinitialize each required
Load Node before starting new Runs.

Compatibility and breaking changes

• Database migration scripts, schemas, credentials, and migration failure blocking are unchanged.
• Migration containers use the image's existing environment; a missing runtime dependency remains
  a startup error rather than triggering an installation attempt.
• Manually extracted bundles remain expert-managed and do not use the installed-release transition
  protocol.
• Breaking changes: None.

Full changelog

See the changes since v1.2.6.