moveit: 2.5.7-1 in 'humble/distribution.yaml' [bloom]

[sea-bass]

Increasing version of package(s) in repository moveit to 2.5.7-1:

• upstream repository: https://github.com/ros-planning/moveit2.git
• release repository: https://github.com/ros2-gbp/moveit2-release.git
• distro file: humble/distribution.yaml
• bloom version: 0.12.0
• previous version for package: 2.5.6-1

chomp_motion_planner

• No changes

moveit

• No changes

moveit_chomp_optimizer_adapter

• No changes

moveit_common

• No changes

moveit_configs_utils

* Added joint limits to rviz launch file. (#3091 <https://github.com/ros-planning/moveit2/issues/3091>) (#3136 <https://github.com/ros-planning/moveit2/issues/3136>)
* Contributors: Matthew Elwin

moveit_core

* Bug fix: RobotTrajectory append() (#1813 <https://github.com/ros-planning/moveit2/issues/1813>) (#1821 <https://github.com/ros-planning/moveit2/issues/1821>)
* Contributors: AndyZe

moveit_hybrid_planning

• No changes

moveit_kinematics

• No changes

moveit_planners

• No changes

moveit_planners_chomp

• No changes

moveit_planners_ompl

• No changes

moveit_plugins

• No changes

moveit_resources_prbt_ikfast_manipulator_plugin

• No changes

moveit_resources_prbt_moveit_config

• No changes

moveit_resources_prbt_pg70_support

• No changes

moveit_resources_prbt_support

• No changes

moveit_ros

• No changes

moveit_ros_benchmarks

• No changes

moveit_ros_control_interface

• No changes

moveit_ros_move_group

• No changes

moveit_ros_occupancy_map_monitor

• No changes

moveit_ros_perception

• No changes

moveit_ros_planning

* Add sleep in setup of flaky PSM test fixture (#3126 <https://github.com/ros-planning/moveit2/issues/3126>)
* Contributors: Sebastian Castro

moveit_ros_planning_interface

* Enhancement/moveit ros1 ports (backport #3041 <https://github.com/ros-planning/moveit2/issues/3041>) (#3118 <https://github.com/ros-planning/moveit2/issues/3118>)
* Contributors: Tom Noble, Mark Johnson

moveit_ros_robot_interaction

• No changes

moveit_ros_visualization

* Fix MeshShape::clear() for safer mesh removal (#3164 <https://github.com/ros-planning/moveit2/issues/3164>) (#3166 <https://github.com/ros-planning/moveit2/issues/3166>)
* Contributors: Matt Wang

moveit_ros_warehouse

• No changes

moveit_runtime

• No changes

moveit_servo

• No changes

moveit_setup_app_plugins

• No changes

moveit_setup_assistant

• No changes

moveit_setup_controllers

• No changes

moveit_setup_core_plugins

• No changes

moveit_setup_framework

• No changes

moveit_setup_srdf_plugins

• No changes

moveit_simple_controller_manager

• No changes

pilz_industrial_motion_planner

* Fix: Resolve race condition in MoveGroupSequenceAction (backport #3125 <https://github.com/ros-planning/moveit2/issues/3125>) (#3127 <https://github.com/ros-planning/moveit2/issues/3127>)
* Enhancement/moveit ros1 ports (backport #3041 <https://github.com/ros-planning/moveit2/issues/3041>) (#3118 <https://github.com/ros-planning/moveit2/issues/3118>)
* Contributors: Maxwell.L, Tom Noble, Mark Johnson

pilz_industrial_motion_planner_testutils

• No changes

[github-actions]

Thanks for sending a pull request to ROS distro!

This is an automated tool that helps check your pull request for correctness.
This tool checks a number of attributes associated with your ROS package and generates a report that helps our reviewers merge your pull request in a timely fashion. Here are a few things to consider when sending adding or updating a package to ROS Distro.
ROS Distro includes a very helpful CONTRIBUTING.md file that we recommend reading if it is your first time submitting a package.
Please also read the ROS Distro review guidelines which summarizes this release process.

ROS Distro Considerations

• ROS Distributions are created using REP-134 Standards Track as a guide.
• Your package name should comply to REP-144 ROS Package Naming
• Your package must build for all platforms and architectures on the ROS buildfarm. See REP-2000 ROS Releases and Supported Platforms for all supported platforms for your ROS Distro.
• Your package must contain an OSI approved license. Your package.xml file must also include that license in a machine readable format. See REP-149 Package Manifest Format Three Specification for additional details.
• A publicly available, open source, repository for your ROS package.
• While not required, we recommend that you create an account for ROS Discourse and subscribe to the appropriate release topic.
• If you would like, you may join our Discord Server and ask questions in the #infra-help channel.

Package Considerations

Having your package included in a ROS Distro is a badge of quality, and we recommend that package developers strive to create packages of the highest quality. We recommend package developers review the following resources before submitting their package.

• REP-2004 Package Quality Declaration-- The ROS 2 TSC has created a quality rating system for ROS packages. These ratings should serve as a guide for package developers. We recommend package developers achieve a quality level of three or higher.
• Documentation -- it is recommended that ROS packages include an extensive README.md file, and API level documentation using the Sphinx documentation system.
• Maintainer Responsibilities -- the ROS 2 documentation includes a guide to ROS package maintainer responsibilities that summarizes your responsibilities as an open source maintainer. While we do not enforce these requirements on package maintainers they should be considered best practices.
• We recommend that your package should strive to conform to the ROS 2 Developer Guide and the ROS 2 Style Guide.

Need Help?

Please post your questions to Robotics Stack Exchange or refer to the #infra-help channel on our Discord server.

---

For changes related to yamllint:

• ✅ All new lines of YAML pass linter checks