Repository navigation
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 namedpassword.
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 upUpgrade
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.