Changelog for package nebula_continental

1.2.0 (2026-07-30)

• feat(nebula_core_ros): make SyncToolingWorker compatible with agnocast_wrapper::Node (#469)

  • feat(nebula_core_ros): make shared diagnostics/sync helpers agnocast_wrapper::Node-compatible
  • feat(continental_ars548_ros_wrapper): migrate ContinentalARS548RosWrapper to agnocast_wrapper::Node (Method 2)

  * fix(continental_ars548_ros_wrapper): publish pass-through messages via publish(const &) The ALLOCATE_OUTPUT + out = std::move(msg) pattern stole msg's buffer, which was allocated on the normal heap (outside the borrow window), so the payload never entered shared memory and agnocast zero-copy delivered an invalid pointer to cross-process subscribers. publish(const &) borrows inside the window and copies into shared memory, which is correct on both the rclcpp and agnocast backends.

  • fix(nebula_core_ros): include renamed nebula_agnocast_wrapper.hpp in sync_tooling_worker
  • feat(nebula_hesai): migrate HesaiRosWrapper to agnocast_wrapper::Node (Method 2)
  • ci(pre-commit): autofix
  • fix(nebula_hesai): renamed wrapper include, const-ref packets publish, restore cie thread factory

  - include the post-#472 nebula_agnocast_wrapper.hpp (old autoware_agnocast_wrapper.hpp no longer exists)

  - publish raw packets via publish(*msg) so the payload is materialized into shared memory (a plain std::move would leave it on the normal heap, invalid for cross-process subscribers)

  - restore make_cie_thread_factory for the packets publish thread; the migration had dropped it, which would leave that non-ROS thread unmanaged by the Agnocast CIE thread configurator and lose its configured priority/affinity

  * fix(continental_ars548_ros_wrapper): log the resolved packets topic again The migration replaced [packets_sub_->get_topic_name()]{.title-ref} with the relative topic literal, which hides the actual (namespaced/remapped) topic and makes troubleshooting harder. The wrapper's Subscription has no get_topic_name(), so resolve the name through the node's topics interface instead; this yields the same fully-qualified name as before on both backends.

  * fix(nebula_hesai): log the resolved packets topic again The migration replaced [packets_sub_->get_topic_name()]{.title-ref} with the relative topic literal, which hides the actual (namespaced/remapped) topic and makes troubleshooting harder. The wrapper's Subscription has no get_topic_name(), so resolve the name through the node's topics interface instead; this yields the same fully-qualified name as before on both backends. ---------Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: Max Schmeller <<6088931+mojomex@users.noreply.github.com>>

• chore: sync files (#74)

  • chore: sync files

  * style(pre-commit): autofix ---------Co-authored-by: github-actions <<github-actions@github.com>> Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>

• Contributors: Koichi Imai, tier4-nebula-app[bot]

1.1.1 (2026-06-03)

1.0.0 (2026-04-06)

0.4.0 (2026-03-27)

• feat(nebula_continental, nebula_hesai): apply agnocast_components for CIE (#418)

  • feat(nebula_continental): apply autoware_agnocast_wrapper for CIE
  • ci(pre-commit): autofix
  • refactor(nebula_continental): replace autoware_agnocast_wrapper with agnocast_components

  * fix(nebula_continental): make agnocast_components dependency conditional on ENABLE_AGNOCAST Align with the Hesai package pattern by guarding the agnocast_components dependency behind the ENABLE_AGNOCAST environment variable, falling back to rclcpp_components_register_node when disabled. This fixes CI failures where rosdep cannot find ros-humble-agnocast-components.

  * fix(nebula_continental): register SRR520 with agnocast_components when ENABLE_AGNOCAST agnocast_components_register_node and

File truncated at 100 lines see the full file