rcourtman 41abdd0b2c Let provider MSP upgrade.sh move an install to a new release ... setup.sh resolves the image pins in .env to digests once, so upgrade.sh only ever re-pulled the release a provider first installed. Moving to a new release meant finding the new digests by hand, so none of a release's fixes, and no new feature such as the portal Plan tab, reached an existing install. Run from a newly extracted release bundle, upgrade.sh now works on the existing install: it resolves the bundle's control-plane and runtime tags to digests, runs the status gate, preflight and verified backup with the new release's control plane through a shell override while nothing on disk changes, then keeps a copy of .env, installs the bundle files and writes the new pins before starting the new images. --keep-image-pins keeps hand-set pins. It also pulls the tenant runtime image before the first status check, which otherwise failed every upgrade to a new CP_PULSE_IMAGE with "not present locally", including the documented pin-editing route.		2026-09-24 10:43:01 +01:00
..
helm/pulse	Prepare v6.4.3-rc.1 release	2026-09-01 21:37:41 +01:00
provider-msp	Let provider MSP upgrade.sh move an install to a new release	2026-09-24 10:43:01 +01:00