ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

bloom-release: How to over-write latest release

asked 2014-01-31 08:11:26 -0500

czalidis gravatar image

updated 2014-01-31 09:28:56 -0500

I have updated my release repo running bloom-release but now I want to update that release over-writing previous commits and tags. One way is to do it manually, using git, resetting each branch/tag to previous state and then running bloom-release again, but I am searching for a more elegant way.

EDIT: I have cancelled the pull request to rosdistro at the end of bloom-release script, so the release is only in my release repo.

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2014-01-31 08:35:47 -0500

William gravatar image

You should never "overwrite" a release. Once a version, say 0.1.0-0 is released, people are referencing it and it should not be changed.

If you need to release version 0.1.0 again, just run bloom-release again and it will automatically increment the release version, so it would become 0.1.0-1.

edit flag offensive delete link more


I have canceled the pull request to rosdistro, so the release is only in my -release repo. I want to do the same release due to a typo, so i don't want to increase the build number without a reason.

czalidis gravatar image czalidis  ( 2014-01-31 09:19:05 -0500 )edit

Version numbers are free. Use another.

ahendrix gravatar image ahendrix  ( 2014-01-31 12:11:43 -0500 )edit

@czalidis in that case there is no one referencing it, but there is no easy way to do this, bloom is setup to explicitly not overwrite releases because often they are already referenced. Manually resetting the branches and tags is about the only thing you could do.

William gravatar image William  ( 2014-01-31 15:48:30 -0500 )edit

Thanks for your time anyway! I have done in once in the past manually and it is a lot of work to reset each branch/tag properly. I was asking only because I saw: "git push --all && git push --tags # You might have to add --force to the second command if you are over-writing existing tags" in bloom-release script.

czalidis gravatar image czalidis  ( 2014-02-01 00:00:28 -0500 )edit

Question Tools

1 follower


Asked: 2014-01-31 08:11:26 -0500

Seen: 207 times

Last updated: Jan 31 '14