Gitlab runner upgrade removes all cache (volumes)

Summary

When upgrading the gitlab runner on my build server, it reports that it's removing all dangling volumes. Which is perfectly ok. But it shows explicitly that it deletes the cache volumes. And yes, when running a build job in CI in Gitlab, all cache is gone and it needs to rebuild that from the 1st job.

Is this intentional? I would expect the cache to be not removed, when upgrading. Otherwise I have to refrain from updating the gitlab-runner in the future. This happens on Ubuntu 22.04, with gitlab runner 15.10.1, but I noticed it happening with the previous upgrade as well. (Probably 15.10.0)

Setting up gitlab-runner (15.10.1) ...
GitLab Runner: detected user gitlab-runner
Runtime platform                                    arch=amd64 os=linux pid=3957801 revision=dcfb4b66 version=15.10.1
gitlab-runner: the service is not installed
Runtime platform                                    arch=amd64 os=linux pid=3957847 revision=dcfb4b66 version=15.10.1
gitlab-ci-multi-runner: the service is not installed
Runtime platform                                    arch=amd64 os=linux pid=3957935 revision=dcfb4b66 version=15.10.1
Runtime platform                                    arch=amd64 os=linux pid=3958016 revision=dcfb4b66 version=15.10.1

Check and remove all unused containers (both dangling and unreferenced) including volumes.
------------------------------------------------------------------------------------------
Deleted Volumes:
runner-w5y64d4e-project-18-concurrent-0-cache-3c3f060a0374fc8bc39395164f415a70
runner-w5y64d4e-project-34-concurrent-0-cache-3c3f060a0374fc8bc39395164f415a70