Hi Thomas,
We added a function to run the git fetch tags --prune command in each submodule folder, before we run git submodule status --recursive to get the submodule details. This is to ensure that the latest submodule tags are retrieved when a commit is detected on the main repository.
We haven’t yet added any code to deal with the scenario where a tag is added to a existing commit after the cache as been updated - this would involve a significant amount of work.
When you reset the repository, the latest changeset for each branch should be updated. Additionally, if the “Load any older changesets which have been tagged” option is ticked, the tagged changesets should be updated. These changesets should include the latest tag information for each submodule at the time of the update.
If this is not the case, then we would be interested in seeing a debug log recorded during the time period when the repository is reset, with details of changeset that is not being updated as expected.