Revoking a deploy token now confirms it worked
Revoking a deploy token left you on a plain error page saying the token was not found, with no sign the revocation had worked. You are now returned to your tokens list with a message confirming which token was deleted.
Revoking a deploy token worked, but it didn’t look like it. You were sent back to that token’s own page — which no longer existed, so you landed on a bare “Token not found” error. The one action where you most want a clear answer gave you something that read like a failure.
You are now returned to your list of deploy tokens, with a message naming the token you just deleted.