gstack-upgrade

To upgrade gstack, the skill detects your installation type and applies the appropriate update path. It safely handles global, local, and vendored installations by fetching updates and running setup scripts to ensure version parity.

The safest way to update a vendored gstack installation is using an automated upgrade workflow. The process stashes local changes, resets to origin/main, and syncs the vendored copy from the primary install to keep environments aligned.

gstack version management handles local changes by automatically stashing them before an upgrade. It fetches the latest updates, resets the environment to origin/main, and provides rollback notes to ensure a safe version transition.

Yes, you can use shell automation to sync gstack across deployment contexts. The skill implements an end-to-end upgrade workflow that detects install types and syncs local vendored copies to maintain feature parity across environments.

Upgrading gstack provides rollback notes after executing the upgrade workflow. While it safely stashes local changes and resets to origin/main, the post-upgrade messaging includes instructions to revert if the new version causes issues.

Install-type detection is needed in a gstack upgrade workflow to apply the correct update path. Distinguishing between global, local, and vendored installations ensures the setup script runs appropriately for each specific deployment context.