ros2_kortex: 0.2.3-1 in 'humble/distribution.yaml' [bloom]

[aalmrad]

Increasing version of package(s) in repository ros2_kortex to 0.2.3-1:

• upstream repository: https://github.com/Kinovarobotics/ros2_kortex.git
• release repository: https://github.com/ros2-gbp/ros2_kortex-release.git
• distro file: humble/distribution.yaml
• bloom version: 0.12.0
• previous version for package: 0.2.2-1

kinova_gen3_6dof_robotiq_2f_85_moveit_config

* Repo update (#220 <https://github.com/Kinovarobotics/ros2_kortex/issues/220>)
  * Updating MoveIt configurations
  * Updating and restructuring instructions
* Update planner_plugin parameters (#199 <https://github.com/Kinovarobotics/ros2_kortex/issues/199>)
* Remove outdated config artifacts (#198 <https://github.com/Kinovarobotics/ros2_kortex/issues/198>)
* Cleanup robots for visualization & sim (#180 <https://github.com/Kinovarobotics/ros2_kortex/issues/180>)
* Update planning pipeline configurations (#187 <https://github.com/Kinovarobotics/ros2_kortex/issues/187>)
* Contributors: Marq Rasmussen, Sebastian Castro, Sebastian Jahr, smoya23

kinova_gen3_7dof_robotiq_2f_85_moveit_config

* Repo update (#220 <https://github.com/Kinovarobotics/ros2_kortex/issues/220>)
  * Updating MoveIt configurations
  * Updating and restructuring instructions
* Update planner_plugin parameters (#199 <https://github.com/Kinovarobotics/ros2_kortex/issues/199>)
* Remove outdated config artifacts (#198 <https://github.com/Kinovarobotics/ros2_kortex/issues/198>)
* Cleanup robots for visualization & sim (#180 <https://github.com/Kinovarobotics/ros2_kortex/issues/180>)
* Update planning pipeline configurations (#187 <https://github.com/Kinovarobotics/ros2_kortex/issues/187>)
* Contributors: Marq Rasmussen, Sebastian Castro, Sebastian Jahr, smoya23

kinova_gen3_lite_moveit_config

* Fixed the Gazebo Fortress Simulation + Separated the arm and gripper control for Gen3_Lite + Fixed bugs (#252 <https://github.com/Kinovarobotics/ros2_kortex/issues/252>)
  * Modified the Gen3_Lite Moveit Package for arm-gripper control separation
* Added a Moveit2 package for Gen3-Lite (#231 <https://github.com/Kinovarobotics/ros2_kortex/issues/231>)
* Contributors: aalmrad

kortex_api

• No changes

kortex_bringup

* Separated the arm and gripper control for Gen3_Lite + Fixed bugs (#252 <https://github.com/Kinovarobotics/ros2_kortex/issues/252>)
  * Separated the arm and gripper controllers for Gen3_Lite in Kortex_bringup
* Added the empty gripper option for gen3.launch.py (#242 <https://github.com/Kinovarobotics/ros2_kortex/issues/242>)
* Fix mock_hardware and enable simulating gen3_lite (#196 <https://github.com/Kinovarobotics/ros2_kortex/issues/196>)
  * Add additional guards if user sets use_fake_hardware and use_internal_bus_gripper_comm true
* Contributors: Marq Rasmussen, aalmrad, smoya23

kortex_description

* Added a missing robot description argument: "moveit_active" (#253 <https://github.com/Kinovarobotics/ros2_kortex/issues/253>)
* Added the empty gripper option for gen3.launch.py (#242 <https://github.com/Kinovarobotics/ros2_kortex/issues/242>)
* Modified the joint limits of Gen3 and Gen3 Lite robots as per the values in the User Guides (#241 <https://github.com/Kinovarobotics/ros2_kortex/issues/241>)
* Added  .STL files for the Gen3 7dof meshes (#235 <https://github.com/Kinovarobotics/ros2_kortex/issues/235>)
* Repo update (#220 <https://github.com/Kinovarobotics/ros2_kortex/issues/220>)
  * Creating Gen3 Lite specific instructions and launch file
  * Updating MoveIt configurations
  * Updating and restructuring instructions
* Update gripper descriptions for use on HW (#206 <https://github.com/Kinovarobotics/ros2_kortex/issues/206>)
  Pass though more hardware parameters for gripper control:
  * use_internal_bus_gripper_comm: specify if gripper comms will pass
  through the robot internally
  * (gripper_)com_port: specify the port the gripper can be exected on
  Use internal comm param in gripper macros:
  * Consider use_internal_bus_gripper_comm param in determination
  for whether or not to launch a ros2_control instance for the gripper. If
  use_internal_bus_gripper_comm is false and we're not running in
  simulation, that means we're expecting to communicate with the gripper
  via USB and we'll need to launch a separate ros2_control instance to
  control it.
  Add documentation on load_robot macro parameters
* fake_components->mock_components (#197 <https://github.com/Kinovarobotics/ros2_kortex/issues/197>)
* Fix mock_hardware and enable simulating gen3_lite (#196 <https://github.com/Kinovarobotics/ros2_kortex/issues/196>)
  * Add additional guards if user sets use_fake_hardware and use_internal_bus_gripper_comm true
* Update gen3 lite and gripper macros (#191 <https://github.com/Kinovarobotics/ros2_kortex/issues/191>)
* Fix wrist with vision mesh (#195 <https://github.com/Kinovarobotics/ros2_kortex/issues/195>)
* Fix mention of nonexistent STL file (#194 <https://github.com/Kinovarobotics/ros2_kortex/issues/194>)
* Enable initial position param in kinova xacros (#190 <https://github.com/Kinovarobotics/ros2_kortex/issues/190>)
* Cleanup robots for visualization & sim (#180 <https://github.com/Kinovarobotics/ros2_kortex/issues/180>)
* Contributors: Abishalini Sivaraman, David Yackzan, Marq Rasmussen, aalmrad, smoya23

kortex_driver

* Add force and velocity hardware interfaces (#204 <https://github.com/Kinovarobotics/ros2_kortex/issues/204>)
  Co-authored-by: Ashton Larkin <mailto:[email protected]>
* Contributors: Paul Gesel

[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