-
Notifications
You must be signed in to change notification settings - Fork 5
Home
Once the HEBI C++ API is released and ready, go to this workflow and click “Run workflow” with the default options:
- Branch:
develop - Version: leave blank (it will use the value from the
VERSIONfile).
This action will create a PR in this repo. Test the changes locally, and if everything works, go ahead and merge.
Then, create a release in this repo using the change logs from the C++ API.
To release, you need to be listed as a maintainer in the rosdistro repo for the HEBI Robotics org. Currently, Hariharan and Chris are the maintainers.
📖 Reference: ROS 2 Release Guide
These steps assume you already have the dependencies installed and a Bloom PAT token set up. If not, follow the reference link first.
Note: Even though I added credentials to
~/.config/bloom, Bloom still asked for them once during the process. After that, it stopped asking.
-
Update the changelog
catkin_generate_changelog
- Only edit the entries under the Forthcoming section.
- Pull in details from the C++ changelogs for more context.
- Commit the changes
-
Prepare the release
catkin_prepare_release --bump {major|minor|patch}Or specify directly:
catkin_prepare_release --version VERSION
-
Run the release for each ROS 2 distro
bloom-release --rosdistro humble hebi_cpp_api bloom-release --rosdistro jazzy hebi_cpp_api bloom-release --rosdistro kilted hebi_cpp_api bloom-release --rosdistro rolling hebi_cpp_api
For the username of the PR step, use HebiRobotics, and for the token, use the one listed in 1Password under "ROS2 Release Bloom Token PAT".
If everything works, you’ll see PRs show up in the rosdistro repo. If something breaks, fix it and rerun the steps.