With Ignition Dome reaching end-of-life , final releases were made for libraries that had outstanding changes.

A series of options have been added to Ignition CMake so it supports projects that aren’t prefixed by ignition . This made it possible for libSDFormat to leverage Ignition CMake starting from Dome.

Support for GPS (NavSat) sensors has been added to Ignition Sensors and a widget powered by Open Street Map has been added to Ignition GUI.

IMU sensors now support custom orientation_reference_frame s:

<sensor name='imu_sensor' type='imu'>
    <orientation_reference_frame>
        <localization>CUSTOM</localization>
        <custom_rpy>1.570795 0 0</custom_rpy>
    </orientation_reference_frame>
</sensor>
Battery discharge can now be triggered from a topic.
Releases
These are the minor and patch releases that came out since the previous post.
Ignition CMake 2.10.0 (Citadel, Edifice, Fortress, Garden)
Changelog
Full changelog
Doxygen: allow all .cc, .hh, and CMakeLists.txt, not just in examples/ dir
Pull request #198
Add LEGACY_PROJECT_PREFIX parameter to ign_create_core_library
Pull request #199
Add HIDE_SYMBOLS_BY_DEFAULT parameter to ign_configure_build
Pull request #196
Add Ubuntu Jammy CI
Pull request #194
FindIgnURDFDOM CMake module
Pull request #193
Do not modify CMAKE_FIND_LIBRARY_PREFIXES and CMAKE_FIND_LIBRARY_SUFFIXES on Windows
Pull request #189
Project option: REPLACE_IGNITION_INCLUDE_PATH
Pull request #190
Project option: NO_IGNITION_PREFIX
Pull request #191
Added Logic to flag pointcloud as not dense if invalid point is detected
Pull request #180
IMU custom_rpy  tag parsing added
Pull request #178
              
Thanks for the summary, Louise 
The “Full changelog” links do not actually lead to the changelogs. You need to click the “Changelog” tab on the page the links lead to to get to the changelog. I think that’s because the tabs are just some javascript-fu and have no representation as e.g. URL fragments.
And my personal feeling about these release notifications - I’m more inclined to the way ROS releases are announced on Discourse - one post per ROS version. This kind of summary of changes in all versions looks a bit chaotic. I know Ignition shares the versions of some libraries between different versions, so it might come with some copy-pasting of the same changelog to different posts, but personally, I’d like the one-release-focued announcements more.
 peci1:
The “Full changelog” links do not actually lead to the changelogs. You need to click the “Changelog” tab on the page the links lead to to get to the changelog. I think that’s because the tabs are just some javascript-fu and have no representation as e.g. URL fragments.
Yeah that’s exactly right. I changed the links to GitHub for now.
 peci1:
And my personal feeling about these release notifications - I’m more inclined to the way ROS releases are announced on Discourse - one post per ROS version. This kind of summary of changes in all versions looks a bit chaotic. I know Ignition shares the versions of some libraries between different versions, so it might come with some copy-pasting of the same changelog to different posts, but personally, I’d like the one-release-focued announcements more.
Thanks for the feedback, I’ll consider this for the next one. This one was particularly large because of the holidays and Dome’s EOL, but I expect future announcements to look more focused like the first one.
For completeness, another feedback I got is that the link-back comments on GitHub were very spammy, especially for people following multiple repositories. So I may remove the links on following announcements unless someone objects. I’m also keeping an eye on this feature of discourse-github which may help here.