moveit_msgs icon indicating copy to clipboard operation
moveit_msgs copied to clipboard

Published 20 hours ago • verified publisher icon ros-planning

Missing release

Open urfeex opened this issue 5 months ago • 6 comments

Hi, https://build.ros2.org/job/Kbin_uN64__moveit_ros_move_group__ubuntu_noble_amd64__binary/19/console indicates that a release containing #186 should be made :-)

urfeex avatar Jul 04 '25 07:07 urfeex

@rhaschke @nbbrooks @sjahr I hope you don't mind me pinging you directly. I believe releasing this would fix a lot of the regressions mentioned in https://discourse.ros.org/t/preparing-for-rolling-sync-2025-07-14/45172

urfeex avatar Jul 14 '25 06:07 urfeex

Thanks for the mention - I do not have a good workflow for tracking the release process and moveit related regressions right now.

I will trigger moveit_msg releases for rolling and kilted (I believe I branched moveit2 kilted branch from main after 186 was merged in).

nbbrooks avatar Jul 14 '25 16:07 nbbrooks

Status pages are the best way to track things - you can search by "moveit" as well: https://repo.ros2.org/status_page/ros_rolling_default.html

(I also struggle to find these, so I have the full list of relevant status pages linked at the bottom of my cookbook: https://github.com/mikeferguson/ros2_cookbook?tab=readme-ov-file)

mikeferguson avatar Jul 14 '25 17:07 mikeferguson

They're linked from their respective docs.ros.org pages:

Image

This one for Jazzy on Ubuntu Noble fi.

gavanderhoorn avatar Jul 14 '25 17:07 gavanderhoorn

I am trying to do the Subsequent Release instructions without a GH classic token with workflow scope (since the ROS docs were written, I believe workflow scope now requires full private repo access which is not acceptable). I though I had done the previous moveit release with only workflow scope, but not sure how I got around this set of errors in bloom-release

! [remote rejected] debian/kilted/bookworm/moveit_msgs -> debian/kilted/bookworm/moveit_msgs (refusing to allow a Personal Access Token to create or update workflow.github/workflows/format.ymlwithoutworkflow scope)

The ros2-gbp/moveit_msgs-release/ branches are pushed up but I do not know what steps to do next manually,

Has anyone done this last part manually that the workflow normally does?

nbbrooks avatar Jul 14 '25 18:07 nbbrooks

Just did it [painfully] manually for https://github.com/ros/rosdistro/pull/46901 and https://github.com/ros/rosdistro/pull/46902 by copy pasting the pattern in some previous moveit_msgs updates in rosdistro

nbbrooks avatar Jul 14 '25 22:07 nbbrooks