catkin_prepare_release pushes twice w/o incrementing tag?

edit

I ran catkin_prepare_release once for the metapackage I maintain, then in its commit history, you can see commit message 0.2.12 twice on the same timestamp. Looking into the changes in each commit, the version defined in package.xml is incremented so that the latest is 0.2.13. However the latest tag in the github repository still remains as 0.2.12.

To summarize what I did not intend:

• Committed twice by running catkin_prepare_release only once
• If committing twice is necessary, tag is not yet updated in the 2nd commit

Is this intended behavior? If so, what steps are the next? I haven't notified buildfarm since this looks not good to me.

I admit that I was working in public wifi which might not be recommended for critical tasks like this, but I don't think the connection wasn't too bad.

Thanks!

ros-groovy-catkin 0.5.65-3quantal-20130325-0722-+0000

Update) command suggested by catkin_prepare_release:

../../../../../../../../../opt/ros/groovy/bin/catkin_package_version --bump patch . && git commit -m "0.2.12" rqt_runtime_monitor/package.xml rqt_robot_steering/package.xml rqt_tf_tree/package.xml rqt_robot_dashboard/package.xml rqt_pose_view/package.xml rqt_nav_view/package.xml rqt_robot_plugins/package.xml rqt_rviz/package.xml rqt_robot_monitor/package.xml && git push && git tag 0.2.12 && git push --tags