Happy to help!

Another thing: It seems that you create a GitHub release, which then creates the tag for you, which then triggers the actual release: https://github.com/scalacenter/sbt-dependency-submission/actions/runs/20231329008.

I recommend to locally tag the release, push the tag, wait for the successful CI pipeline until the artifacts hit maven central and only afterwards create the GitHub release from the then already exsting tag. Because if ci fails, you end up having the release announced on GitHub, with people getting notified - but the artifacts can't be fetched as they are not published (even if you do another release afterwards, IMHO it's bad practise to have a GitHub release page in the archive that does not actually exist)

Just my 2 cents, because I have done the same in the past until I realized that process has flaws.
And sorry for trying to be too smart here ;)

You're probably right here, it's just convenient to do it this way. I'll do it the other way around later.

@tgodzik Can you also force push the v3 tag again? Thanks for all your efforts!