Hi Fredrik,
Florian can probably explain this better, but AFAIK this is the internal patch-level of the Google Blaze release. When we cut a new Blaze release candidate for Google, we run a huge test suite and occasionally identify breakages that might require a cherry-pick. Those would then cause the patch-level of the RC to get bumped. For example, for 5.0.0-pre.20210604.6 we started with just the baseline, then over time found out that we needed four cherry-picks (only two were relevant and part of Bazel) and had to recreate one release candidate due to maybe an infrastructure flake or something similar. Thus we ended up at .6 :)
When we then create the Bazel rolling release, we just use the literal version number from Blaze for Bazel, too, so that it's easy to automate and will not cause naming conflicts.
Cheers,
Philipp