FYI we never had a successful 2.18.0dev2 release. Anyone object to me kicking one off? (it'll take a smidge of coercion as the GitHub actions definition has drifted from the repo. so we'll likely push-and-consume an action tailored to this ref)

We skipped that one on purpose, IIRC

I think it's possible to manually unclog the technical problem. Not high prioirty, but I don't like the asymmetry of the GitHub release 😅

So the manual unclogging we'd do is craft a

release.yml

compatible with that branch, then tell GitHub to run the action from the branch. Note that the action itself still checks out the correct ref of the repo. Just that the top level commands are determined by the hand-crafted yaml (in this case, avoiding references to files that don't exist yet 😛)

This will make the release notes for dev3 weird, because it assumed it was a diff from dev1

Ok