gstack-upgrade

You can automate gstack upgrades by invoking the upgrade Skill, which detects your installation type and applies the latest version globally or locally. It handles required migrations and provides safe rollback options for consistent updates.

The best way to handle gstack migrations is to run the automated upgrade flow, which identifies your installation type and applies necessary version migrations. This ensures consistent updates across global, local, and vendored environments.

Yes, the gstack upgrade process includes safe rollback handling for failed migrations. It coordinates install-type detection and applies upgrades with rollback options to ensure you can recover from errors.

Yes, you can automate upgrades for both global and local gstack installs using the upgrade Skill. It detects global git, local git, and vendored installations, then upgrades each environment to the latest version automatically.

Upgrading gstack across vendored and git-based installations requires migration tooling to handle structural differences between installation types. The upgrade process coordinates these migrations to ensure consistent, auditable updates across all environments.

Manually upgrading gstack is error-prone and time-consuming because you must individually detect installation types, apply migrations, and manage rollbacks across global, local, and vendored environments without automated coordination.