gstack-upgrade

To upgrade gstack without losing local changes, the upgrade process detects your installation type and optionally syncs local vendored copies while preserving any user modifications made to the files. It ensures your tooling stays current without overwriting custom configurations.

Upgrading a global gstack installation updates the primary system copy directly, while a vendored deployment upgrade also syncs local project copies to match the upgraded source. The tool automatically detects the install type and applies the appropriate upgrade mechanism.

Yes, the gstack upgrade process reads the VERSION and CHANGELOG.md files to present a concise changelog summary of what's new. This surfaces the latest features and changes for quick decision making before you finalize the rollout.

Yes, the gstack upgrade supports both git-based and vendored deployments by detecting the installation type first. It upgrades the primary copy and can optionally sync local vendored copies to ensure all tooling is in sync with the upgraded source.

You can automate the gstack upgrade by running it as a preamble or a standalone command within your DevOps workflow. This streamlines version control and automation by upgrading the primary copy and syncing vendored copies without manual intervention.

The gstack upgrade focuses specifically on upgrading the gstack tool and syncing vendored copies while preserving user changes. It does not manage broader version control operations or dependencies outside of the gstack ecosystem.