ublox_dgnss: 0.5.5-3 in 'jazzy/distribution.yaml' [bloom]

[hortovanyi]

Increasing version of package(s) in repository ublox_dgnss to 0.5.5-3:

• upstream repository: https://github.com/aussierobots/ublox_dgnss
• release repository: https://github.com/ros2-gbp/ublox_dgnss-release.git
• distro file: jazzy/distribution.yaml
• bloom version: 0.12.0
• previous version for package: 0.5.4-1

ntrip_client_node

* added log_level param and CURLOPT_MAXAGE_CONN
* Contributors: Nick Hortovanyi

ublox_dgnss

* Merge pull request #33 <https://github.com/aussierobots/ublox_dgnss/issues/33> from bvsam/base-rtcm-support
  Base rtcm support
* Fixed ublox_fb+r_rover.launch.py and ublox_fb+r_base.launch.py
* updated ublox_fb+r_rover.launch.py and ublox_fb+r_base.launch.py
* updated ublox_fb+r_rover.launch.py and ublox_fb+r_base.launch.py
* updated ublox_fb+r_rover.launch.py and ublox_fb+r_base.launch.py
* Changed ublox_fb+r_base.launch.py
* Changed ublox_fb+r_rover.launch.py
* Merge branch 'main' into base-rtcm-support
* Merge pull request #32 <https://github.com/aussierobots/ublox_dgnss/issues/32> from bvsam/mb+r_fix
  Updating mb+r_base launch file and adding missing parameters
* Updating launch file description comments
* Updating mb+r_base launch file and adding missing parameters
* Adding 2 launch files for fixed base use case
* Improving ublox_rover_hpposllh_navsatfix launch file
* Cleaning up and improving launch files
* added ubx_rxm_cor usb output
* ubx_sec_sig msg ver 2 changes
* added log-level for debug
* added log_level param and CURLOPT_MAXAGE_CONN
* Contributors: Benjamin Sam, Nick Hortovanyi, Xiran Zhou, ryan

ublox_dgnss_node

* Merge pull request #33 <https://github.com/aussierobots/ublox_dgnss/issues/33> from bvsam/base-rtcm-support
  Base rtcm support
* fixed style
* Merge branch 'main' into base-rtcm-support
* Merge pull request #32 <https://github.com/aussierobots/ublox_dgnss/issues/32> from bvsam/mb+r_fix
  Updating mb+r_base launch file and adding missing parameters
* Fixing formatting to allow for tests to pass
* Fixing formatting to enable tests to pass
* Fixing errors in code to ensure successful builds
* Adding more CONFIG_TMODE parameters
* Updating mb+r_base launch file and adding missing parameters
* Adding initial code for fixed base use case
* uncrustify formatting fixes
* Merge branch 'main' of github.com:aussierobots/ublox_dgnss
* uncrustify formatting changes
* Merge pull request #30 <https://github.com/aussierobots/ublox_dgnss/issues/30> from bvsam/base-station-rtcm
  Add base station rtcm message publishing support
* Updating rtcm publisher QOS for subscription compatibility
* Minor: fixing error in code
* Changing rtcm publisher topic name
* Adding payload logging for rtcm publishing
* Making subscription topics absolute for backwards compatbility
* Updating subscription topic names to be non-absolute
* Fixing errors in code
* Adding basic rtcm receival and publishing functionality
* Added Subcription Options Qos Override on subscriptions
* Add Publisher Option with QOS Overriding for all publishers
* uncrustify formatting changes
* parameter pub for ubx_mon_ver ubx_sec_uniqid
* ubx_sec_sig msg ver 2 changes
* added CFG_SIGNAL for GPS, SBAS, GAL, BDS, QZSS and GLO
* updated cfg items
* Contributors: Benjamin Sam, Nick Hortovanyi, Xiran Zhou, ryan

ublox_nav_sat_fix_hp_node

• No changes

ublox_ubx_interfaces

• No changes

ublox_ubx_msgs

* Merge pull request #33 <https://github.com/aussierobots/ublox_dgnss/issues/33> from bvsam/base-rtcm-support
  Base rtcm support
* Adding initial code for fixed base use case
* Update UBXSecSig with 1.5 firmware cent freq jamming state
* Contributors: Benjamin Sam, Nick Hortovanyi

[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