Skip to content
sprigsprigsprig

Upgrades

sprig ships as a versioned distribution. An upgrade is:

Terminal window
git pull                       # or unpack the new distribution
./sprig azure deploy           # rebuild + redeploy platform code
./sprig azure smoke            # verify

When a release notes changes to the resource or Entra layer, additionally re-run the installer — it is idempotent and converges the environment:

Terminal window
cd infra && ./install.sh -s <subscriptionId> --what-if   # review the delta
./install.sh -s <subscriptionId>

Compatibility promises

Section titled “Compatibility promises”
  • sprig-install.json remains valid across upgrades; builder machines don’t need reconfiguration for platform-code updates.
  • Published apps are untouched by platform upgrades — they are static resources in builder sandboxes.
  • Breaking changes to the plugin (skill paths, script flags) are called out in the changelog and require builders to update their plugin copy.