Skip to content

v0.9.0

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 29 Oct 14:05
v0.9.0
2c3a919
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Module Release Notes

Module Name: lifecycle
Release Tag: v0.9.0
Origin Release Tag: v0.8.0
Release Commit Hash: 2c3a919
Release Date: 2026-10-29

Overview

This document provides an overview of the changes, improvements, and bug fixes included in the software module release version v0.9.0
as compared to the module's origin release (which is usually the previous release).

Disclaimer

This release is not intended for production use, as it does not include a safety argumentation or a completed safety assessment.
The work products compiled in the safety package are created with care according to the S-CORE process. However, as a non-profit, open-source organization, the project cannot assume any liability for its content.

For details on the features, see https://eclipse-score.github.io/score/main/features/lifecycle/index.html

Changes to the Module

New Features

  • None

Improvements

  • Configuration option deployment_config.ready_recovery_action is now deprecated to avoid confusion btw. ready_recovery_action and recovery_action.
    Instead use the new configuration parameters deployment_config.activation_retry_attempts and deployment_config.activation_retry_delay_ms. Note that
    deployment_config.activation_retry_delay_ms is not yet implemented and only a placeholder.
  • Improved stability of the feature integration tests
    (#850).
  • Extended the ILmControl API with the new method wait_for_connection(), which blocks until the client is connected
    to the Launch Manager, the timeout expires, or a stop is requested via a stop token
    (#840, #850).
  • Improved the feature architecture documentation with Control API behavior and Recovery Actions
    (#800).

Bug Fixes

  • Fixed a race in ILmControl: an activation callback registered before the service was discovered tried to read
    samples immediately. It now waits until the connection is established
    (#849).
  • Fixed a narrowing bug in the health monitor's TimeRange: MinMs() / MaxMs() returned uint32_t and could
    silently narrow values. They now return uint64_t, and negative durations violate a precondition check. Both the C++
    library and the Rust FFI were updated (#827).

Other Changes by Label

  • None

Compatibility

  • The following platforms are supported using the bazel_cpp_toolchains:

    • x86_64-unknown-linux-gnu
    • aarch64-unknown-linux-gnu
    • x86_64-unknown-nto-qnx800
    • aarch64-unknown-nto-qnx800

Performed Verification

  • Build on all supported platforms
  • Unit test execution on all supported platforms

Known Issues

  • None

Known Vulnerabilities

  • None

Upgrade Instructions

  • Configuration option ready_recovery_action is deprecated and will be removed with the next release. Replace configuration option deployment_config.ready_recovery_action.restart.number_of_attempts with deployment_config.activation_retry_attempts and deployment_config.ready_recovery_action.restart.delay_before_restart_ms with deployment_config.activation_retry_delay_ms.
Assets 4
Loading