You as the upstream developer make a release of the upstream package. Which results in a tag on the upstream repository 0.3.1
But your pull request releases the packge into the kinetic rosdistro. This is the release that most people care about and track. When we’re preparing for a sync we have a quiet period where we prevent releases into the rosdistro to make sure that we can run tests and be confident that things have built fully. In this case by default I held any new releases starting Wednesday until I ran the sync today on Friday.
I see that you’ve fixed your master branch and the devel job is passing, but until you release your source code with a new version and rerun bloom to create a new release into kinetic the build failures will not be fixed for anyone using kinetic unless the explicitly ask for the upstream devel branch from source which is unusual and not generally recommended as that’s unreleased code and not guaranteed to be compatible if the maintainer is doing a coordinated release or refactoring is in process.