* a bump of the version that should have happened in the last release [c9f543e](https://github.com/galaxyproject/planemo/commit/c9f543ea56aa280131bafe91e8e60fb7aab614a9)

If you are going to do the release via pull request like in this case (which I find preferable), you need to use make commit-version instead of make release-local , otherwise the version gets bumped again to the next dev0 prerelease by new-version .

If you are going to do the release via pull request like in this case

I did not intend to do a release with this PR. My idea was just to finish what should have happened when I would have followed the guidelines.

which I find preferable

You mean a PR that bumps the version. And then creating the release via the GH interface? I guess we can do this (seems simpler). But then we should always do it this way (and document it), or?

Disadvantage would be that we would not have the ....dev0 version in the master branch (or we would need another PR).

If you are going to do the release via pull request like in this case

I did not intend to do a release with this PR. My idea was just to finish what should have happened when I would have followed the guidelines.

The PR title starts with "Finish release" :D

which I find preferable

You mean a PR that bumps the version. And then creating the release via the GH interface? I guess we can do this (seems simpler). But then we should always do it this way (and document it), or?

Yes, that would be my preference.

Disadvantage would be that we would not have the ....dev0 version in the master branch (or we would need another PR).

That's the same of the Galaxy release process (separate PRs to bump the final and pre-release versions).

That seems like a pain, it takes me a minute to cut a new release but if I do it this new way it's at least 2 PRs ...

@mvdbeek I find the Makefile workflow kinda brittle, but you are the one doing most releases, so I'm happy to keep it as it is. I can still do it half-manually if I need to.

Thanks @nsoranzo and @mvdbeek . I will try to create a release using the documented process.

Not there yet #1609 .. but close