hey fyi the release failed due to the pants_release migration: https://github.com/pantsbuild/pants/actions/runs/5329437767/jobs/9655115214#step:8:13. I'm not sure how we want to deal with it because I already git tagged the commit? So we can't cherry-pick a fix. We'd need to skip the release version, right?

For a dev release, yeah, skipping it is probably fine (one could theoretically delete the git tag and try again, but probably not worth bringing out that nuclear option for 2.18.0.dev2...). Prior art: 2.17.0a0 wasn't published for similar reasons: https://github.com/pantsbuild/pants/blob/main/src/python/pants/notes/2.17.x.md#2170a1-may-19-2023

Thanks. @happy-kitchen-89482 or @broad-processor-92400, do either of you have a chance to fix the blocking issue or revert the changes to use pants_release?

Skipping that version and deleting the tag (for good measure) is probably wise. I will take a swipe at the fix first.

at this point, maybe we wait to do the release on Friday? We'd need to redo the release notes anyways because more things have landed on main. Seems unnecessary for me to do a release today and then you do one on Friday (Benjy you're on release duty)

Yeah we can probably skip this one