gstack-upgrade

Upgrading a vendored gstack installation synchronizes your local copy while preserving modifications. It detects the vendored install type, stashes local changes, runs the upgrade, and restores your custom configurations from backups automatically.

Upgrading gstack handles auto-upgrade prompts by offering snooze or never options before applying updates. It detects your installation type, executes the appropriate git or vendored upgrade steps, and manages snooze logic automatically.

Seeing what's new after updating gstack involves extracting changelog entries between your old and new versions. The upgrade process automatically summarizes user-facing changes, providing a concise overview of what changed in the release.

Rolling back a failed gstack setup from a backup is supported during the upgrade flow. If the setup step fails after upgrading, the process automatically restores your previous installation from preserved backups to ensure system stability.

The gstack upgrade process works for both global git and local repo installs by detecting the specific installation type. It selects the appropriate upgrade flow, whether it is global-git, local-git, or vendored, and executes the corresponding steps.

Your gstack upgrade requires synchronizing a separate local vendored copy to ensure project-embedded dependencies match the newly upgraded version. This synchronization happens automatically when a vendored copy is detected, keeping your project consistent.