Release v0.10.0

[0.10.0] - 2026-06-23

Added

• RecorderFlushConfig: black-box flush-as-sampling policy fields (ROB-408 / WS-3):
  flush_on_failure (default true), baseline_per_op (default 1),
  sample_rate (default 0.0), flush_on_demand (default true), and the
  always-enforced max_per_hour quota (default 60). The recorder no longer
  flushes only on aborted actions: any failed trace fires a flush, one recent
  successful recording is kept per operation, and a rolling-hour cap guards disk
  and upload bandwidth.

Changed

• SubscriptionsConfig.default_strategy: documented that it only tunes the
  structured always-on sink and is NOT authoritative for sink selection. The
  subscription gating policy wins; heavy sensor types (Image / PointCloud2) are
  gated to record_only (ring buffer only) regardless of default_strategy: adaptive (ROB-408 / WS-3).

Release v0.9.9

[0.9.9] - 2026-06-21

Changed

• Backend default endpoint → https://backend.robotops.com (was https://api.robotops.com). backend.robotops.com is the canonical production endpoint (infra prod DNS + go-backend prod k8s ingress); api.robotops.com was stale. Agents that don't override ROBOT_OPS_AGENT_BACKEND_URL now resolve to the correct host. Schema-only change; version bumped to gate the release. Part of the cross-repo backend-URL reconciliation (RobotOpsInc/web_app#204).

Pre-Release v0.9.9-development-68cfc5d

[0.9.9] - 2026-06-21

Changed

• Backend default endpoint → https://backend.robotops.com (was https://api.robotops.com). backend.robotops.com is the canonical production endpoint (infra prod DNS + go-backend prod k8s ingress); api.robotops.com was stale. Agents that don't override ROBOT_OPS_AGENT_BACKEND_URL now resolve to the correct host. Schema-only change; version bumped to gate the release. Part of the cross-repo backend-URL reconciliation (RobotOpsInc/web_app#204).

Release v0.9.8

[0.9.8] - 2026-06-16

Changed

• ROS 2 Humble / Ubuntu 22.04 Jammy / amd64 Debian package (ROB-402): added an amd64 row to the Humble/jammy build-packages matrix in release.yml, mirroring the existing humble/arm64 row, so ros-humble-robotops-config is now published for amd64 in addition to arm64. No schema changes; version bumped to gate the release.

Release v0.9.7

[0.9.7] - 2026-06-13

Changed

• ROS 2 Humble / Ubuntu 22.04 Jammy / arm64 Debian package (ROB-325): the Dockerfile and the ci.yml / release.yml / release-dev.yml workflows are now parameterized by ROS distro instead of hardcoding Jazzy. The Dockerfile takes --build-arg ROS_DISTRO (FROM ros:${ROS_DISTRO}); the build matrices gained a {ros_distro, os_version, arch} dimension so a single build path produces both ros-jazzy-robotops-config_*_{amd64,arm64}.deb (Noble) and ros-humble-robotops-config_*_arm64.deb (Jammy) via bloom-generate --os-version ${OS_VERSION} --ros-distro ${ROS_DISTRO}. The ci.yml artifact checks (librobotops-config.so, CMake prefix, headers, protobuf ldd) now resolve under /opt/ros/${ROS_DISTRO}. The Humble deb links against Jammy's libprotobuf23 (3.12.4) and publishes to the apt.robotops.com jammy channel (Jazzy → noble). robot_agent's Jetson (Orin Nano) Humble build links against this package.

Release v0.9.6

[0.9.6] - 2026-06-11

Added

• Add subscription gating policy and QoS defaults to SubscriptionsConfig for topic visibility and least-intrusive compatible subscriptions.

Release v0.9.4

[0.9.4] - 2026-05-20

Added

• Add TopicIngestConfig to the shared schema for selective topic promotion and ingest safety limits.
  • topic_ingest.enabled
  • topic_ingest.use_builtin_allowlist
  • topic_ingest.include
  • topic_ingest.exclude
  • topic_ingest.max_message_size_bytes

Release v0.9.2

[0.9.2] - 2026-03-22

Fixed

• Add apt-get update before package installation in release workflow to fix arm64 CI failures caused by stale package cache

Release v0.9.1

[0.9.1] - 2026-03-22

Changed

• Reduce default StorageConfig rotation thresholds for near-real-time MCAP delivery (ROB-100)
  • storage.max_file_size_mb: 100 MB → 10 MB
  • storage.max_file_age_secs: 3600 s → 30 s
  • Reduces worst-case data latency from ~1 hour to ~30 seconds for low-traffic robots
  • Operators can override via ROBOT_OPS_AGENT_STORAGE_MAX_FILE_SIZE_MB / ROBOT_OPS_AGENT_STORAGE_MAX_FILE_AGE_SECS env vars

Release v0.9.0

[0.9.0] - 2026-02-10

Added

• Add RecorderConfig section for Black Box Recorder configuration (ROB-98)
  • recorder.enabled: Master enable/disable switch (default: true)
  • recorder.ring_buffer: Ring buffer memory and lookback settings
    • max_memory_mb: Global memory limit for all topic ring buffers (default: 500 MB)
    • default_lookback_seconds: Default lookback duration when exporting (default: 30 seconds)
  • recorder.topics: Topic selection for recording
    • include: Topics to record as regex patterns (default: [".*"])
    • exclude: Topics to exclude (default: ["/rosout", "/parameter_events", "/robotops/.*"])
  • recorder.tf: TF handling for recordings
    • enabled: Enable TF recording (default: true)
    • max_hz: Rate limit for /tf topic (default: 30.0 Hz)
  • recorder.flush: Flush (export) settings
    • post_event_buffer_seconds: Time to continue capturing after triggering event (default: 5 seconds)
    • output_dir: Output directory for recorder MCAP files (default: "/var/tmp/robotops/recordings")
    • compression: Compression algorithm (default: "lz4", options: lz4, zstd, none)
    • max_recordings: Maximum number of recordings to keep on disk (default: 100)
    • max_disk_mb: Maximum total disk space for recordings (default: 5000 MB)
  • recorder.action_overrides: Per-action overrides (first matching pattern wins)