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
- Read the release notes of every version between yours and the target, on the feed’s package page.
- Check the signatures of the new packages (Checking a package’s signature).
- Note your current version: it is your rollback.
Upgrade the services
- Change the one version property of your central package management, or every Router
PackageReference, to the new version. - Restore and update the lock files:
dotnet restore --force-evaluate, then commit the changedpackages.lock.jsonfiles. - Build. Treat new
STELLAdiagnostics as you would compiler errors: they describe endpoints the gateway would not serve as you expect. - 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
- Gateway and services of one release go together. Upgrade the gateway first, then the services, one instance at a time, within one maintenance window.
- Mixed versions during the window. Instances of the old and the new release connect to the gateway side by side; callers that send no
X-Api-Versionreach both, and callers that send it reach only that version (Rolling updates). - Rolling restart. Each stopping instance reports
Drainingand finishes its requests in flight withinDrainDeadline.
After the upgrade
GET /health/readyanswers200and the instance list shows every service.- The service logs show
Discovered <n> endpoints via source generationwith the expected counts. - Assemblies of a release carry the metadata
StellaOps.Component.PublishedAt; a build without it is not a release build.
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.
