Skip to content

Update dependency score_communication to v0.3.0#39

Open
eclipse-score-bot wants to merge 1 commit into
mainfrom
renovate/score_communication-0.x
Open

Update dependency score_communication to v0.3.0#39
eclipse-score-bot wants to merge 1 commit into
mainfrom
renovate/score_communication-0.x

Conversation

@eclipse-score-bot

@eclipse-score-bot eclipse-score-bot commented Jun 29, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
score_communication bazel_dep minor 0.1.1 → 0.3.0

Release Notes

eclipse-score/communication (score_communication)

v0.3.0

Module Name: communication
Release Tag: v0.3.0
Origin Release Tag: v0.2.1
Release Commit Hash: 6b1a78b
Release Date: 2026-07-13

Overview

The communication module provides a generic communication frontend with an IPC binding for use in the S-CORE project.

The module is available as a Bazel module in the S-CORE Bazel registry: https://github.com/eclipse-score/bazel_registry/tree/main/modules/score_communication

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/communication/index.html

Improvements

Core Communication Features

  • Added the LoLa inter-domain gateway with application orchestration, configuration parsing, and sample hypervisor transport layer for forwarding services across domains (#​450, #​510, #​536, #​576, #​578).
  • Introduced field tags architecture replacing boolean enablers to enable independent Get/Set/Notify functionality on fields (#​357).
  • Extended methods with semi-dynamic support, non-movable references, and improved resource management (#​632, #​572, #​593, #​390).
  • Added skeleton event move semantics and event subscription change notifications (#​610, #​358, #​409).

Message Passing & Architecture

  • Expanded message-passing dependability with architecture diagrams, safety analysis (FTA, FMEA), and component/feature requirements documentation (#​372, #​530, #​601, #​555).
  • Improved cross-domain service support and service discovery enhancements (#​618, #​639, #​633).

C++ Modernization & Codebase Quality

  • Replaced all score::cpp::optional with standard std::optional across 125 files, aligning with modern C++17 standards (#​598).
  • Cleaned up deprecated Rust FFI and old API patterns, reducing integration complexity (#​602).
  • Refactored method enablement semantics and removed legacy SomeIP configuration structs (#​673, #​406).

Testing & Quality Infrastructure

  • Massive expansion of test coverage: skeleton/proxy event move semantics tests, generic proxy/skeleton integration tests, method/subscription state-machine tests (#​559, #​653, #​408, #​571, #​605, #​466).
  • Added compiler warning feature bundles (15+ warning categories) integrated into all targets for systematic code hygiene (#​527).
  • Introduced visibility guards and static analysis for public API surface (#​641, #​550).
  • Expanded QNX8 and address/UB/leak/thread sanitizer test coverage across all toolchains (#​436, #​401, #​657, #​415, #​585).

CI/CD & Release Automation

  • Completely refactored GitHub Actions infrastructure with reusable workflow composables, Bazel caching layer, and dynamic environment setup (#​621).
  • Added nightly quality dashboards with automated code coverage, clang-tidy, and CodeQL reporting (#​448, #​215).
  • Implemented automatic release artifact uploads for documentation and coverage reports (#​691, #​693).

Documentation & Process

  • Restructured Sphinx build pipeline with versioned publishing, CSS theme modernization, and PlantUML diagram support (#​672, #​458, #​464, #​378).
  • Extended safety analysis documentation with failure modes, FTA chains, and architectural diagrams (#​601, #​372, #​410, #​599).
  • Added requirements files (CONTRIBUTING, quality README) and architecture documentation (#​303)

Bug Fixes

Configuration & Service Binding

  • Fixed runtime configuration parsing, service instance ID range handling, and method/field enablement defaults (#​696, #​683, #​668, #​673).
  • Fixed service element binding validation with comprehensive coverage of proxy/skeleton configurations (#​618, #​639).
  • Removed deprecated SomeIP deployment-specific code that was causing configuration mismatches (#​406).

Shared Memory & Lifecycle Management

  • Fixed skeleton shared-memory reopen/recreate flows with proper resource lifecycle and state preservation (#​665, #​642).
  • Fixed subscription state-machine race conditions and stability issues under concurrent access (#​605, #​466, #​466).
  • Fixed event registration and notification handling, including signal propagation reliability (#​414, #​576).
  • Fixed skeleton event move semantics to prevent data corruption during transfers (#​610, #​408).
  • Fixed proxy/skeleton resource cleanup on destruction and partial offer scenarios (#​642, #​596).

Message Passing & IPC

  • Fixed unix-domain socket NOSIGNAL handling and poll-based event notification (#​585).

Quality & Build Infrastructure

  • Fixed coverage generation and LLVM cov integration across all toolchains (#​675, #​549).
  • Fixed lockfile enforcement in CI to prevent dependency drift (#​690).
  • Fixed clang-tidy infrastructure and report publishing pipeline (#​621, #​488).
  • Fixed snapshot mirror reliability for reproducible builds (#​635).
  • Fixed CodeQL database extraction and MISRA report generation (#​550).
  • Fixed unused parameters, variable shadowing, and sign conversion warnings systematically (#​627, #​608, #​562).
  • Fixed template member function documentation in Doxygen (#​477).

Compatibility

Performed Verification

  • Unit test execution on host with all supported toolchains
  • Build on supported target platforms (QNX8 x86_64 and QNX8 aarch64)
  • Thread sanitized unit test execution
  • Address and UB sanitized unit test execution
  • Leak sanitized unit test execution

Known Issues

Upgrade Instructions

Backward compatibility with the previous release is not guaranteed.

Contact Information

For any questions or support, please raise an issue/discussion.

v0.2.1

Module Name: communication
Release Tag:
Origin Release Tag:
Release Commit Hash:
Release Date:

Overview

The communication module provides a generic communication frontend with an IPC binding for use in the S-CORE project.

The module is available as a Bazel module in the S-CORE Bazel registry: https://github.com/eclipse-score/bazel_registry/tree/main/modules/score_communication

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/communication/index.html

Improvements

  • Make message passing public visible

Bug Fixes

N/A

Compatibility

Performed Verification

  • Unit test execution on host with all supported toolchains
  • Build on supported target platforms (QNX8 x86_64 and QNX8 aarch64)
  • Thread sanitized unit test execution
  • Address and UB sanitized unit test execution
  • Leak sanitized unit test execution

Known Issues

Upgrade Instructions

Backward compatibility with the previous release is not guaranteed.

Contact Information

For any questions or support, please raise an issue/discussion.

v0.2.0

Module Name: communication
Release Tag:
Origin Release Tag:
Release Commit Hash:
Release Date:

Overview

The communication module provides a generic communication frontend with an IPC binding for use in the S-CORE project.

The module is available as a Bazel module in the S-CORE Bazel registry: https://github.com/eclipse-score/bazel_registry/tree/main/modules/score_communication

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/communication/index.html

Improvements

  • lola Methods: Added UniqueMethodIdentifier, MethodType enum, basic acceptance tests, and signature variation tests; migrated Skeleton/Proxy to use UniqueMethodIdentifier; initialized InArgs and return values on creation
  • Fields (Get/Set): Added Get/Set API to ProxyField and SkeletonField, FieldOnlyConstructorEnabler to SkeletonField/SkeletonMethod/ProxyMethod variants, and SetHandler support for SkeletonField (skeleton-side implementation is WIP)
  • Generic Skeleton: Introduced a PoC implementation of Generic Skeleton for Events with initial partial restart handling, a refined interface, alignment/over-aligned-type guards, and a new README
  • lola Refactoring: Extracted TransactionLogIndex, skeleton shared memory functionality, and shared_data_structures into separate targets; removed EventDataControlCompositeImpl, EventSubscriptionControlImpl, and HasAsilBSupport; use ScopeExit for method registration guards
  • message_passing: Use pulses for zero-notify messages
  • mw/com: Migrated score::cpp::optional to std::optional, use MeyerSingleton for static Runtime initialization, ResultBlank consistently; renamed process_identifier → application_id; removed dependency on score_logging
  • New Rust COM API Library: Introduced a fully reworked Rust COM API (//score/mw/com/impl/rust/com-api) with:
  • Backend-independent architecture: A standalone backend crate enabling seamless switching of runtime backends without changes to user applications
  • Registry-based FFI layer: A flexible foreign-function interface for C++/Rust interop
  • MW::COM-enabled runtime (lola-runtime): Backend support for the COM module
  • Async FindService and async Receive APIs, unsubscribe support, Interface declarative macro, CommData/Reloc derive macros, error enum optimizations via thiserror, Rust doc tests, and full API documentation
  • C++/Rust memory validation integration tests, architecture/sequence diagrams
  • Toolchain: Added score_gcc_aarch64_toolchain, missing compiler warning options, and always-on colored build output
  • CI/CD: Added GCC toolchain integration example, enforced formatting, made Coverage Report a required merge-queue check, restricted workflow permissions, optimized Bazel cache to merge-queue only
  • Documentation: Merged SETUP.md into CONTRIBUTING.md, moved Sphinx docs to docs/sphinx/, added Docker prerequisite and formatter instructions to README, updated QNX instructions

Bug Fixes

  • mw/com: Fixed race condition in TimeoutSupervisor, fixed correct construction of shared memory path, fixed method resource cleanup, fixed failing SkeletonField tests, fixed move semantics in mw/com/impl
  • lola: Fixed callback registration in SkeletonEvent, fixed misnamed variable, asserted valid base address instead of casting, changed unreachable branch to a precondition
  • SampleAllocateePtr: Fixed null dereference crash and missing mock deleters in tests
  • Generic Skeleton: Fixed shared memory storage application, alignment issues, and layering violations
  • Rust COM-API: Fixed Clippy/rustfmt warnings, added error handling for set/unset receive handler
  • InstanceSpecifier: Fixed deprecated InstanceSpecifier::Create usage
  • mw/com: Fixed race condition, restored mp2 log level mapping
  • CI: Fixed typos in QNX workflow names/job names, fixed ASan ODR violation, fixed broken FTA includes in safety analysis

⚠️ Known Limitations / Work in Progress

  • Rust COM API migration: The old Rust APIs for communication are deprecated. Consumers are requested to adopt the new Rust COM API library. See //score/mw/com/impl/rust/com-api for details.
  • Method handler signature is not final: The current handler signature for a method ReturnType(InArgType1, InArgType2, ...) is ReturnType(InArgType1&, InArgType2&, ...). The final signature will be void(ReturnType&, const InArgType1&, const InArgType2&, ...) to avoid an unnecessary copy.
  • Proxy method selection via config not yet implemented: Currently, the consumer/proxy side must pass the list of method names it intends to use as a string list in Proxy::Create(). In the final implementation this will be read from mw_com_config.json.
  • Methods are not fully tested: General functionality works, but edge cases have not been covered yet.
  • Field Get/Set skeleton-side implementation is WIP: ProxyField and SkeletonField APIs (signatures) are final, but the skeleton-side implementation is incomplete. Configuration of Get/Set availability via mw_com_config.json is also not yet implemented.

Compatibility

Performed Verification

  • Unit test execution on host with all supported toolchains
  • Build on supported target platforms (QNX8 x86_64 and QNX8 aarch64)
  • Thread sanitized unit test execution
  • Address and UB sanitized unit test execution
  • Leak sanitized unit test execution

Known Issues

Upgrade Instructions

Backward compatibility with the previous release is not guaranteed.

Contact Information

For any questions or support, please raise an issue/discussion.

v0.1.4

Module Name: communication
Release Tag: v0.1.4
Origin Release Tag: v0.1.2
Release Commit Hash: 484f046
Release Date: 2026-03-09
Overview

The communication module provides a generic communication frontend with an IPC binding for use in the S-CORE project.

The module is available as a Bazel module in the S-CORE Bazel registry: https://github.com/eclipse-score/bazel_registry/tree/main/modules/score_communication

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/communication/index.html

Improvements

  • (Partial) migration to new S-CORE toolchain
  • Rust API macros were optimized and error reporting improved
  • Rust support for QNX builds
  • Support for clang-tidy linting
  • Support for CodeQL analysis
  • Preliminary support for methods
  • Removal of message passing 1.0 (please use message passing 2.0)
  • Improved logging in message passing 2.0 via callback injection
  • Enabled integration tests in CI
  • Integrated mw::service frontend with stubbed backend (introduction to unblock ConfigDaemon - please do not yet use for other use cases)
  • API documentation based on Doxygen and Sphinx with documentation available at https://score-communication.readthedocs.io/en/latest/
  • Alow injection of a tracing library
  • Improved CI setup and test infrastructure to decrease flakiness

Bug Fixes

Compatibility

Performed Verification

  • Unit test execution on host with all supported toolchains
  • Build on supported target platforms (QNX8 x86_64 and QNX8 aarch64)
  • Thread sanitized unit test execution
  • Address and UB sanitized unit/integration test execution
  • Leak sanitized unit/integration test execution

Known Issues

  • Thread sanitized integration tests experience flakiness that is likely introduced by the framework.

Upgrade Instructions

Backward compatibility with the previous release is not guaranteed.

Contact Information

For any questions or support, please raise an issue/discussion.

v0.1.3

  • Enabled various code quality tools
  • Extension of the Rust API (expect further extensive work on this API)
  • Support explicit setting of application id in configuration (with fallback to PID)

Full Changelog: eclipse-score/communication@v0.1.2...v0.1.3

[!CAUTION]
This release was not agreed on with the maintainers of the communication module. It was created by a committer from the S-CORE project without following our release workflow. This workflow would have prevented this release.
Please avoid using this release. We do not provide any safety guarantees. We take this case very seriously and work on both organisational and technical measures to prevent this in the future.

v0.1.2

Module Name: communication
Release Tag: v0.1.2
Origin Release Tag: v0.1.1
Release Commit Hash: d5414f7
Release Date: 2025-12-19

Overview

The communication module provides a generic communication frontend with an IPC binding for use in the S-CORE project.

This release is meant for integration with the S-CORE 0.5 Beta Release.
The module is available as a Bazel module in the S-CORE Bazel registry: https://github.com/eclipse-score/bazel_registry/tree/main/modules/score_communication

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/communication/index.html

Improvements

  • Enabled various code quality tools.
  • Extension of the Rust API (expect further extensive work on this API)
  • Support explicit setting of application id in configuration (with fallback to PID)

Full Changelog: eclipse-score/communication@v0.1.1...v0.1.2

Bug Fixes

Compatibility

Performed Verification

  • Unit test execution on host with all supported toolchains
  • Build on supported target platforms (QNX8 x86_64 and QNX8 aarch64)
  • Thread sanitized unit test execution
  • Address and UB sanitized unit test execution
  • Leak sanitized unit test execution

Known Issues

General Issues
  • Safety package is incomplete due to missing documentation and verification.
  • Coverage infrastructure is in beta stage. Results are therefore without any guarantee of correctness.
  • TRLC reports are in beta stage. Results are therefore without any guarantee of correctness.
LLVM Toolchain
  • The toolchain uses a non-hermetic sysroot. Hence, compilation may fail on hosts with an incompatible libstdc++ (
QNX 8 Toolchain (x86_64 and AArch64)
  • Unit tests are not currently executed on QNX 8 SDP.

Upgrade Instructions

Backward compatibility with the previous release is not guaranteed.

Contact Information

For any questions or support, please raise an issue/discussion.

  • If you want to rebase/retry this PR, check this box

This PR was generated by #infrastructure automation. Contact us if you have any questions or feedback.

@github-actions

github-actions Bot commented Jun 29, 2026 •
edited
Loading

Copy link
Copy Markdown

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run //:license-check

Status: ⚠️ Needs Review

Click to expand output 
[License Check Output]
2026/07/14 07:40:01 Downloading https://releases.bazel.build/8.3.0/release/bazel-8.3.0-linux-x86_64...
Extracting Bazel installation...
Starting local Bazel server (8.3.0) and connecting to it...
INFO: Invocation ID: e6d61aea-7cd8-4fde-bf93-d91680e35d89
Computing main repo mapping: 
Computing main repo mapping: 
DEBUG: Rule 'rules_boost+' indicated that a canonical reproducible form can be obtained by modifying arguments integrity = "sha256-LTilyiMMjpYyAi1PW+8RycyAEHy9clo7915R0Bchb2E="
DEBUG: Repository rules_boost+ instantiated at:
  <builtin>: in <toplevel>
Repository rule http_archive defined at:
  /home/runner/.bazel/external/bazel_tools/tools/build_defs/repo/http.bzl:394:31: in <toplevel>
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
ERROR: Error computing the main repository mapping: score_communication@0.3.0 depends on boost.program_options@1.83.0.bcr.4 with compatibility level 0, but <root> depends on boost.program_options@1.87.0 with compatibility level 108700 which is different

@eclipse-score-bot eclipse-score-bot changed the title Update dependency score_communication to v0.2.1 Update dependency score_communication to v0.3.0 Jul 14, 2026
@eclipse-score-bot
eclipse-score-bot force-pushed the renovate/score_communication-0.x branch from 243244e to f30f193 Compare July 14, 2026 07:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

automation renovate

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@eclipse-score-bot