Upgrading

Every Router release is one line release: all Router packages share one version, built from one commit (Installing Stella Ops packages). An upgrade moves every Router package of a solution, and the gateway, to the new version.

Before you upgrade

  1. Read the release notes of every version between yours and the target, on the feed’s package page.
  2. Check the signatures of the new packages (Checking a package’s signature).
  3. Note your current version: it is your rollback.

Upgrade the services

  1. Change the one version property of your central package management, or every Router PackageReference, to the new version.
  2. Restore and update the lock files: dotnet restore --force-evaluate, then commit the changed packages.lock.json files.
  3. Build. Treat new STELLA diagnostics as you would compiler errors: they describe endpoints the gateway would not serve as you expect.
  4. Run your tests, including in-memory harness tests (Testing with the in-memory harness).

Upgrade the gateway

With the .NET tool:

dotnet tool update StellaOps.Router.Gateway.Host --version <new version> --tool-path /opt/router/tools

With your own host, upgrade its packages as for a service, then build and deploy it.

Order and compatibility

After the upgrade

Rolling back

Install the previous exact version of the tool, or restore the previous package version and lock files, and redeploy. Published versions never change, so a rollback restores the same bytes as before.