Adding a comment to say that this issue still occurs in 1.19. The workaround I have found is to send a different URL with the new hash to the client, this causes the old pack to be correctly deleted and the new one to be downloaded and applied correctly.
SyntheticDev
Adding a comment to say that this issue still occurs in 1.19.
The workaround I have found is to send a different URL with the new hash to the client, this causes the old pack to be correctly deleted and the new one to be downloaded and applied correctly.