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.

SurgePilot v1.2.6

Highlights

• Registration now requires matching passwords before submitting. The confirmation field includes
  an eye button to show or hide its value, including keyboard operation. See PR #65.
• Runtime builds download the unchanged JMeter 5.6.3 distribution from the Apache distribution CDN,
  addressing the archive-server download timeout observed in native amd64 validation.

Install

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

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

Upgrade

Official installed releases v1.0.0, v1.1.0, v1.2.3, and v1.2.5 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.

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

• Registration confirmation is checked only in the frontend. Existing authentication APIs,
  credentials, and sessions are unchanged.
• JMeter remains at version 5.6.3. Explicit Runtime source and checksum overrides remain supported.
• 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.5.

SurgePilot v1.2.5

Highlights

• Reconciles the first-Admin system API Catalog document with the current product OpenAPI after
  startup, while preserving its stable identity and user-created Catalog documents.
• Extends the installed-release transition to later v1 targets and tests every published,
  supported upgrade source during formal release validation.
• Validates the complete release candidate before creating its formal Git tag. The release-stack
  verifier also accepts legitimate OpenAPI schema fields named password.

Install

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

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

Upgrade

An installed release from the official v1.0.0, v1.1.0, or v1.2.3 release is within the supported
same-major upgrade range. Back up PostgreSQL, MinIO, and other persistent volumes before upgrading.
Stop or finish active Runs and Load Node initialization work, run the installation command above,
and then run surgepilot up.

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

Existing Load Nodes retain their previous Runtime version after the control plane is ready. Each
required Load Node must be explicitly reinitialized before new Runs are execution-ready.

Compatibility and breaking changes

• Supported published installed-release upgrade sources: v1.0.0, v1.1.0, and v1.2.3, within
  product major 1.
• A stale local deployment lock fails closed and requires the operator to verify no installer or
  lifecycle command is running before removing that exact lock directory.
• 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.3.

SurgePilot v1.2.3

Highlights

• Adds the first bounded user-local installed-release transition, preserving the existing
  Compose project, volumes, deployment configuration, credentials, Workspace data, artifacts,
  Monitoring data, and the first-Admin system API Catalog document.
• Keeps release payloads in immutable version directories selected by one small dispatcher.
• Refuses migration while Runs, initialization, leases, control requests, or report parsing are
  active.
• Uses the installed psycopg 3 driver when probing databases created by the v1.0.0 and v1.1.0
  deployment configuration.
• Correctly validates the distinct vX.Y.Z Runtime artifact identity and the preserved historical
  system Catalog identity during upgrade publication.

Install

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

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

Upgrade

Automatic transition is supported from the official v1.0.0 and v1.1.0 releases. Back up the
PostgreSQL, MinIO, and other persistent volumes before upgrading. Stop or finish active Runs and
Load Node initialization work, run the installation command above, and then run surgepilot up.

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

Existing Load Nodes retain their previous Runtime version after the control plane is ready. Each
required Load Node must be explicitly reinitialized before new Runs are execution-ready.

Compatibility and breaking changes

• Supported installed-release upgrade range: v1.0.0 through v1.1.0, within product major 1.
• A stale local deployment lock fails closed and requires the operator to verify no installer or
  lifecycle command is running before removing that exact lock directory.
• Manually extracted bundles remain expert-managed and do not use the installed-release transition
  protocol.

Full changelog

See the changes since v1.1.0.

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.

SurgePilot v1.0.0

Highlights

• Initial public release of the self-hosted SurgePilot distributed load-testing platform.
• Visual Scenario and Test Plan workflows, authenticated Workspaces, Linux Load Nodes, Debug and
  Standard Runs, Run Reports, and InfluxDB/Grafana monitoring are available in one release.
• The release uses digest-pinned multi-architecture control-plane images and native Linux amd64
  and arm64 Runtime assets. A checksum-verified user-local installer provides the surgepilot
  lifecycle command.
• API Catalog, the PAT-authenticated public API, and Help guidance for AI agents are included.

Install

On a supported Linux host or macOS host with Docker Desktop:

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

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

Upgrade

This is the first public release, so no upgrade from an earlier SurgePilot release applies.
Automatic upgrades are not supported.

Compatibility and breaking changes

• The containerized control plane supports Linux amd64, Linux arm64, and macOS through Docker
  Desktop.
• Load Nodes and the Taurus/JMeter Runtime are Linux-only; the supported distributions are Ubuntu
  24.04 and Debian 12.
• The interactive release setup configures HTTP for a trusted LAN. Internet-facing deployments
  require an operator-managed HTTPS reverse proxy and secure-cookie configuration.
• Breaking changes: None; this is the initial public release.

Full changelog

See the v1.0.0 tagged commit history.