updating-upstream

To update git submodules automatically, this Skill scans your `.gitmodules` file, identifies eligible submodules, and fetches their latest stable tags while avoiding pre-release versions. It ensures dependencies are current and consistent across your projects with minimal manual effort.

Automated dependency management uses atomic commits, creating one commit per submodule update. This enforces safety checks and maintains a clear version control history, allowing you to easily rollback a specific submodule update if needed.

No, you cannot use this to update submodules managed by lockstep. The Skill specifically scans `.gitmodules` and filters out lockstep-managed dependencies, targeting only those eligible for independent automated updates to their latest stable versions.

The best way to avoid pre-release versions when updating git submodules is to use an automated tool that applies safety checks. This Skill specifically targets stable upstream tags and filters out pre-releases during the dependency update process.

Updating upstream submodules is designed to require minimal manual intervention. The Skill automates fetching the latest stable tags and handles version comments in `.gitmodules`, creating atomic commits so you can safely rollback if conflicts or issues arise.