Skip to content

Runtime versions

Every service runs a version of the GraphPilot proxy runtime. By default it follows the stable version and moves to a new one on its next deployment. You can fix a service to one version in the portal (Service settings, Runtime) or with gpilot service runtime pin <version>. Changing the pin rebuilds the service with the version the pin resolves to, unless the service already runs that version and no deployment is in progress. In the portal you can also save the pin without deploying, and the service’s next deployment uses it. Either way it needs service:edit and deployment:edit.

You can also pin a single deployment in the service config:

[runtime]
version = "0.33.1"

This key pins only the deployment that gpilot deployment create makes with that config. The CLI checks the version, removes it from the uploaded config and sends it as the deployment’s runtime version. It is not the service’s pin: a redeploy from the portal, or a change of the pin, does not carry it. To keep the service itself on a version, pin it in the portal or with gpilot service runtime pin.

A withdrawn version can no longer be chosen or deployed. A service that runs one is flagged in the portal. What moves it off depends on its pin:

  • Not pinned, or pinned to a supported version: redeploy it. The deployment uses the pinned version, or else the stable version, which is never a withdrawn one.
  • Pinned to a withdrawn version: every deployment of the service that names no version is refused, including one from the portal that keeps the default Proxy version and a gpilot deployment create without a [runtime] version. The service is not moved to the stable version instead. A deployment you request is refused before it is created, with RUNTIME_VERSION_WITHDRAWN in the API error, so gpilot exits with 4. A redeploy that GraphPilot starts on its own is created and fails before anything is built, with the same message on the deployment. Nothing is built or activated for a refused deployment, so a deployed service keeps serving the version it already runs. Pin a supported version, or remove the pin with gpilot service runtime unpin or in the portal; either change redeploys the service, unless you choose to apply it with the next deployment in the portal. A pin on a version that is no longer in the catalog is treated the same way, and the portal flags it on the Runtime settings page and in the deployment dialog.

A deployment that names a supported version itself, with [runtime] version or under Proxy version in the portal’s deployment dialog, is not refused, whatever the service’s pin says.

1.8.1

· Stable

1.8.0

1.7.0

1.6.0

1.5.0

1.4.0

1.3.1

1.3.0

1.2.0

1.1.0

1.0.1

1.0.0