Open Lastique opened 2 months ago
Apparently, git tags in submodules are created manually, as described here:
At the point of this issue creation, this section did not contain a command to actually checkout the submodules at revisions referenced by the superproject, which means the tags in submodules could be created at incorrect commits. The command has been added now. Also, the tags for Boost 1.85.0 have been fixed.
I'm leaving this issue open as I believe tagging should be done automatically during release CI to eliminate the possibility of errors in the future.
This was reported by multiple library maintainers on the ML. Boost release tags that are set in git submodules point to wrong commits in some cases.
The following script shows the problematic submodules:
This will show the list of submodules, for which the currently checked out commit (i.e. the submodule's boost-1.85.0 tag) doesn't match the commit referenced by the superproject. The commit SHA it'll show is the commit referenced by the superproject.
The output on my machine is: