This is not the approach we do. What you have is a burned release and it stays unmodified in the repository. We do not rewrite history on master and tags. The single source of truth is source-release.zip which is not available on dist, so everything is good.
So fix your bugs and start a new release n+1. That's it. Don't forget to assign the issues in JIRA to the new release too. So you basically retain n+1 fix versions, just like a did for Resolver with two failed releases. > Gesendet: Sonntag, 11. Oktober 2020 um 22:16 Uhr > Von: "Elliotte Rusty Harold" <[email protected]> > An: "Maven Developers List" <[email protected]> > Betreff: Rollback failed release > > I cancelled a planned release of the maven-dependency-plugin before it > got to a vote but after it had been pushed to Github. (discovered a > couple of issues I want to fix first) > > I dropped the bundle from Nexus. Now I need to revert the last couple > of commits and remove the tag. They're about three different ways to > do this in git, e.g. throwing away the last couple of commits or > creating a new commit that undoes the effects of the old commits but > does not remove them from the history. Anyone happen to know what's > preferred in this scenario? Thanks. > > -- > Elliotte Rusty Harold > [email protected] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
