Okay, yeah, sequence: 1. I was intending to tag https://github.com/pantsbuild/pants/commit/48b2f737e3953257a07188f9332eb01c79d00dc1 2. I was on https://github.com/pantsbuild/pants/commit/c15e54e5c8100a7d8638589bc6f675a95e7c49e9 and didn't double check properly (sorry 😞 ) 3. the

release.py tag-release

command tagged that commit with

2.21.0.dev0

then force pushed, that tag already existed earlier in https://github.com/pantsbuild/pants/commit/2e5c50511f809aa3c007bb54924277c3b0348f64 (and has been released) 4. I cancelled the release CI https://github.com/pantsbuild/pants/actions/runs/8147336570 before it attempted too upload new artifacts So, I think there's two steps: 1. I'll retag

2.21.0.dev0

back to how it was (and cancel the CI again, just put the tag back to how it was) 2. make the script not do a force push by default 🙂

(I'll wait a bit before doing the retagging, to give time for y'all to offer opinions.)

It happens

PR for the script adjustment: https://github.com/pantsbuild/pants/pull/20640 (cancelled CI for the retag https://github.com/pantsbuild/pants/actions/runs/8148665908)