Closed clalancette closed 6 months ago
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code
@clalancette @boxanm See comment in libnabo PR 135
@boxanm I'll take care of it, just adding you as a reviewer to keep you in the loop.
Thanks for merging and tagging!
Description
Do a release of 1.4.1 for libpointmatcher
Summary:
The source release of 1.4.0 was done on this repository without bumping the package.xml version. This means that that version cannot be released on the ROS 2 buildfarm to fix https://build.ros2.org/view/Rbin_uN64/job/Rsrc_uN__libpointmatcher__ubuntu_noble__source/
Instead of moving the tag or any other git shenanigans, just make a new release 1.4.1 that properly updates the CHANGELOG and bumps the package.xml. Once this is merged in, I'll need one of the maintainers to also create a tag (1.4.1), at which point we can bloom-release this and fix the build on the ROS 2 buildfarm.
Changes and type of changes (quick overview):
Checklist:
Code related
PR creation related
base ref
branch is set to thedevelop
branch (the build-system won't be triggered otherwise)develop
branch (the build-system will reject it otherwise)PR description related
# <issue-id>
if changes are of typefix
feat
fix
docs
style
refactor
perf
test
build
ci
chore
revert
<type>!
Note for repository admins
Release PR related
push/merge
on the default branch (ie:master
) and therelease
branch.draft
mode until all the release reviewers are ready to push the release.release
->master
branch is created (not in draft mode),