Hashed Storage: trigger migration to hashed storage via post-deployment migration
In %13.0 we enabled Hashed Storage for everyone. As part of the release post we recommended people to upgrade the remaining legacy storage applications, and gave them a planned 2 releases without automatically migrating. We missed the planned %13.2 release as the one we said we would start to automatically migrating the remaining projects.
We should trigger that in %13.4 and add that to the release post.
With that we can consider that any instance with %13.4 or later should be using Hashed Storage (if for any reason there are still projects that failed to migrate, will trigger a warning when running gitlab-rake gitlab:check
Edited by Gabriel Mazetto