gstack-upgrade

Automating a gstack upgrade involves invoking a dedicated workflow that detects your installation type, performs a safe upgrade with backups, and syncs local vendored copies. You initiate the process by running the /gstack-upgrade command.

Upgrading a vendored gstack installation can be done safely by detecting the local source, applying the upgrade, and running a post-upgrade sync. The workflow includes safeguards and rollback options to prevent breaking local dependencies.

Handling a gstack version upgrade across multiple environments requires detecting whether the installation is global git, local git, or vendored. The automation workflow then applies the appropriate upgrade path and displays the changelog for verification.

The gstack upgrade process supports automatic rollback if the new version fails by utilizing safety checks and backups created before the upgrade. This ensures your environment reverts to its previous working state if errors occur.

A gstack upgrade shows a changelog after updating from a global git source to surface what is new to the user. This step is part of the multi-step workflow designed to verify the successful application of the latest version.

You need to sync local vendored copies after a gstack upgrade when your environment uses vendored sources. The workflow performs a post-upgrade sync automatically to ensure all local copies match the newly installed latest version.