A while back there were some changes that were made to Wrangler 1.x in regards to causing expiration of KV content to be delayed when a new deployment happens, on the basis, it seems that this would help avoid clients getting HTTP 404 errors. This behavior seems (looking at code for Wrangler 1.x) to be connected with the 'publish' command.