All good. We have eyes on this issue and will be issuing a fix.
Tag name resolution at /tag/name should and must remain compatible, this is an explicit choice and decision we’ve made. But I think in this case it’s a number so perhaps the name resolution must have gone wrong at the backend.