S-CORE Daily

[dcalavrezo-qorix]

This thread collects S-CORE Daily — daily digest of Eclipse S-CORE activity.

Each issue is posted as a comment below, so subscribe to this discussion to get every new issue as a notification. Generated automatically from public eclipse-score activity; every item links to its source. Corrections and feedback welcome as replies.

[dcalavrezo-qorix]

S-CORE Daily — 2026-08-26

Headline: A busy Wednesday for S-CORE: three releases shipped (including a breaking change in baselibs), 32 pull requests merged across 17 repositories, five community meetings posted their minutes, and 127 long-standing tracking issues in the kyron and score repos were closed.

In plain terms

Three modules cut new releases today — baselibs, bazel_cpp_toolchains, and the brand-new score_cpp_policies — with baselibs v0.2.12 carrying a breaking API change that consumers of StaticDestructionGuard need to check. Code activity was broad but incremental: clang-tidy cleanups, QNX build fixes, docs-as-code improvements, and continued work on code coverage tooling (llvm-cov) across several repositories. Community meetings covered testing report automation, Rust coding guidelines, and a quality-manager role assignment that was merged, reverted, and re-proposed pending a formal vote — worth watching if you're involved in governance. The large batch of closed issues in kyron and score appears to be historical process-template cleanup rather than new work. Nothing else in the window looks urgent for downstream users.

Releases

• baselibs — v0.2.12: basic C++ utility library update. Breaking change: StaticDestructionGuard<T>::GetStorage() now returns T& instead of a raw storage type — code that reinterpret-casts its return value needs updating.
• bazel_cpp_toolchains — v1.0.2: fixes QNX build ordering of user_link_flags relative to linked libraries, resolving undefined-reference errors.
• score_cpp_policies — v0.1.0: first release of this new repository, introducing centralized clang-tidy infrastructure and per-sanitizer Bazel features/flags.

From the meetings

Testing Community (minutes)

• Decisions: Tests should live in a separate directory, but the exact location doesn't matter since test frameworks can discover different paths.
• Open questions: Whether a single module verification report target can serve differently-configured test targets without maintenance overhead relative to the process_description template.

Infrastructure Community — Rust (minutes)

• Action items: @PLeVasseur to introduce the coding guideline in the Safety-Critical Rust Consortium's meeting the same day.

Security & Crypto FT (minutes)

• The meeting was cancelled due to holidays; discussion resumes 2026-09-09. Urgent topics should go to the security Slack channel.

Base Libs FT (minutes)

• Decisions: A new baselibs release for S-CORE 0.9 would go out the same day. For the vajson serializer open-sourcing, the code will initially live alongside the existing writer implementation with a Bazel config choice between pretty-printed and compact output, pending a performance-based decision on which to keep long-term.
• Open questions: More proposals welcome on baselibs#516 (renaming the ABI-compatible data types component).

General SW Dev Process Community (minutes)

• Decisions: @pahmann's PR adding him as Quality Manager (alongside @masc2023 and @PandaeDo) was merged. The community agreed llvm-cov based code coverage on Linux and QNX is viable, pending the Technical Lead Circle's final procedure decision.
• Action items: Process community to leave review comments, if any, on the large contribution/intro restructuring PR (score#3224).
• Open questions: How to properly configure llvm-cov on QNX given compiler-setting differences between coverage and non-coverage test runs, and who has the toolchain expertise to set it up.

Discussions worth following

• S-CORE & QNX (Infrastructure Community) — new comment from the 2026-08-26 QNX sync: good progress on an exception letter for QDL, feedback received, with a letter or timeline update expected. Link.

Code changes

baselibs

• [Change] Link unit tests to component requirements for bit-manipulation and bitmask operators, improving traceability (#499).

bazel_cpp_toolchains

• [Bug fix] Reorder user_link_flags after libraries to link, fixing QNX undefined-reference errors (#128).

communication

• [Bug fix] Resolved clang-tidy findings for stringview usage, uninitialized variables, and missing special member functions across the codebase, improving code safety and consistency (#1012, #1014, #1015).
• [Documentation] Fixed a broken link and a typo in the README (#1009).

docs-as-code

• [New feature] Testcase links in docs are now annotated with pass/fail/skip/disabled status (#739).
• [Bug fix] Improved data handling and bundle documentation, and fixed duplicate "needs" appearing from nested docs bundles (#751, #758).
• [Maintenance] Prepared needs templates for upcoming work (#762).
• 2 automated dependency updates merged (devcontainer, Python packages).

inc_security_crypto

• [Change] Restored QNX Rust toolchains in .bazelrc, unblocking QNX cross-compilation CI (#191).

inc_someip_gateway

• [Maintenance] Made Google Test a dev-only dependency so consuming modules can use the gateway's public mocks without pulling it in (#272).

lifecycle

• [Change] Introduced unified LLVM-based code coverage, replacing separate C++/Rust coverage pipelines (#526).
• [Maintenance] Standardized devcontainer integration and a small README fix (#516, #531).
• 2 automated dependency updates merged.

persistency

• [CI / automation] Improved release workflow reliability by skipping verification when release prep fails and fixing a git tagging error (#335).
• 2 automated dependency updates merged.

process_description

• [Change] Updated an implementation-process requirement, consolidating dependency-analysis needs to be fulfilled by SBOM generation instead (#783).

qnx_unit_tests

• [Change] Fixed environment-variable forwarding so multiple env vars are passed through correctly, not just the first (#41).

score

• [Change] Expanded infrastructure maintainers in CODEOWNERS (#3216). The quality-manager role-assignment PR for @pahmann was merged, then reverted, then reopened pending election-relevant approvals (#3213, #3218, #3220).

score-crates

• [Bug fix] Added cargo lockfile definitions required by a newer rules_rust version (#69).

score_cpp_policies

• [New feature] Added C++ compiler warning features (#33).

time

• [Change] Adopted the unified LLVM coverage pipeline, improved QNX download stability, and fixed a coverage job naming issue that broke the Bazel cache plugin (#186, #189, #191).
• [Maintenance] Added a cache-maintenance workflow and bumped workflow versions (#162).
• 3 automated dependency updates merged.

.eclipsefdn

• [Change] Archived the toolchains_qnx and toolchains_gcc repositories and added an incubator repository for ecu_model (#212, #219).

Overall: 10 automated dependency-update PRs merged today across inc_someip_gateway, lifecycle, logging, module_template, persistency, and time.

Issues

• lifecycle: [bug] IdentifierHash uses std::hash, unstable across compiler/toolchain builds, crashing the Launch Manager on a ControlClient request (#528).
• 23 issues opened, 127 closed in this window (most closures were long-standing kyron and score process-template tracking issues).

Footer

S-CORE Daily is generated automatically from public eclipse-score activity for the window shown. Links go to the sources; corrections welcome as replies.

[dcalavrezo-qorix]

S-CORE Daily — 2026-08-27

Headline: Lifecycle shipped two releases in one day (v0.4.0, v0.5.0) and a bazel module rename lands across the stack, while dependency-alignment and release-workflow cleanup dominate the merge queue.

In plain terms

The lifecycle module had a busy day: two new releases went out, and a chunk of merged work continues its migration to an mw::com-based control API and fixes to its release workflow. Across the org, a coordinated rename of the score_lifecycle_health bazel module to score_lifecycle touched multiple repos (bazel_registry, lifecycle) — one bazel_registry PR explicitly removes an incorrect 0.4.0 release, so if you consume that package, check you're not pinned to it. The Time and Persistency feature teams and the Technical Lead Circle posted their regular meeting notes, with the Tech Lead Circle flagging an interesting prototype linking Lobster traceability reports into the Sphinx docs pipeline. Nothing here looks urgent, but the lifecycle and bazel_registry renames are worth a glance if your builds depend on those modules.

Releases

• lifecycle v0.4.0 — adds working-directory support for deployment configs, plus other fixes since v0.3.0.
• lifecycle v0.5.0 — follow-up release the same day; changelog lists no new features/fixes/compatibility notes beyond v0.4.0.
• score_cpp_policies v0.1.1 — adds tests/CI for compiler-warnings features and migration documentation (#35, #37).

From the meetings

Persistency FT (minutes)

• New PR: feat: make KVS max snapshot count configurable persistency#383. Updated: persistency#376.
• Merged/closed: persistency#380, pull/386, pull/385, pull/382.
• Note: some changes merged without linking to issues.
• Open question: persistency#375 — @Ahmed-Elsaka-JC will discuss with ark whether he can handle it.
• Action item: persistency/pull/337 — @Ahmed-Elsaka-JC to review and approve if no issues; to be discussed at the next meeting.

Technical Lead Circle (minutes)

• Decision/status: no updates yet on the v0.9 release_candidate_09 branch.
• Discussed a prototype connecting Lobster traceability reports with Sphinx/sphinx-needs docs (bitmanipulation example), spanning playground branches in baselibs, docs-as-code, tooling, and score.

Time FT (minutes)

• v0.9 checklist (time#190): unclear what still needs to be done.
• ASIL-B requirements followup: all comments fixed, waiting on feedback about the meaning of ASIL_B rating in API requirements.
• Reviews: many PRs merged/closed this week. Open PRs from @gordon9901 — time#158 (@BjoernAtBosch to re-review today) and time#122 (needs more discussion). Other open PRs (doxygen docs, component requirements) are ready for review.

Code changes

.eclipsefdn

• [Change] Enable config_management module for qnx licence — (#215)

bazel_registry

• [Breaking change] Remove incorrect lifecycle 0.4.0 release — reverts a bazel-registry entry pending correct republishing (#512)
• Bazel module rename: score_lifecycle_health → score_lifecycle, part of harmonizing module names per the v0.9 release checklist (#511)

communication

• Added integration tests covering move-construction/assignment for mw::com Skeleton methods and Proxy methods, and fixed clang-tidy performance findings (#659, #820, #1003)

docs-as-code

• [Documentation] Improved metamodel reference docs (#748)
• [New feature] Added manual tag to docs targets to avoid build issues, across two follow-up PRs (#765, #766)
• [Tests] Downstream Bazel lockfile problems are now ignored so they don't block CI (#768)

inc_security_crypto

• [Bug fix] Updated stale module lockfile that was breaking workflows (#195)

inc_someip_gateway

• [Maintenance] Moved docs-as-code build rules out of shared BUILD files into per-component docs/BUILD (#273)
• [CI / automation] Bazel now retries dependency downloads to work around flaky CI networking (#274)

lifecycle

• mw::com control API: initial library-side implementation of the ilm_control interface using mw::com, closing lifecycle#480 — daemon-side follow-up still to come (#478)
• Bazel module rename: score_lifecycle_health → score_lifecycle (#530)
• Release housekeeping: aligned SCORE platform dependencies, extended release notes, adjusted/fixed the release workflow, moved sanitizer settings and docs-as-code dependency handling (#517, #534, #539, #543, #544, #547, #548)
• One automated github-actions dependency bump merged (#540)

logging

• Docs-as-code updates and CW_32 export changes merged (#280, #281)

module_template

• Automated github-actions dependency bump merged (#161)

os_autosd

• [Change] Added a docs-publish workflow, copied from module_template (#59)

score_cpp_policies

• Added CI/tests for the new compiler-warnings feature and migration documentation (#35, #37)

time

• [Change] Moved qnx_credential_helper to fix a broken cache maintenance workflow (#192)

tools

• [New feature] Introduced repo_policy_sync, a large new tool for repository policy management, followed by a src-layout refactor and a switch to run policy sync in plan mode (#10, #11, #12)

6 automated dependency bumps merged across devcontainer (1), inc_someip_gateway (2), logging (1), time (2).

Issues

• lifecycle: createTransition() aborts the whole daemon on any unrecognized run target name, instead of returning an error
• lifecycle: Remove scripts/prepare_release_notes.sh cleanup
• tooling: coverage: integration mode — scope external module roots (reference_integration)
• tooling: plantuml parser: 2.x rejects standard PlantUML constructs used in logging's design diagrams (blocks score_tooling 2.x adoption)

9 issues opened, 5 closed.

Footer

Generated automatically from public eclipse-score activity for the window shown in the briefing. Links go to the sources; corrections welcome as replies.

[dcalavrezo-qorix]

S-CORE Daily — 2026-08-30

Headline

A quiet weekend for meetings and discussions but a busy one for code: 24 pull requests merged across 21 repositories, two module releases shipped, and 38 issues closed.

In plain terms

Over the past three days (Friday through Sunday) the S-CORE project kept moving mostly through code contributions rather than meetings or discussions — there were no meeting minutes or new discussion threads in this window. Two releases went out: an updated toolchain platform module and a docs-as-code release with several new features and fixes. A notable bug fix landed in the lifecycle module addressing a hash function that wasn't stable across compilers, which could cause crashes in certain integration scenarios. Several repositories also picked up routine dependency and CI maintenance. Anyone building on lifecycle or docs-as-code should check the release notes for changes that affect their setup.

Releases

• bazel_platforms — v1.1.0: adds support for Ebclfsa 2.0.0-beta2.
• docs-as-code — v8.1.0: new features include annotating test-case links with results, a manual-build flag for docs targets (they no longer build automatically on //...), and a module verification report template; also fixes docs(data=...) usage and nesting docs_bundle() inside docs(). Modules can mix any docs-as-code 8.y.z versions.

Code changes

.eclipsefdn

• [Change] Enforce CI in inc_ecu_model — tightens CI requirements for the new repository (#220); follow-up fix to CI job names (#221).

.github

• [Change] Update profile README — automated refresh of the org profile from the latest metrics snapshot (#95).

bazel_cpp_toolchains

• [Change] Add Ebclfsa 2.0.0-beta2 — updates the toolchain so the SDK's linker (not the host's) is used correctly after extraction (#131).

bazel_platforms

• [New feature] Add Ebclfsa 2.0.0-beta2 support, matching the new release above (#22).

communication

• [Change] mw/com: add test for disabling field set/get in config — improves test coverage for a configuration option (#857).
• [Change] mw/com/dependability: split requirements into per-unit requirements for clearer traceability (#1008).

docs-as-code

• [New feature] Module verification report / complex templates — adds a new report template combining ideas from prior discussions (#763).

inc_ecu_model

• [Change] Initial repo setup — bootstraps the new repository with bazelmod, quality workflows, and placeholder code (#1).

lifecycle

• [Bug fix] Make IdentifierHash stable across compilers/binaries — fixes a hash implementation that previously wasn't guaranteed consistent across compiler/library versions, which could break identifier matching between processes (#527).
• [Change] Fix shutdown race condition in PGM that could fail integration tests (#537).
• [Change] Move to Bazel 8.7.0 (#550).
• [Bug fix] Add missing mod need in documentation (#555).
• [Change] Fix doc build (#556) and run formatter to correct a style error introduced by docs: implement general graph checks scheme #527 (#560).

logging

• [Change] Adopt the unified LLVM source-based coverage pipeline from score_tooling 2.2.0, replacing the older gcov-based coverage tooling, aligning with similar migrations in other modules (#282).

module_template

• [New feature] Integrate QNX IFS toolchain centrally — closes gaps identified in downstream modules needing QNX imagefs support (#160).

persistency

• [Bug fix] Add missing mod need in documentation (#397).

reference_integration

• [Maintenance] Bump devcontainer to 1.11.0, use KVM and docker-in-docker feature, enabling previously-broken local test/run workflows (#312).

time

• [Change] Upgrade to score_lifecycle 0.5.0 — follows the renaming of the score_lifecycle_health module to score_lifecycle, no functional changes beyond the rename (#197).

tooling

• [New feature] Add Graphviz support for Lobster reports, removing the need for a host-installed Graphviz binary and making report generation reproducible (#448).

tools

• [New feature] Discover policy PRs by label instead of branch head, fixing cases where renamed policies caused duplicate or missed pull requests (#13).
• [Maintenance] Convert score_tools into a uv workspace so components like cr_checker and repo_policy_sync can have independent dependencies (#17).
• [New feature] Extract repo_cache as a reusable component, so other tools can reuse the repository-caching logic (#18).

Dependency updates (automated): 10 automated dependency bumps merged across baselibs (2), cicd-workflows (1), inc_someip_gateway (1), infrastructure (1), lifecycle (1), module_template (2), process_description (1), and score (1).

Issues

• lifecycle — IdentifierHash uses std::hash, not stable across compiler/toolchain builds — crashes Launch Manager on a ControlClient request bug — closed, fixed by PR docs: implement general graph checks scheme #527 above.
• score — includes links are missing in several needs documentation, help wanted, high prio — closed.

12 issues opened, 38 closed in this window.

Footer

S-CORE Daily is generated automatically from public eclipse-score activity for the window shown. Links go to the sources; corrections welcome as replies.

[dcalavrezo-qorix]

S-CORE Daily — 2026-08-31

Headline

Eclipse S-CORE shipped four module releases and merged 32 pull requests on 2026-08-31, while community meetings zeroed in on the final checklist for the upcoming v0.9 release.

In plain terms

Several S-CORE building blocks got new versions today, including the lifecycle module (v0.6.0) and the kyron async runtime (v0.1.4). Across five community meetings, the recurring topic was readiness for the v0.9 release: which modules are done, which still need a new version, and open questions about AI-generated code and possibly delaying the release by a week. Code activity was broad — 32 substantive changes landed across 18 repositories, touching documentation tooling, the lifecycle and baselibs modules, and CI infrastructure. Nothing merged today was flagged as breaking, though one dependency update (lifecycle v0.5.0) is noted elsewhere as having introduced breaking changes to mocks. Anyone tracking the v0.9 timeline should watch the Technical Lead Circle minutes for a final go/no-go.

Releases

• bazel_cpp_toolchains v1.0.3 — adds support for Ebclfsa 2.0.0-beta2. (release)
• kyron v0.1.4 — version bump preparing for the broader v0.9 release. (release)
• lifecycle v0.6.0 — adds a "wait for file ready" condition so components can signal readiness once a configured file appears; includes other fixes and logging improvements. Pre-release notice: not intended for production use, no completed safety assessment. (release)
• score-crates v0.0.12 — fixes a Bazel cargo lockfile definition issue. (release)

From the meetings

Infrastructure Community

• Decisions/Updates: docs-as-code 8.1 adds a metamodel visualization and a module verification report template; module versions for the S-CORE 0.9 release were posted for review.
• Open questions: the reference_integration v0.9 PR does not compile out of the box (first docs build in months); potential to improve llvm caching via an external cache.
  (minutes)

Technical Lead Circle (TL & Communities & CFTs)

• Decisions: DR-8 implementation PR docs: restructure process metamodel #278 merged; PR Detailed Design #280 still in progress.
• Action items: @antonkri to double check Persistency status and prepare a module verification report PR; @arsibo to create a new Logging release; @lavrovvalera to create a new Time release; @antonkri to double check Config Management; @pawelrutkaq to check/raise crates to 0.0.12 in ref-int and switch Kyron to 1.4; @AlexanderLanin to switch docs-as-code to a newer version (e.g. 8.1.0); @antonkri to create a commit with initial release notes for modules; @antonkri to provide the tooling link for Show & Tell.
• Open questions: whether to move the release by one week; tooling module 2.1.0 brings a breaking change for reference_integration, flagged by @PiotrKorkus for the 0.10 cycle.
  (minutes, follow-up)

Architecture Community

• Decisions: reviewers should comment on PR add design decision include path #3196 (design decision include path); the name-collision question was split into a separate decision record, issue #3234.
• Open questions: clarification of the FR Shepherd role and effort expectations, requested by the Valeo-side attendee, was added to the agenda.
  (minutes, agenda addition)

SW Dev Process Community - S-CORE Safety Team

• Agenda: documents should link what they document; clarifying versioning; clarifying ownership of the Module Verification Report Template.
  (minutes)

Technical Lead Circle (Tech Lead Sync)

• Decisions: DR-8 PR docs: restructure process metamodel #278 merged, PR Detailed Design #280 in progress; module verification report should be integrated for v0.9 for baselibs, persistency, and logging.
• Action items: @antonkri to create a commit with initial release notes for modules; @PhilippM-qorix to clarify what to pay attention to when using AI-generated code (context: PR #275 review); @FScholPer to clarify whether the Eclipse Foundation Copilot license can be used in CI (helpdesk ticket opened).
• Open questions: whether to move the release by one week.
  (minutes)

Discussions worth following

• Communication FT Weekly [2026-08-31] — feature-team status update covering SOME/IP, Flatbuffers, Rust API, Methods & Fields, CI, and open bug tickets.
• S-CORE Daily — the collector thread for this newsletter series; already has 3 comments and is the place to follow future issues.

Code changes

.github

• [New feature] Add policy sync dashboard tab, giving a compliance overview with PR links and downloadable JSON (#96).

baselibs

• [Change] Add a Rust wrapper for score::cpp::stop_token, letting Rust applications interact with frameworks like lifecycle that require stop tokens (#461).
• [Change] Enable contributions under score/**/docs/** (#526).
• [Change] Retire unused OS APIs, removing unused cpuid/file-stream/make-dev libraries and making score/os:netdb public (#535).

cicd-actions

• [New feature] Optionally upload Bazel build/test profiles from CI runs for performance investigation (#32).

communication

• [Change] Move skeleton service element requirements (#1007).

config_management

• [Change] Switch to score_lifecycle v0.5.0, adapting to breaking changes introduced in that release's mocks (#58).

docs-as-code

• [New feature] Show test pass/fail status and link to source in verification report tables, instead of bare, uninformative IDs (#773).
• [Bug fix] Treat <error> test cases as failed instead of passed when parsing JUnit results (#774).
• [Bug fix] Preserve per-entry bundle data when rebasing documentation mount entries (#779).

inc_someip_gateway

• [New feature] Add a convenience alias for the SOME/IP config schema file (#262).

itf

• [Maintenance] Commit a module.bazel.lock file so Bazel lockfile-mode workflows work reliably (#140).

kyron

• [Change] Replace a raw waker array with StaticVec in wake_all, removing manual iterator bookkeeping (#167).
• [Change] Fix documentation (#169).

lifecycle

• [Change] Add "wait for file ready" condition support (#500).
• [Change] Use an identifier hash instead of an index for the dependency graph, closing a use-after-free-adjacent design issue (#523).
• [Change] Disable warnings originating from external code so the module's own warnings stay visible (#549).
• [Change] Set up the verification report using the shared central template (#551).
• [Change] Fix a deprecation warning from the mw::com runtime initialization API (#563).
• [Change] Log process startup timing for diagnostics (#565).
• [Change] Add release notes for v0.6.0 (#572).

logging

• [Change] Add record_property calls in tests for requirement traceability (#276).

reference_integration

• [Maintenance] Bump Ebclfsa SDK to 2.0.0-beta2 (#315).
• [CI / automation] Retry flaky SDK downloads (e.g. QNX) via Bazel instead of failing builds outright (#316).

score

• [Bug fix] Keep a software verification link mount-relative so it stays valid when the documentation bundle is mounted under a different prefix — needed for the 0.9 release (#3236).

tooling

• [Change] Add a "class" stereotype (#446).

tools

• [New feature] Schedule policy sync and support an apply mode, running a daily drift-detection plan without failing the workflow (#20).
• [New feature] Include policy metadata (IDs, titles, descriptions) in the JSON report (#21).
• [New feature] Ensure Bazel dependencies by adding a policy and operation for declaring the SCORE devcontainer as a direct dependency (#22).

mcp-servers

• 3 automated dependency updates merged (GitHub Actions and pre-commit/ruff bumps).

Elsewhere, 6 additional automated dependency bumps merged across cicd-workflows, inc_someip_gateway, kyron, lifecycle, logging, and time (9 total automated updates).

Issues

• docs-as-code: docs_bundle propagates transitive data to unrelated mount entries bug — opened and closed same day.
• docs-as-code: Public docs_bundle is not self-contained because bundle examples include files outside docs/ bug
• docs-as-code: fix: respect Bazel package boundaries when mounting docs bundles bug
• score: Decision Record for name collision in include paths & file names community:architecture

10 issues opened, 3 closed.

Footer

S-CORE Daily is generated automatically from public eclipse-score activity for the window shown. Links go to the sources; corrections welcome as replies.

[dcalavrezo-qorix]

S-CORE Daily — 2026-09-01

Headline

Eclipse S-CORE merged 23 pull requests across 13 repositories on 2026-09-01, with meeting minutes confirming SCORE v0.9 will ship next week using the existing release workflow while the new DR8 workflow gets polished.

In plain terms

No new module releases went out on 2026-09-01, but a busy day of code review kept several building blocks moving: cleanup work in baselibs, docs-as-code, and lifecycle, plus a QNX test fix in inc_someip_gateway marked as a breaking change. The Release Community's minutes are the headline: SCORE v0.9 is set to be released next week using the current (non-DR8) integration workflow, with a handful of modules (lifecycle_health, logging, time, config) still needing final touches. The SW Dev Process Community continues discussing template ownership and versioning. Two new discussions opened, including a question about building for generic aarch64 Linux targets. Twelve issues closed, several of them wrapping up a multi-part Bazel toolchain refactor.

From the meetings

General SW Dev Process Community (SW Dev Process Community)

Minutes by @masc2023, link

• Agenda for next session (Sep-03): continue discussion on versioning and template ownership, following up on an earlier thread.
• Open PRs to review: module_template#166.
• No decisions or action items were recorded yet for this upcoming meeting.

Release Community Meeting (Release Community)

Minutes by @PiotrKorkus, link

• Decisions:
  • "CPP toolchains v0.5.4 will be used for SCORE v0.9 release."
  • "SCORE release v0.9 will be created next week with the old integration workflow and DR8 will be integrated to main once all issues are fixed."
• Action items:
  • Kai to create a PR pulling cpp toolchains into known_good.json on the main branch.
  • Piotr to check the root cause of the test workflow failing on the release candidate branch.
  • Anton to create a PR for the persistency module verification report.
  • Piotr to check the Rust failures in the DR8 workflow.
• Open questions / tracked items (v0.9 integration checklist, issue #3186, tracking PR reference_integration#320):
  • orchestrator — needs to be deleted.
  • lifecycle_health — PR to bump to 0.6 still pending.
  • logging — release still to be created.
  • time — needs updating in known_good with a new release.
  • config — will be removed from v0.9 if problems persist, otherwise newest main will be integrated with a new release.
  • DR8 workflow (reference_integration#280) needs polishing before merging, to avoid introducing too much chaos.

Discussions worth following

• Generic aarch64 Linux target in reference_integration? (Q&A, @fortunaLim) — asks whether it's possible to build for aarch64 Linux with mainline glibc, outside the existing QNX and Elektrobit ebclfsa SDK paths; relevant to anyone targeting non-QNX aarch64 platforms.
• Logging CFT Weekly [2026-09-01] (Logging FT, @arsibo) — weekly logging feature-team meeting notes covering plans to create a new logging release and v0.9 goals/backlog items.

Code changes

baselibs

• Remove //score/datetime_converter target and functionality — the implementation was error-prone with leap-second bugs, removed before wider adoption (#471).
• Switch to score_cpp_policies for clang-tidy — centralizes linter configuration since bazel-tools-cc is unmaintained (#514).
• Retire unused OS select wrapper — QNX recommends poll() over select() (#536).

cicd-workflows

• Enable access to git repos in workflows — lets downstream users with private repos check them out (#226).

docs-as-code

• Make docs data root bundle data — reworks how documentation bundle files are declared for Sphinx (#785).
• Do not use literalinclude for now — reverted a broken approach pending a proper fix (#787).
• Remove obsolete license-check workflow — no longer providing working CI coverage for about six months (#788).
• Expand downstream compatibility coverage — adds kyron, lifecycle, logging, and time to downstream compatibility tests (#789).

inc_security_crypto

• Add pkcs11 provider backend pkcs11_dynload — loads a PKCS#11 module at runtime via dlopen() (#168).

inc_someip_gateway

• Breaking change: Run tests on QNX and apply fixes — Connect IPC message size reduced to fit QNX's lower IPC limit (#268).
• Run tests with sanitizers — helps catch bugs earlier (#281).
• Add clang-tidy and ruff checks and fixes — aligns tooling with the communication module ahead of a planned migration (#283).

lifecycle

• Remove test end file — control client test driver now sends SIGTERM directly to launch manager instead of polling for a file (#564).
• Add modernize-concat-nested-namespaces to clang-tidy and apply to codebase — collapses nested namespace declarations across 67 C++ files (#569).

mcp-servers

• Local harness apm — adds graphify and context management for local setup (#12).

os_autosd

• Adding warning list — adds a gcc warning list that throws a compilation error by default (#60).

os_images

• Pin cicd-workflows reusable workflows to a commit SHA — part of a large-scale CI refactoring across S-CORE repositories (#9).
• Update Ebclfsa image to 2.0.0-beta2 and enable IPv4 multicast — makes the image more interchangeable with the Ubuntu image (#30).

reference_integration

• Make timeouts more stable for QNX (#322).
• Use Bazel label for config_management patch reference — aligns with the other seven known_good.json entries (#324).
• Remove Orchestrator module — was scheduled for removal in 0.8 (#325).

tools

• Cross-repository apply bug fix — updates generated PR bodies/labels via GitHub REST, and configures bot identity for cached checkouts (#23).

.eclipsefdn

• Adding os_autosd homepage (#222).

7 automated dependency updates were also merged across baselibs, inc_someip_gateway, lifecycle, module_template, and os_images.

Issues

• communication: Bug: SIGABRT when two independent polling proxies use the same LoLa event — closed, tagged p0.
• Multiple bazel_cpp_toolchains issues tracking a feature-composition refactor of Linux/QNX toolchain templates were closed (#86, #87, #88, #89, #90, #91, #92).

5 issues opened, 12 closed.

Footer

S-CORE Daily is generated automatically from public eclipse-score activity for the window shown. Links go to the sources; corrections welcome as replies.

[dcalavrezo-qorix]

S-CORE Daily — 2026-09-02

Headline

Eclipse S-CORE published three releases and merged 22 pull requests across 12 repositories on 2026-09-02, including a coverage-pipeline overhaul for baselibs and a fix for silently-accepted broken documentation links in docs-as-code.

In plain terms

Three modules — docs-as-code, logging, and the core score repo — shipped new versions today, mostly fixes and documentation cleanup rather than new features. The baselibs and logging repositories both adopted a shared, unified way of measuring test coverage across C++ and Rust code, which should make quality reports more consistent project-wide. In docs-as-code, a bug that let documentation reference undeclared or broken links without failing checks was closed. Community meetings covered Rust safety guidelines, code-scanning follow-ups for baselibs, and an interest group session on hardware accelerators/AI. Nothing breaking or urgent stands out; routine maintenance and cleanup dominated the day.

Releases

• docs-as-code v8.1.1 — Bug-fix release: correct handling of bundled documentation data on rebuilds, fixed test-case link reporting, module-verification-report now shows test results, and additional metamodel checks. Compatible with any docs-as-code 8.y.z. (release)
• logging v0.2.3 — Adds dynamic configuration and file-transfer migration, DLT log capture documentation, safety documents for logging, and adoption of the shared LLVM coverage pipeline; several documentation and CI fixes. (release)
• score v0.7.2 — Small documentation fixes (quality manager role assignment, software verification link) and a dependency bump to docs-as-code v8.1.1. (release)

From the meetings

Infrastructure Community — Rust (link)

• Notes: shared links on Rust safety-critical coding guidelines, a rust-sig discussion, and an article on Rust safety certification. No formal decisions or action items recorded.

Base Libs FT (link)

• Action items: upload scanning results to GitHub Code Scanning; unify clippy, ruff, and clang-tidy since all are based on aspect_rules_lint; clean up the clang-tidy infrastructure in score_cpp_policies, currently hampered by misleading documentation.
• Open question: whether to cancel next week's Baselibs weekly meeting (2026-09-09), as two regular attendees are unavailable.

Lifecycle FT (2026-09-16 minutes, 2026-09-23 minutes)

• Placeholder entries for upcoming meetings; no participants, agenda, or minutes recorded yet.

Discussions worth following

• Interest Group: HW Accelerators/AI — weekly meeting notes posted, referencing an AGENTS.md addition to the score repository; worth watching for how AI-agent tooling gets integrated into the project. (comment)

Code changes

.github

• [Bug fix] Clarify policy-sync dashboard status indicators, replacing ambiguous exclamation marks with clear red-X markers so repositories with an open policy PR show correctly as an actionable state (#97)
• [CI / automation] Added shared daily and PR workflows so .github follows the organization's common maintenance and pull-request check setup (#98)

baselibs

• [Change] Adopted the shared LLVM coverage pipeline from score_tooling, replacing the C++-only gcov/genhtml flow with a single report covering both C++ and Rust, line and branch data, and consistent baselines (#533)

bazel_registry

• Automated dependency update merged (1 change, GitHub Actions hardening).

communication

• [Change] Added a test covering an interface with events, fields, and methods together (#1018)
• [Change] Split the generic skeleton and service elements for clearer structure (#1027)
• [Change] Fixed deprecated runtime initialization (#1034)
• Plus 2 automated dependency updates.

docs-as-code

• [New feature] Added explicit support for treating generated bundle documentation as sources, keeping data for supporting/runtime files, and preserving generated source roots through the bundle manifest (#786)
• [Bug fix] Basedpyright warnings are now treated as errors and the existing warning backlog was cleared, closing a gap where 29 warnings had silently accumulated (#792)
• [Bug fix] Undeclared links are now rejected while parsing the metamodel, fixing a case where broken documentation links failed silently (#793)
• [Bug fix] Fixed a needs_json data issue with a reproduction scenario and restructuring (#796)
• [Maintenance] Annotated resolved source files to fix a pre-commit type-checking failure (#795)
• Plus 1 automated dependency update (GitHub Actions, 2 bumps).

inc_someip_gateway

• [Maintenance] Fixed compiler warnings introduced by the LLVM 19→22 upgrade (#284)
• Plus 1 automated dependency update.

lifecycle

• [Bug fix] The daemon now rejects an unrecognized run target instead of aborting entirely, closing a crash risk where an invalid transition request could take down the whole process (#542)
• [Change] Documentation builds now run on pull requests instead of only from main, and unused license-check/reference-integration workflows were removed (#561)

logging

• [Change] Removed persistent configuration and a related flag from the CW_34 export path (#289)
• [Documentation] Fixed cross-references broken by aggregated documentation builds (#290) and renamed the datarouter_backend README to avoid being excluded from aggregated builds (#292)

process_description

• [Change] Clarified references and formatting in the verification-process requirements documentation (#787)

reference_integration

• [Change] Bumped to lifecycle 0.6.0 for a new feature, expected to remain backwards compatible (#321)
• [Change] Extracted bazel_cpp_toolchains to known_good per a team decision, and corrected a command in generated MODULE.bazel files (#326)

Automated dependency updates: 5 merged across communication (2), inc_someip_gateway (1), rules_imagefs (1), and score (1).

Issues

• baselibs: Fix duplicate Sphinx label baselibs_architecture
• communication: Flaky test in move-construct skeleton integration test flaky-test
• score-crates: iceoryx2-pal-posix-qnx8 always needs a C toolchain, breaking hermetic C++ consumers

7 issues opened, 10 closed.

Footer

S-CORE Daily is generated automatically from public eclipse-score activity for the window shown. Links go to the sources; corrections welcome as replies.

[dcalavrezo-qorix]

S-CORE Daily — 2026-09-03

Headline

Eclipse S-CORE shipped four releases and merged 29 pull requests across 15 repositories on 2026-09-03, headlined by a new time v0.0.2 with QNX build support and a breaking docs-as-code cleanup.

In plain terms

Four modules got new releases today, including a first v0.1.0 for rules_imagefs (a tool for building disk images used in testing) and a fresh v0.0.2 for the time module that adds QNX platform support among many other improvements. Documentation tooling (docs-as-code) removed an old, deprecated option — anyone building docs with that option will need to update, so it's flagged as a breaking change. The Tech Lead Circle discussed possibly delaying the v0.9 release by about a week and continued planning for this very newsletter to run automatically. Seventeen new issues were opened, mostly routine cleanup and traceability work in baselibs, and five were closed.

Releases

• config_management — v0.2.0: updated build tooling versions and switched to score_lifecycle v0.5.0.
• logging — v0.2.4: minor fixes removing the need for patches in the reference integration platform, plus documentation fixes.
• rules_imagefs — v0.1.0: adds ext4 disk-image creation for integration testing; first tagged 0.1.x release for this module.
• time — v0.0.2: exposes daemons publicly, adds QNX build support and a devcontainer for it, refactors CI workflows and CodeQL analysis, and improves unit test coverage.

From the meetings

Meeting Minutes - Tech Lead Sync (Technical Lead Circle)

Link

• Decisions / status:
  • v0.9 release status: "in Progress, probably we will need to move the release v0.9 at least by one week"
• Action items:
  • @PhilippM-qorix to send the AI-usage-in-development proposal to the Technical Leads.
  • @BjoernAtBosch to take the Daily Newsletter proposal to the community for announcement.
  • @FScholPer is clarifying with the Eclipse Foundation how to run the newsletter in CI.

Persistency FT Meeting Minutes 2026 (Persistency FT)

Link

• Updates:
  • New issue: persistency#402.
  • persistency#366: @Ahmed-Elsaka-JC will create subtasks.
  • persistency#375: @arkjedrz will provide the correct command for execution (originally raised by @Saumya-R).
  • Note: some changes were merged without linking to issues.
  • PR persistency#383 is approved and needs to be merged.
  • PR persistency#376 was updated.
• Open items:
  • persistency#337: feedback provided by @Ahmed-Elsaka-JC, waiting on the author to address review points.

Discussions worth following

• Generic aarch64 Linux target in reference_integration? — a Q&A thread on whether S-CORE could support a generic aarch64 Linux target; @opajonk discussed which OS dependencies would need to be covered and shared experience testing on a Raspberry Pi 5 (comment, comment).
• S-CORE Daily — the community discussion about this newsletter received a new comment: yesterday's edition was posted for feedback (link).

Code changes

baselibs

• [Change] Add vajson safety artifacts — contributes vector safety artifacts for vaJson, addressing Testing Community: Kick-Off #203.
• [Change] Fix deprecated implicit copy ctor — fixes a rule-of-five violation in a base type; no user-facing impact.
• [Documentation] Lower quick-start heading level and Disambiguate module architecture Sphinx label — documentation structure and duplicate-label fixes.
• [Change] Increase http_connector_retry_max_timeout to 30s — addresses timeout issues occasionally seen when downloading the QNX SDP.

communication

• [Change] mw/com/dependability: split requirements per high-level architecture.
• [Change] Upgrade baselibs to released version 0.2.12 — also locks the lockfile mode to ensure reproducible dependency resolution.

docs-as-code

• Breaking change — Drop deprecated scan_code parameter — simplifies the API; anyone still using this parameter needs to update.
• [Bug fix] Exclude nested bundle mount roots — fixes duplicate document/ID discovery when a documentation bundle is mounted inside another Sphinx source tree.
• [Refactoring] Introduce wrapper for bundle declaration — untangles the public docs-build functions to ease future changes.
• [CI / automation] Try new caching action — replaces an outdated link-check workflow with Bazel caching to speed up CI.

inc_someip_gateway

• [New feature] End to end performance tests — reworks performance/profiling tests to run under Bazel, a first step toward better performance visibility.

kyron

• [Change] Adopt the LLVM coverage pipeline from score_tooling 2.2.1 — replaces the old coverage flow, a prerequisite for future score_tooling upgrades.

lifecycle

• [Bug fix] Enable ASSERT_DBG in unit tests — fixes a missing debug-assert flag that had silently disabled certain checks.
• [Change] Do not skip sanitizer tests in pipeline — re-enables sanitizer tests, fixing Improvement: Document Configuration Management process #538.
• [Documentation] Lower quick start heading.

logging

• [Change] Link detailed design with wp__sw_implementation.

orchestrator

• [Change] Adopt the LLVM coverage pipeline from score_tooling 2.2.1 — introduces Bazel-level code coverage where previously only a Cargo-based job existed.

reference_integration

• [Change] Bump score_logging to v0.2.3 — prep work for the score v0.9 release.
• [Change] Fix docs build after upstream removal of docs_combo_experimental — unblocks the documentation build step.

rules_imagefs

• [New feature] Add ext4 image creation — creates disk images for integration tests (usable with QEMU); also bumps Bazel to 8.6.0.

scrample

• [Maintenance] Keep declared Bazel version at 8.6.0 or newer — aligns with the org-wide minimum-Bazel-version policy.

time

• [Change] Improve time daemon coverage — closes several branch/line coverage gaps and documents justified exceptions.

tooling

• [Change] Class Diagram <-> Sequence Diagram, Add docs for cpp parser, Parse free function — ongoing work on the C++ parsing/diagramming tooling.

Automated dependency updates: 11 automated bumps were merged across baselibs (2), communication (2), inc_someip_gateway (1), logging (3), module_template (1), process_description (1), and time (1).

Issues

• [baselibs] Six new traceability-cleanup issues opened for hash, concurrency, filesystem, safecpp, result, and string_manipulation/utils components (tooling: Integrate standards charts and Correct tests for checks #550–Logging CFT Weekly [2025-03-04] #556, @4og).
• [communication] Flaky test in move-semantics integration test — flaky-test label.
• [inc_security_crypto] openssl-sys patch mismatch in feature-reduced builds.
• [score-crates] Release 0.0.12 unusable.
• [tools] cr_checker silently accepts malformed copyright headers.

17 issues opened, 5 closed.

Footer

S-CORE Daily is generated automatically from public eclipse-score activity for the window shown. Links go to the sources; corrections welcome as replies.

[dcalavrezo-qorix]

S-CORE Daily — 2026-09-06

Headline

Eclipse S-CORE merged 26 pull requests across 12 repositories and shipped a new lifecycle v0.6.1 release over 2026-09-04 to 2026-09-06.

In plain terms

Over the last three days the lifecycle module got a new release (v0.6.1) that removes an unmaintained build-tooling dependency and fixes early-termination bugs. Twelve repositories saw merged work, from documentation tooling improvements to safety-requirements refinement for the Time feature. The Time feature team discussed how to balance safety (ASIL-B) qualification with practical scope, and the Technical Lead Circle confirmed the S-CORE release timeline may slip by about a week and touched on plans for this very newsletter. Two new community discussions were opened, including a request for an official S-CORE logo. Nothing breaking was flagged in this window.

Releases

• lifecycle — v0.6.1: removed the unmaintained "Hedron's Compile Commands Extractor for Bazel" dependency and related scripts, and made several dependencies non-dev for easier integration. Not intended for production use (no completed safety assessment).

From the meetings

Base Libs FT (thread)

• No meeting held this week ("No meeting this week").

Time FT (thread)

• Decisions: Proposal to merge score#3020 "how it is now and improve it further after FMEA and FTA done"; merge queues approved by the team for smoother multi-PR merging ("Approved from the Team, @NEOatNHNG will create change for that").
• Action items: @NEOatNHNG to create the change enabling merge queues.
• Open questions: how to scope ASIL-B on requirements — whether it should also cover internal data-integrity guarantees, or stay limited (e.g. QM + FFI toward memory), remains undecided.

Technical Lead Circle (thread)

• Decisions: none formally recorded this round.
• Action items: @PhilippM-qorix to send a proposal for AI usage in the development area to the Tech Leads; @BjoernAtBosch to take the Daily Newsletter forward to announce it to the community; @FScholPer to clarify with the Eclipse Foundation how to run the newsletter in CI.
• Open questions: Status of v0.9 — "in Progress, probably we will need to move the release v0.9 at least by one week."

Discussions worth following

• Logo for S-CORE organization in github (Ideas, by @limdor) — the eclipse-score GitHub org currently has no logo even though the Eclipse Foundation project page does; asks whether one should be added.
• SOME/IP in S-CORE [2026-09-04] (Communication FT, by @LittleHuba) — proposal to use mw::com with LoLa as the IPC mechanism within SOME/IP, plus an updated architectural view for the SOME/IP Gateway and Binding use cases.

Code changes

.github

• [Refactoring] Use shared repo-cache for repository checkouts — unifies checkout caching across registry, reference-integration, and platform repos (#99).

baselibs

• [Change] Add test for flatbuffers array header, characterize InterruptibleState SetValue/SetError, and implement LockedPtr::transform — expand test coverage and add a monadic transform helper for concurrency utilities (#437, #517, #456).
• [Change] Keep going and collect clang-tidy reports on CI, then fix the clang-tidy SARIF upload ref — CI no longer aborts on first clang-tidy failure, and its report upload now works correctly (#538, #559).
• [Change] AGENTS.md: clarify copyright header scope and docs layout (#540).

communication

• [Change] Enable core dump extraction for bigdata integration test — stores core files for easier debugging when they're generated (#739).
• [Change] Remove dummy test that falsely linked a safety requirement, exposing the requirement as genuinely uncovered (#1047).

docs-as-code

• [New feature] Add local Needs exports to documentation bundles — lets each bundle expose a standalone requirements inventory for independent validation (#772).
• [Refactoring] Remove deprecated source code linker cache, consolidating on the Bazel-generated sourcelinks path (#803).

inc_security_crypto

• [Change] Adopt the LLVM coverage pipeline from score_tooling 2.2.1 — first coverage flow for this repo, reporting C++ and Rust line/branch coverage together (#198).

lifecycle

• [Change] Fix incorrect behaviour on early termination, including clearer termination reasons and refactored process-info helpers (#576).
• [Change] Remove "Hedron's Compile Commands Extractor for Bazel" as an unmaintained dependency, mark documentation dependencies public, and remove a duplicate bazelrc import — cleanup enabling patches to be removed from reference_integration (#593, #594, #595).
• [Change] Add release notes for v0.6.1 (#596).

reference_integration

• [Change] Fix documentation builds and modules layout, add a missing doc file, fix Graphviz rendering, and move to lifecycle 0.6.1 (#331, #332, #333, #334).

score

• [Change] [TIME] Add ASIL-related requirements and rework existing ones — defines safety-related stakeholder/feature requirements for Time, including FFI and safe time qualification asks (#3020).

tooling

• [New feature] Group architectural design views in software_arch docs — reorganizes the Sphinx page into clearer Requirements/Design/API/Analysis sub-sections (#455).

tools

• [New feature] Handle empty repositories in organization-wide policy sync, skipping them instead of failing (#27).
• [Bug fix] Configure Git credentials for apply mode so policy-update pushes no longer fail with a missing-username error (#29).
• [CI / automation] Separate hourly plan and daily apply for repository policy sync, giving frequent drift visibility without frequent remote mutations (#30).

Automated dependency updates: 7 bumps merged across baselibs, inc_security_crypto (3), lifecycle, module_template, and time.

Issues

• baselibs: How do we satisfy the process demands described when deviating from MISRA required rules
• inc_someip_gateway: Add CRC Mechanism to gatewayd for ASIL Compliance

10 issues opened, 5 closed.

Footer

S-CORE Daily is generated automatically from public eclipse-score activity for the window shown. Links go to the sources; corrections welcome as replies.

[dcalavrezo-qorix]

S-CORE Daily — 2026-09-07

Headline

Eclipse S-CORE shipped reference_integration v0.9.0 and merged 16 pull requests across 8 repositories on 2026-09-07.

In plain terms

The reference integration project — the demo/reference stack that ties S-CORE modules together — reached version 0.9.0, bundling toolchain updates, a logging demo app, and documentation improvements. The lifecycle module saw the most activity, with several process-supervision refactors landing and one CI change reverted the same day after being found problematic. Community meetings focused on preparing v0.9 release notes and lessons learned, plus a continued discussion on SOME/IP communication design. Anyone tracking reference_integration or lifecycle should check the linked pull requests for details; no breaking changes were flagged today.

Releases

• reference_integration — v0.9.0: release rollup including a dashboard tag-resolution fix, removal of the old autosd toolchain, a new logging demo app, a Bazel 8.6.0 update, README improvements (QNX8 aarch64, RPi guide), and dependency bumps (score_config_management, score_itf v0.5.0).

From the meetings

Infrastructure Community

Minutes by @AlexanderLanin — link

• Decisions: Repo Policy Sync is now running with the first few policies.
• Open questions: Semi Maintained Ticket View shared for review.

Technical Lead Circle — Tech Lead Sync

Minutes by @b-rei — link

• Decisions: Release notes for v0.9 need to be revised; acceptance requested at module owner level.
• Action items: Prepare a lessons-learned covering integration process, release notes, documentation, and patch handling (DR08). @FScholPer will check how to improve automated release-note creation.
• Open questions: Feedback on the AI Usage proposal requested within 2–3 days; ML3 feedback expected after 14.09; RUST strategy and implementation approach needs revision and refinement.

Architecture Community

Minutes by @qor-lb — link

• Decisions: Meeting was cancelled due to an insufficient number of agenda items; next meeting scheduled for Sept 14th.

Technical Lead Circle — TL & Communities & CFTs

Minutes by @antonkri — link

• Open questions: Status of v0.9, tracked via reference_integration#320.

Discussions worth following

• Communication FT Weekly [2026-09-07] — new weekly thread from the Communication feature team covering SOME/IP, Flatbuffers, Rust API, and open CI/infrastructure tickets.
• SOME/IP in S-CORE [2026-09-04] — follow-up meeting notes revisit a SOME/IP binding proposal, with concerns raised about reusability compared to a similar proposal from a year ago, plus a question on mw_com Allocate handling for the SOME/IP binding.
• Diagnostics - Weekly — discussion on reviewing inc_diagnostics#26 and how to proceed with a related proposal.
• Generic aarch64 Linux target in reference_integration? — clarifies that the eb-aarch64 build target is currently general-purpose (not EB-corbos-specific), though this may change in later versions.

Code changes

.eclipsefdn

• [Change] Add coverage_tool repository for the S-CORE coverage pipeline — new infrastructure repo to host the LLVM source-based coverage pipeline, published as Bazel module score_coverage (#223)

bazel_registry

• [Change] Extend baselibs and cfg mgmt maintainers by request (#516)

communication

• [Change] Rust target edition removes and rustfmt fix — Rust targets now use the toolchain's default edition instead of per-target settings (#1050)

docs-as-code

• [Change] Make central viewport usable on all screens — improves documentation readability on larger screens (#805)

lifecycle

• [Change] Processes construct their own supervision — moves alive-supervision construction into the ProcessInfoNode constructor, combining the alive monitor thread and implementation (#522)
• [Change] Alive monitor refactor cleanup — follow-up cleanup after docs: Setup demo repository which can link feature-requirements #522, renaming start/stop methods and restructuring supervision files (#571)
• [Change] Introduce counting and waiting test-utility processes — new test utilities for waiting on process counts via named semaphores (#587, #589)
• [Change] Use //... in test workflow — broadens test coverage now that no failures occur (#604)
• [CI / automation] Use new cache actions, then reverted the same day after issues surfaced (#607, #608)
• 2 automated dependency bumps were also merged in lifecycle.

logging

• [Bug fix] Resolve log bridge FFI stable compiler compatibility — fixes crashes when building score_logging against modern stable Rust toolchains, unblocking related inc_security_crypto issues (#275)

mcp-servers

• 3 automated dependency updates merged (setup-uv, ruff-pre-commit, ruff requirement).

reference_integration

• [Change] Release candidate v0.9 — the large integration PR behind today's v0.9.0 release (#320)

Issues

• .github bug: repo sync overview broken good first issue
• 15 opened, 9 closed across the organization today.

Footer

S-CORE Daily is generated automatically from public eclipse-score activity for the window shown. Links go to the sources; corrections welcome as replies.

[dcalavrezo-qorix]

S-CORE Daily — 2026-09-08

Headline

Eclipse S-CORE merged 22 pull requests across 20 repositories on 2026-09-08, with community meetings covering the v0.9 patch follow-up and security/crypto review backlog.

In plain terms

No new releases shipped today, but the project kept moving fast on the follow-up work from last week's v0.9 release: the reference integration repo updated its module version pins and patch overview, and the website published the v0.9 release notes. Several modules landed sizeable engineering work, including a new diagnostics API, a franca datatype parser for communication metadata, and QNX process configuration for the time module. The Release Community meeting flagged a handful of module areas (communication, lifecycle, platform, tooling) still needing patch review before they're fully aligned with v0.9. The Security & Crypto team continues to have a backlog of pull requests awaiting review — worth watching if you depend on that module.

From the meetings

Security & Crypto FT

• Decisions: None recorded this session.
• Action items:
  • PR review backlog highlighted as a concern — too many topics for one hour, many PRs waiting for review.
  • Access control for Crypto (score#3058) — image recreated after being lost, currently under review by ETAS, owner @christianbe9.
  • Backlog grooming continues via the project board.
• Open questions: Ideas requested to improve the weekly meeting format given the volume of pending PRs.
• Minutes by @sunildevda

Release Community

• Decisions: SCORE v0.9 has been created (release, docs); main branch of reference_integration updated with v0.9 versions (PR #336). For communication, it was agreed the dev_dependency setting stays as-is.
• Action items:
  • @LittleHuba to check visibility of communication examples currently located in tutorial doc pages.
  • @kgraeper to forward and check the 4 pending lifecycle patches.
  • @PiotrKorkus to check the pending platform and tooling patches.
• Open questions: How to handle modules whose examples don't expose the real use case — agreed a separate example directly in reference_integration is acceptable when linking from the module repo isn't a good fit.
• Minutes by @PiotrKorkus

SW Dev Process Community — Safety Team

• Decisions: None — no new points were discussed this session.
• Action items: Discussion points captured from the September 1 meeting to be continued at the next meeting (Sep 15).
• Open questions: None recorded.
• Minutes by @CryptoNutcase

Discussions worth following

• Logging CFT Weekly [2026-09-08] — Logging FT meeting minutes by @arsibo, including a decision to pursue a common code-coverage solution and a CFT logging proxy, with @arsibo noted as owner of AVL's Murathan Güzel taking over that task.
• S-CORE Fortnightly — new recurring thread for a two-week digest of S-CORE activity, aimed at both technical and non-technical readers; subscribe here for future issues.

Code changes

.github

• [Change] Update profile README — automated refresh of the organization profile README from the latest metrics snapshot.

bazel_cpp_toolchains

• [Documentation] Explain QNX SDP version selection — clarifies that SDP 8.0.4 selects a different archive than 8.0.0, reducing confusion for users configuring the QNX toolchain.

bazel_platforms

• [New feature] Add git ignore for the module — housekeeping to keep generated files out of version control.

communication

• [Change] Fix line numbers in literalincludes — tutorial documentation was pointing to the wrong lines of source code after later edits; line references are now corrected.

coverage_tool

• [Change] Bootstrap score_coverage from tooling/coverage with tests, lint and docs — extracts the LLVM source-based coverage pipeline into its own Bazel module, a step toward formal tool qualification under the S-CORE tool-management process (ISO 26262-8 clause 11).

docs-as-code

• [Tests] Add golden outputs for docs.bzl scenarios — replaces hard-to-maintain inline Python assertions with explicit golden-file outputs, making the documentation build's test scenarios easier to understand and update.

eclipse-score-website

• [Change] Milestone 0.9 release — publishes the v0.9 release notes on the public S-CORE website.

inc_diagnostics

• [Change] Add DTC C++ API for diag_lib — introduces a Diagnostic Trouble Code API for reporting fault status and configuring fault/debounce behavior, a building block for the diagnostics module.

inc_ecu_model

• [Change] Franca datatype parser — adds a parser/transformer for the Franca-based communication metadata model, including grammar, metadata class model, and deployment property handling.
• [Change] Fix workflow triggers on merge — CI fix so workflows trigger correctly on merge.

inc_someip_gateway

• [New feature] Replace C assert with S-CORE assert — standardizes on the project's own assertion mechanism instead of the C standard library one, for consistency across the codebase.

kyron

• [CI / automation] Change pin of workflows from main to commit — pins CI/CD workflows to a fixed commit hash instead of a moving branch, reducing the risk of unreviewed workflow changes.

lifecycle

• [Change] Simplify alive monitor time — removes the legacy NanoSecondType, simplifying the alive-monitor timing code (closes issue docs: hide safety and security if empty #483).
• [Change] Get rid of legacy names — renames files/classes and cleans up log messages and doxygen comments to drop outdated naming.

os_autosd

• [Change] Baselibs CI — disables an outdated build_autosd job and adds a nightly baselibs job.

reference_integration

• [Change] Alignment after v0.9 — updates module version pins to match the newly released v0.9.
• [Change] Make docs generated — moves documentation generation into the automated build.

testing_tools

• [Change] Move test scenario libraries under score/ — relocates C++/Rust test scenario libraries to align with the project's standard score/ layout (closes reference_integration#141).

time

• [New feature] Add QNX process configuration, schema, docs for TimeSlave reference integration — adds the QNX configuration, JSON schema, and example needed to build and run the TimeSlave process on QNX.

toolchains_rust

• [CI / automation] Pin workflow to commit not main — same CI hardening pattern as kyron, pinning to a fixed commit hash.

tooling

• [Change] [Puml Parser] fix class diagram grammar — corrects grammar handling in the PlantUML class-diagram parser.

tools

• [New feature] Enable globs & comments in exclude file — lets the exclude-file used by the copyright checker use glob patterns and comments, easing maintenance (closes issue Initial version of stakeholder requirements #24).

8 automated dependency bumps were also merged, in persistency (6), reference_integration (1), and time (1).

Issues

• inc_security_crypto: Support of Certificate parsing API — new feature request from the crypto team.
• inc_security_crypto: Support of get public key API — new feature request from the crypto team.
• lifecycle: Simplify alive monitor time cleanup — closed, resolved by PR QNX Compiler Configuration #603 above.

6 issues opened, 5 closed in this window.

Footer

S-CORE Daily is generated automatically from public eclipse-score activity for the window shown. Links go to the sources; corrections welcome as replies.

[dcalavrezo-qorix]

S-CORE Daily — 2026-09-09

Headline

Eclipse S-CORE merged 16 pull requests across 9 repositories on 2026-09-09, while the Infrastructure and Testing community meetings flagged a proposal to standardize on Rust Edition 2024 and closed out review of the v0.9 release.

In plain terms

No new releases shipped today, but the security/crypto module saw a wave of activity: 20 new issues were opened there, laying out a detailed roadmap for certificate handling, OCSP support, trust stores, and cross-provider key operations — useful context if you're building on that module. The Infrastructure community discussed upgrading the project's Rust code to the newer "Edition 2024" language standard, which would need to be written down as a formal platform requirement. The QNX operating-system integration also came up again, with a private-storage request pending with the Eclipse Foundation. On the code side, communication and docs-as-code had the most substantial changes, including internal refactoring and documentation tooling cleanup.

From the meetings

Testing Community

• Decisions: None recorded this session.
• Action items: None recorded beyond the agenda items — SCORE v0.9 release noted, and a pending review flagged for itf#139.
• Open questions: None recorded.
• Minutes by @PiotrKorkus

Infrastructure Community

• Decisions: None recorded this session.
• Action items:
  • A Rust Edition 2024 upgrade was proposed by @bharatGoswami8, with tickets opened in score_rust_policies#13 and toolchains_rust#42.
  • The Rust edition used in the project needs to be defined as a formal Platform requirement (see score#1499).
• Open questions: None recorded.
• Minutes by @dcalavrezo-qorix

Discussions worth following

• S-CORE & QNX — Infrastructure Community meeting minutes: the exception letter for QDL is done, and the group is re-requesting private storage from the Eclipse Foundation, restricted to S-CORE members (comment).
• S-CORE Daily — the previous day's newsletter thread picked up a follow-up comment (link).

Code changes

baselibs

• [Change] Post-process flatc jsonschema output into rich schema — generates JSON schema from Flatbuffers schema definitions with consistent ordering, easing comparison between generations.
• [Change] Correct requirement linking in flatbuffers tests — fixes traceability links between tests and requirements.

communication

• [Change] Split the generic proxy and service elements — splits genericproxy into separate files by functionality, field, and event, and relinks a previously broken test-to-requirement reference.
• [Change] Fix proxy method extract rvalue — small correctness fix in proxy method handling.
• [Change] Refactor OnProxyMethodUnsubscribe to remove code duplication — merges two near-identical unsubscribe methods into one, reducing duplicated logic.
• [Change] Preparation to enable -Wconversion — groundwork for turning on a stricter compiler warning that catches implicit type-conversion bugs.

docs-as-code

• [Refactoring] Simplify documentation target setup — general cleanup of the documentation build configuration.
• [Refactoring] Reorganize the documentation CLI — moves the documentation command-line tool into its own package, making its build ownership and integration contract clearer.
• [Refactoring] Remove sphinxdocs dependency — drops an external Bazel module dependency, simplifying the docs build and keeping ownership of the "Needs" generation in-repo.

inc_security_crypto

• [Change] Fix QNX build and tests — updates dependencies for QNX-compatible Rust builds and pins a compatible libc version, fixing QNX build/test failures.

lifecycle

• [CI / automation] Use new cache actions (only) — trials an improved Bazel build-cache action as an early adopter, ahead of a possible wider rollout.
• [Change] Compiler warnings from score_cpp_policies — starts migrating to a shared, stricter set of compiler warning policies.
• [Change] Add IdentifierHash::if_exists — adds a helper that constructs an identifier hash only when it already exists, avoiding unnecessary allocation.

module_template

• [Change] Added code and test for example component — adds a working code and test example demonstrating the docs_bundle usage pattern for new modules.

persistency

• [Documentation] README.md updates — removes an obsolete README and updates build/test instructions to reflect Bazel-only test running.

tooling

• [Change] [Puml Parser] Support note alias in class diagram — adds support for note aliases in PlantUML class diagrams.

One automated dependency bump was merged (coverage_tool).

Issues

• inc_security_crypto: 20 new issues opened outlining a roadmap for certificate management (CSR generation/parsing, OCSP, trust stores, cross-provider key operations) and crypto configuration — see #207 onward.
• score: Security for S-CORE Release v0.9 closed.
• tooling: PlantUML parser 2.x rejects standard constructs used in logging's design diagrams closed.

25 issues opened, 8 closed across the organization today.

Footer

S-CORE Daily is generated automatically from public eclipse-score activity for the window shown. Links go to the sources; corrections welcome as replies.

[dcalavrezo-qorix]

S-CORE Daily — 2026-09-10

Headline

Eclipse S-CORE merged 18 pull requests across 15 repositories on 2026-09-10, published a first os_images release, and heard from three feature teams that persistency, time, and safety-process work continues to move forward.

In plain terms

A good amount of routine engineering happened today: infrastructure and tooling improvements, QNX/QEMU test setup work, and a documentation-config refactor. The os_images repository cut its very first release (v0.0.0), bundling groundwork like license layout, Bazel toolchain updates, and new OS image support (Ubuntu, autosd, Ebclfsa). The Persistency feature team closed out several PRs and opened new issues to track follow-up work, including a question about how many snapshots a system should be allowed to keep. The Time feature team wrapped up its v0.9 program-increment tickets, moving anything unfinished to v0.10. Nothing this cycle was flagged as breaking or urgent — mostly steady progress.

Releases

• os_images — v0.0.0: first tagged release of the OS images repository, bundling license/layout setup, an autosd image folder, dependency updates, Bazel 8.6.0 requirement, devcontainer/dependabot setup, and new Ubuntu and Ebclfsa image support. This is a v0.0.0 tag — treat it as an early/pre-release baseline rather than a stable release.

From the meetings

Time FT

• Decisions: "v0.9 PI ticket #3011 is closed. All not closed tickets are moved to #3013."
• Action items: Callbacks API — @florianfueller.
• (link)

Persistency FT

• Updates: 5 new issues opened (persistency #409, #410, #411, #412, #413); persistency#375 closed; 8 PRs merged/closed since the last meeting; 1 new PR (docs: not all plantuml types supported #415) and 2 updated PRs (Technical Lead Circle [2025-02-17] #383, docs: Bugfix in YAML translation #401) still in flight.
• Follow-ups: persistency#337 fixes done, awaiting @umaucher's final review; cleanup of score#3052 moved/updated into score#3111, owned by @umaucher.
• (link)

SW Dev Process Community — S-CORE Safety Team

• Open questions: No participants recorded and nothing done "due lack of participants"; agenda repeats prior open items from the General and Safety threads.
• (link)

Discussions worth following

• S-CORE Daily — the previous day's newsletter (2026-09-09) picked up a new comment; the thread continues to serve as the running community digest (link).

Code changes

.eclipsefdn

• [Change] Replace strict status checks with merge queue — switches the persistency repo's branch protection to a squash merge queue, matching baselibs/communication/inc_someip_gateway (#218).

bazel_cpp_toolchains

• [New feature] Refactor features implementation — moves toolchain features to rule-based definitions instead of implementation-level definitions (#132).

communication

• [Change] Divide tests in public API and impl tests (#1010); Upgrade C++ toolchains in module integration, with mw::com's own toolchain upgrade to follow separately (#1065).

docs-as-code

• [Refactoring] Wrap environment access — centralizes environment-variable reading/parsing for consistent, typed configuration handling and clearer errors on missing config; flagged with a breaking-change note (#815). Add central config class — near no-op change that switches execution-context detection to Bazel variables and adds workspace path validation (#817).

inc_security_crypto

• [Change] Refactor integration tests for QNX ITF execution — adds shared ITF integration-test macro, process-runner utility, x86_64 QNX QEMU environment and IFS configuration (#166); Enable run_under_qemu to avoid the cap_net_raw capability unavailable on GitHub runners (#226).

inc_someip_gateway

• [New feature] Quality pack targets — adds Bazel targets for unit/component tests, code coverage, and module documentation tied to the SOME/IP protocol spec (#277).

itf

• [New feature] Add QEMU disk image parameter — lets integration-test binaries/data be supplied via an extra mounted image instead of modifying a QCOW2 image (#139).

lifecycle

• [Change] Document to_chars async-signal-safety assumption in signal_safe_log, closing out issue Copyright year #385 (#622).

os_images

• [New feature] Automatically mount second disk to /opt — mirrors QNX/Docker image behavior so integration-test data is available without extra manual steps (#29).

persistency

• [Change] Rollback googletest version to restore compatibility with baselibs (#415).

reference_integration

• [Change] Add SBOM — draft PR to generate a software bill of materials from code (#304).

tools

• [New feature] Support glob repository selection — lets Repository Policy Sync target repositories with shell-style glob patterns instead of a manually maintained exact-name allowlist, so new repos can be picked up automatically (#33).

module_template, tooling — 2 automated dependency bumps merged (module_template: actions-template-sync; tooling: devcontainer and github-actions groups), plus 2 more automated dependency updates elsewhere (inc_security_crypto, time).

Issues

• persistency: Maximum number of snapshots — open question on snapshot retention limits.
• tools: repo_policy_sync: support glob patterns for repository selection — opened and closed the same day, implemented via tools#33.
• 4 issues opened, 2 closed today.

Footer

S-CORE Daily is generated automatically from public eclipse-score activity for the window shown. Links go to the sources; corrections welcome as replies.

[dcalavrezo-qorix]

S-CORE Daily — 2026-09-13

Headline

Covering three days (2026-09-11 to 2026-09-13), Eclipse S-CORE merged 24 pull requests across 19 repositories and published two releases, including a first release of the new coverage tool.

In plain terms

This report covers a three-day window (Friday through Sunday) rather than a single day. The most notable news is the first release of coverage_tool (score_coverage), a new code-coverage pipeline for S-CORE, plus a docs-as-code fix that makes generated documentation use the full screen width. Work continued across many modules — lifecycle process handling, the SomeIP gateway, logging's DLT transport design, and repository tooling for managing Bazel dependencies and policy pull requests. Nothing in this window is flagged as breaking. People building on S-CORE should note the new score_coverage module (0.1.0) is now available via the Bazel registry, and that the persistency repository's merge-queue setup got its first verification PR.

Releases

• coverage_tool — v0.1.0: first release, bootstrapping score_coverage (the LLVM source-based code coverage pipeline, successor to score_tooling//coverage) with tests, lint and docs, plus a fix to include virtual-includes and vendored headers in the coverage scope.
• docs-as-code — v8.1.2: fix so generated documentation pages use the full screen width. Compatible with any docs-as-code 8.y.z version.

Discussions worth following

• S-CORE Daily (comment) — the ongoing show-and-tell thread received a new post recapping the 2026-09-10 daily digest.

Code changes

baselibs

• [Change] Add test for flatbuffers vector header — extends test coverage for the flatbuffers vector header (PR #564).

bazel_cpp_toolchains

• [Change] Remove unused feature set — cleans up feature sets left over from the migration to target-defined features (PR #136).

bazel_registry

• [New feature] Drop compatibility-level auto-injection — removes injection of the now-deprecated, no-op compatibility_level setting (PR #517).
• [New feature] Add module with first release 0.1.0 — registers score_coverage in the Bazel registry with periodic-pull enabled (PR #518).

coverage_tool

• [Change] Include virtual-includes and vendored headers in the coverage scope — fixes a bug where headers vendored from an external repository (e.g. flatbuffers) were dropped from coverage reports (PR #3).

inc_ecu_model

• [Change] Fix Franca parsing error when handling annotations and anonymous type collections (PR #8).

inc_someip_gateway

• [Maintenance] Make performance tests packet-loss aware — introduces rate limiting so performance tests no longer count every send as successful regardless of network capacity (PR #288).
• [Bug fix] Fix subscription major version issue — passes the configured service major version to vSomeIP subscriptions, preventing subscriptions from getting stuck pending when a different major version is offered (PR #295).

lifecycle

• [Change] Expose //config:test_image to allow overloading test images, plus a --test_runner pytest argument for running tests with different utilities (PR #525).
• [Change] Remove component-level requirements that are no longer needed (PR #562).

logging

• [Documentation] Add DR-002 design record for DLT network transport, covering DLTv2/IPv4 fragmentation support and header construction (PR #299).

mcp-servers

• [Change] Use the active reusable PR-check workflow instead of a no-op one (PR #21).

module_template

• [Change] Add an example for the auto-generated module verification report, improving traceability between logical interfaces and implementing components (PR #166).
• [Change] Refactor tests and improve the component-example structure, adding unit and integration tests (PR #173).

os_autosd

• [Change] Add module tests — nightly jobs now test the building of feature/target modules (PR #62).

persistency

• [Documentation] Fix README title and trailing whitespace — used as a control PR to verify the new merge-queue setup works as expected (PR #419).

score

• [Change] Export logging feature requirements for consumption by the logging module (PR #3250).

score_cpp_policies

• [Documentation] Add documentation on the sanitizers migration (PR #38).

tooling

• [Change] Add headlines above renderings in the docs build, and add examples to the docs build (PR #465, PR #466).

tools

• [New feature] Manage Bazel dev dependencies, make generated pull-request templates configurable, and record the tool checkout revision used to generate policy PRs (PR #34, PR #36, PR #37).
• [Bug fix] Preserve Git auth for pre-commit hooks so hooks fetching private Bazel dependencies no longer fail with authentication errors (PR #38).

Automated dependency updates: 13 bumps merged across inc_security_crypto (4), inc_someip_gateway (2), lifecycle (1), logging (1), module_template (2), persistency (1), process_description (1), and time (1).

Issues

• bazel_registry: drop compatibility_level auto injection closed — resolved by PR Integrate OpenDUT framework for executing SCORE Tests #517 above.
• score_cpp_policies: Update score_cpp_policies documentation for sanitizer features closed — resolved by PR Improvement: WebPage #38 above.

9 issues opened, 11 closed in this window.

Footer

S-CORE Daily is generated automatically from public eclipse-score activity for the window shown. Links go to the sources; corrections welcome as replies.

[dcalavrezo-qorix]

S-CORE Daily — 2026-09-14

Headline

Eclipse S-CORE merged 21 pull requests across 13 repositories and published a tooling release, while community meetings covered a coverage-tool split, QNX status, and next release planning.

In plain terms

The tooling module reached v2.2.2, mostly parser and documentation improvements for diagram and class-diagram tooling. The bigger structural news came from the Infrastructure Community meeting: the LLVM coverage pipeline has moved out of score_tooling into its own module, score_coverage, so it can be independently qualified under the project's Tool Confidence Level process — baselibs is the first module to migrate, and others (like inc_someip_gateway) are following. Elsewhere, work continued on crypto integration tests, communication's Rust API, lifecycle timing configuration, and persistency's key-value store API. Two new discussions are worth a look: one on Rust certification planning, one on the Communication feature team's weekly status. Nothing in this window is flagged as breaking.

Releases

• tooling — v2.2.2: a batch of parser and documentation improvements, including Graphviz support for Lobster reports, class-diagram/sequence-diagram parsing fixes, free-function parsing, and grouping of architectural design views in generated docs.

From the meetings

Security & Crypto FT (Security & Crypto FT)

Minutes by @sunildevda

• Decisions/updates: three PRs closed since last meeting (QNX build/test fixes, ITF test refactor, run_under_qemu change to avoid cap_net_raw); several PRs remain in progress, tracked by owner.
• Action items: ongoing PR reviews assigned to @ChansAlive, @se-lo, @prabakaranklst, @HeHa112, @ShoroukRamzy, @GuruprasadBhatL; access control for Crypto tracked via score#3058 (@christianbe9); hashing migration from Baselibs to Crypto tracked via inc_security_crypto#125 (@kssim).
• Open questions: how to handle cases where HSM/TEE is busy, continuing a discussion raised by Ugesh (BMW) in the wider SCORE meeting.

Architecture Community (Architecture Community)

Minutes by @arsibo

• Meeting cancelled due to insufficient agenda items; next meeting scheduled for September 21.

Infrastructure Community (Infrastructure Community)

Minutes by @dcalavrezo-qorix

• Decisions: the LLVM coverage pipeline is now its own repo and Bazel module, score_coverage 0.1.0, split out of score_tooling following the Tool Management Plan (tools with TCL LOW need full qualification, not just evaluation); rollout to all modules is underway this week, with the first migration in baselibs#584 (also fixes baselibs#558).
• Action items: @dcalavrezo-qorix to compare the project's tool-classification approach with the Useblocks open-source approach; @AlexanderLanin to talk to the process team about the same comparison, and to merge caching improvements this week; @FScholPer to ask the process community what they expect an SBOM to contain.
• Open questions: review by the process team of open points on the coverage-tool split (TVR location, tool_req vs TRLC, who signs off as approver); QNX status has a new open problem this week.

Meeting Minutes (TL & Communities & CFTs) (Technical Lead Circle)

Minutes by @FScholPer

• Decisions: all modules should switch to the new unified code-coverage tooling (an open PR exists for baselibs); next Tuesday's release meeting will be used for release-lead planning.
• Action items: contributors are asked to link code and unit tests to requirements, link component requirements to features, fill out the inspection checklist, and use the traceability overview — as a wish list for the next release.

Discussions worth following

• Rust certification in S-CORE: gap analysis and plan (September 2026) — Infrastructure Community, by @dcalavrezo-qorix: a proposal for the Rust, tooling, and safety-manager communities assessing what's still needed for a Rust ASIL B module to pass a confirmation review against ISO 26262:2018.
• Communication FT Weekly [2026-09-14] — Communication FT, by @LittleHuba: weekly status covering SOME/IP, Flatbuffers, Rust API, CI/infrastructure, and open bug tickets.

Code changes

baselibs

• [Change] Fix unsafe type conversion in stat — addresses a filesystem type-conversion bug (PR #563).
• [Change] Migrate coverage pipeline to score_coverage 0.1.0 — swaps @score_tooling//coverage for the newly split-out, independently qualified coverage module; only labels change, no interface impact (PR #584).

cicd-workflows

• [Change] Use latest action versions with hash pinning in action.yml, following GitHub's recommended practice (PR #233).

communication

• [Change] Large refactor of the type-erased binding (Mf type erased binding) (PR #897).
• [Change] Update tooling to 2.2.2 for rules_score (PR #1075).
• [Change] Ignore unused QualityType argument, fixing a warnings-as-errors build failure when a constexpr branch leaves the argument unused (PR #1078).

docs-as-code

• [Refactoring] Normalize join_path path segments, adding unit coverage and documenting path-normalization behavior for generated docs (PR #819).
• [Tests] Update module_template test path so downstream compatibility checks pass after tests moved location (PR #822).

inc_someip_gateway

• [Tests] Add shared test-capture helpers and migrate ITF tests, part of a larger TC8 conformance test suite effort (PR #292).
• [Maintenance] Switch to the new coverage tooling repo, following the same change as baselibs (PR #297).

lifecycle

• [Change] Replace floating-point seconds with integer milliseconds in timing configuration, removing floating-point representation from the binary format (PR #388).
• [Change] Give each thread a descriptive name (e.g. worker, health_mon, os_handler, lcm_signal) to aid debugging (PR #631).

persistency

• [Bug fix] Correct spacing in KVS log messages, removing doubled spaces from error output (PR #403).
• [Change] Add remove_all_keys(), discard_pending_changes(), and get_storage_file_size() APIs (PR #421).

reference_integration

• [CI / automation] Save workflow cache only on main-branch pushes, not on PRs or feature branches (PR #341).
• [Change] Remove lifecycle patches that are now applied upstream (PR #344).

sbom-tool

• [Change] Fix a build error affecting the dash-licenses scan (PR #11).

score

• [Change] Fix the copyright header comment in aou_req.rst for the time feature (PR #3245).

tooling

• [Change] Add a maturity argument to the safety-analysis tooling (PR #468).

tools

• [Bug fix] Preserve the aspect_rules_py dependency, keeping it usable outside the development-only dependency context (PR #40).
• [New feature] Add a policy-driven GitHub workflow reference update mechanism, a proof of concept to compare against Renovate (PR #41).

5 automated dependency updates merged across baselibs, inc_someip_gateway, lifecycle, os_autosd, and tools (one each).

Issues

• baselibs: score's llvm_cov integration filters flatbuffers headers out of the report closed — resolved by PR Epic: (Initial) Tooling Detailed Design, Implementation, Unit Verification #584 above.
• persistency: Log messages in kvs.cpp have doubled spaces closed — resolved by PR Logging CFT Weekly [2025-02-18] #403 above.
• reference_integration: ref_int - cache improvements closed — resolved by PR new GitHub teams request for operational team #341 above.

16 issues opened, 11 closed in this window.

Footer

S-CORE Daily is generated automatically from public eclipse-score activity for the window shown. Links go to the sources; corrections welcome as replies.

[dcalavrezo-qorix]

S-CORE Daily — 2026-09-15

Headline

Eclipse S-CORE merged 39 pull requests across 23 repositories, with community meetings covering v0.9 lessons learned, reference-integration frequency, and SBOM plans, while no new releases went out.

In plain terms

No module releases shipped in this window, but a wide spread of maintenance and refactoring work landed across 23 repositories — much of it CI/CD hardening (pinning workflow references to commits instead of @main) following an upcoming cleanup in cicd-workflows. The Release Community meeting set concrete expectations: each module should integrate into reference_integration at least once every two weeks, and module owners are asked to start producing SBOMs. The SW Dev Process Community continued planning for v0.9 and v1.0 milestones, and flagged two process-description issues with no assignee. Baselibs saw substantive work too, including new setenv/unsetenv support and Bazel tooling reorganization. Nothing in this window is flagged as breaking.

From the meetings

Base Libs FT Meeting Minutes 2026 (Base Libs FT)

Follow-up by @4og

• Decisions/updates: documentation of score/memory will be cleaned up via baselibs#522; removal of moved-out content tracked in baselibs#586.

General SW Dev Process Community (SW Dev Process Community)

Minutes by @masc2023

• Decisions: discussion on "Versioning, Template Ownership" postponed — no participants present had the relevant knowledge; module_template#166 remains open and will be discussed again next meeting.
• Action items: resolve assignment gap on process_description's "Audit Findings (14.04.2026)" issue (process_description#652) — no owner yet, to be discussed in the next meeting (15.9.2026); a task for introducing ISO 8800 into the process description has been created (process_description#789).
• Open questions: planning status for v0.9 (score#2961) and v1.0 (score#3257); versioning and template-ownership discussion continues in discussions/2234.

Release Community Meeting Minutes (Release Community)

Minutes by @PiotrKorkus (15.09.2026)

• Decisions: module owners should create a PR in reference_integration bumping their module's version (by hash, no formal release needed) at least once every two weeks; GH stacked PRs may be used when several modules need updating together; an SBOM workflow is already integrated in reference_integration (reference_integration#304), and modules should also produce their own SBOM for inclusion in the module verification report.
• Action items: @PiotrKorkus to hold a v0.9 lessons-learned session next week (22.09) and post details in Slack; @AlexanderLanin extending an initial dev-dependency alignment list (contributions welcome, see the policy file); @antonkri to draft a proof-of-concept using baselibs to separate dev-dependencies from regular ones; @Lukasz-Juranek to raise SBOM-in-verification-report idea in the security meeting.
• Open questions: patches from v0.9 still to be checked for baselibs, communication, and config_management; increase-integration-frequency proposal to be further discussed in Monday's tech alignment call.

Minutes by @PiotrKorkus (22.09.2026)

• Decisions: integrating modules takes significant effort — reaffirmed that each module should integrate to reference_integration at least once every two weeks.

Discussions worth following

• Logging CFT Weekly [2026-09-15] — Logging FT, by @arsibo: weekly status noting logging#301 needs an assignee, logging#299 will be updated after discussion, and a proposed rename from "logging" to "log_and_trace" pending a check with a maintainer.

Code changes

.github

• [Bug fix] Use scheduled reports from main so the Pages dashboard only consumes artifacts from the scheduled policy-sync workflow, not manually dispatched runs (PR #103).
• [Bug fix] Compact policy matrix columns to keep the dashboard's policy table readable when policy IDs are long (PR #104).
• [Bug fix] Prevent category scrollbars, fixing a tooltip sizing issue exposed by the compacted matrix columns (PR #105).

baselibs

• [Documentation] Implement setenv and unsetenv in score::os::Stdlib, closing a long-standing feature request (PR #507).
• [Change] Remove a Linux-only constraint from require_typed_memory that was blocking score_communication from using the config setting (PR #539).
• [CI / automation] Consolidate linting with rules_lint, fixing an issue where sandboxed clang-tidy failures silently dropped build outputs (PR #576).
• [Change] Move dev-only Bazel tooling (copyright, formatting, license checks) out of the root BUILD file into a dedicated tools/BUILD, keeping the root build free of dev dependencies (PR #585).

bazel_cpp_toolchains

• [Maintenance] Pin cicd-workflows references to a commit ahead of an upcoming workflow cleanup (PR #143).
• [Bug fix] Fix the sysroot directory for AArch64 builds on AutoSD, pointing to the whole directory instead of a file list (PR #144).
• [Change] Update the CODEOWNERs list (PR #145).
• [Bug fix] Pass sysroot flags to assembly actions while keeping linker-specific flags limited to link actions (PR #146).

cicd-workflows

• [Change] Fix common checks enabling cache too late in on-PR workflows (PR #232).

communication

• [Change] Resolve locked MISRA package dependencies offline without mutating the real home directory, using a hermetic per-invocation fake HOME for CodeQL (PR #1081).
• [Change] Declare a missing safe_math dependency for lola/messaging that was only resolving transitively (PR #1089).

coverage_tool

• [Change] Pin the license-check workflow reference to a commit for reproducible CI (PR #7).

docs-as-code

• [CI / automation] Try cached workflows based on a new setup-bazel-cache action (PR #816).
• [Refactoring] Derive bundle runtime paths from source_dir, and a related series of path-handling refactors: clarify runtime-to-execroot path conversion (PR #823), expose bundle source paths in execroot form (PR #824), remove unused explicit source metadata (PR #825), and centralize documentation path resolution in one place instead of reconstructing it from raw environment variables (PR #820, PR #827).

inc_diagnostics

• [Maintenance] Pin cicd-workflows references ahead of a planned workflow cleanup (PR #34).
• [Change] Pin the license-check workflow reference to a commit (PR #35).

inc_ecu_model

• [Change] Refactor the data type model, a large restructuring (PR #7).

kyron

• [Change] Pin the QNX workflow reference to a commit for reproducible CI (PR #173).

lifecycle

• [Bug fix] Replace score::cpp::expected with score::Result in launch_manager concurrency types, part of a broader error-handling migration (PR #577).
• [Change] Remove redundant whitespace from log messages caused by mw::log's automatic spacing (PR #636).

mcp-servers

• One dependency bump: ruff-pre-commit to v0.16.6 (PR #25).

module_template

• [Change] Improve clarity and guidance in the module verification report template (PR #178).

persistency

• [Bug fix] Classify KVS unit and integration tests as "small" to remove default-test-size warnings (PR #424).

reference_integration

• [Change] Pin the tests workflow reference to a commit (PR #345).

rules_imagefs

• [Maintenance] Pin cicd-workflows references ahead of a planned cleanup (PR #21).

score

• [Change] Fix broken links to the Baselibs safety manual in the platform safety manual, which pointed to an unpublished path (PR #3242).

score-crates

• [Bug fix] Pin a workflow reference to a commit instead of main (PR #76).

score_rust_policies

• [Bug fix] Pin a workflow reference to a commit instead of main (PR #14).

time

• [Change] Rename the SOCK environment variable to BPF_DEVICE_PREFIX, fixing a QNX startup failure where ClockIdentity resolution could fail on vtnet0 due to env-variable coupling (PR #218).

tooling

• [Change] Add validation support for override, virtual, and noexcept in PlantUML tooling for interface-inheriting classes (PR #469).

tools

• [Bug fix] Use a stable report artifact name so the cross-repository metrics dashboard can reliably retrieve policy-sync reports (PR #43).
• [Bug fix] Recognize tagged newer SHA pins, fixing false policy failures when a minimum-release SHA and current-release SHA diverge in Git history (PR #44).

2 automated dependency updates merged across inc_security_crypto and score (one each).

Issues

• baselibs: Fix unsafe st_uid conversion to int64_t in StatBuffer closed.
• bazel_cpp_toolchains: Missing sysroot flags for assembler actions in 1.0.3 for autosd10 build and Broken --sysroot path generation for aarch64 cross-builds closed — resolved by PR docs: add recommended extensions #146 and PR move docs tooling to _tooling #144 above.
• cicd-workflows: common checks enables cache too late closed — resolved by PR Plan the process community goals realization for safety confirmation measures #232 above.
• time: QNX QEMU time_slave ClockIdentity fails on vtnet0 closed — resolved by PR Document current concept for multi repo dependencies #218 above.

14 issues opened, 8 closed in this window.

Footer

S-CORE Daily is generated automatically from public eclipse-score activity for the window shown. Links go to the sources; corrections welcome as replies.

[dcalavrezo-qorix]

S-CORE Daily — 2026-10-04

Headline: Over the weekend (2–4 October), S-CORE merged 35 pull requests across 18 repositories, led by code-quality clean-ups in the communication module, and published a C++ toolchain pre-release.

In plain terms

This issue covers three days (Fri 2 – Sun 4 October). Most work was housekeeping that makes the code safer and easier to maintain: the communication module fixed dozens of static-analysis findings (automated checks that flag risky code patterns) without changing behavior. The lifecycle module now rejects unsupported start-up configurations at build time instead of failing later. Several repositories moved to the new shared coverage tool, and the JSON library had a small change reverted after a test failed. Worth watching: the Time team's integration planning and an open discussion on how to prove a requirement is fully verified by many tests.

Releases

• bazel_cpp_toolchains v1.0.5-rc1 — pre-release / non-production test release. The GCC version flag is now derived from the resolved toolchain version, and rules_cc was bumped to 0.2.25.

From the meetings

Time FT — Weekly 2026-09-25, minutes by @lavrovvalera (comment)

• Decisions / status:
  • "Callback impl is almost ready"
  • Requirements: "in progress, next week is expectations to have the PR"
  • TimeDaemon configuration: "we need to have the possibility to configure the thresholds"
• Action items:
  • @MaciejSalwa543 and @lavrovvalera to prepare the TimeDaemon integration strategy proposal; @lavrovvalera to find a ticket for it
  • @lavrovvalera to clean up the v0.10 planning (plan for 09.10)
  • @lavrovvalera to create a ticket for threshold configuration
  • Review the SW component requirements: @lavrovvalera and anybody
• Open questions:
  • Verification: "we are lacking the systematic strategy" for testing, mainly at integration level; waiting for feedback from @BlueXMarv3l; low-expectation precision smoke tests were suggested
  • Idea of a common config for TimeSlave and TimeDaemon, with the possible blocker that projects may use a different TimeSlave process

Discussions worth following

• SW Dev Process Community: How to go from multiple partially_verifies to a fully_verifies — a new comment from @a-zw notes that maintaining the list of test instantiations manually defeats the purpose of typed tests, while declaring it as a pattern weakens the idea that someone reviewed all tests; no solution yet (comment).

Code changes

Infrastructure and tooling

.eclipsefdn

• [Change] Custom CodeQL settings for lifecycle; project tab shown in all infrastructure repos — makes security-scanning setup explicit per repo (#232)

tools

• [New feature] Managed-block policy synchronization — lets repository policy files be kept in sync while preserving surrounding content (#52)
• [Bug fix] Bazel filegroups can now be passed to the pytest macro (#53)

docs-as-code

• [New feature] Adopts pytest from tools, removing ~600 lines of duplicated code (#881)
• [Bug fix] Warns on duplicate external Need IDs that share a base URL, which could previously hide conflicts (#895)
• [Change] external_needs accepts a public docs target, so authors don't need to know internal targets (#897)

coverage_tool

• [Documentation] Coverage architecture page rewritten for readers (#18)

rules_imagefs

• [Change] Adds license information for mke2fs (#24)

Modules

baselibs

• [New feature] Upgrade to score_bazel_cpp_toolchains 1.0.4 (#503)
• [Change] JSON serializer (vajson): pretty printing added and made the default output format (#636, #653)
• [Change] A fix to serialize numbers by stored type (#646) was reverted after a test failed (#656); the related precision issue was closed
• [Change] Component docs now carry code-target metadata so documentation links to source (#641)

communication

• [Bug fix] Series of static-analysis clean-ups with no behavior change: member initialization, redundant std::move, redundant c_str(), C-style arrays, intentional integer-to-pointer casts, and noexcept rules (#1192, #1210, #1225, #1232, #1233, #1235)
• [Build] Macros ignored in cognitive-complexity checks (#1238)
• [Change] Packages upgraded to versions without known vulnerabilities (#1249)

lifecycle

• [Change] Unsupported ready-condition configurations now cause a build error (#724); requirements reworded for clarity (#687)
• [Change] Completes the migration to score_coverage 0.3.1, with manual QNX coverage for C++ (#735); VS Code settings updated (#729)

logging

• [Change] Coverage pipeline migrated to score_coverage 0.3.1 (Linux only) (#338)

persistency

• [Change] Editorial and architecture document updates, safety plan aligned to templates (#453, #458)
• [Maintenance] Bazel updated to 8.7.0 (#454)

inc_ecu_model

• [Change] Shared, reproducible ruff and buildifier lint setup across editor, hooks and CI (#22)

inc_security_crypto

• [Change] rust-analyzer configured for the Bazel workspace in VS Code (#269)

Process and architecture

process_description

• [Change] Monitoring requirement link completeness and extended versioned-links concept for requirements and architecture (#806, #807)

score

• [Change] Lifecycle logical interfaces refined, adding a ReportRunning interface (#3297)

Automated dependency updates: 7 merged (bazel_cpp_toolchains, docs-as-code, itf, lifecycle, logging, module_template, nlohmann_json).

Issues

• docs-as-code: Decision: How should external_needs find a docs target's local Needs?
• communication: four Rust API improvement proposals on the async service stream and futures, thiserror, paste crate usage (#1261, #1263, #1264, #1265); eight automatically filed flaky-test reports
• lifecycle: Blocking wait for "Terminated" state Ready Condition

16 issues opened, 9 closed.

S-CORE Daily is generated automatically from public eclipse-score activity for the window shown. Links go to the sources; corrections welcome as replies.

[dcalavrezo-qorix]

S-CORE Daily — 2026-10-05

Headline: On 5 October, S-CORE published tooling release v2.3.1, merged 25 pull requests across 13 repositories (mostly communication and docs-as-code), and closed 78 issues in a large backlog clean-up.

In plain terms

A new version of the shared build tooling (v2.3.1) was released, and the communication module has already adopted it. Much of the day's work was code-quality tidying in the communication module and extra test coverage for the documentation tooling. Three weekly meetings posted notes, covering architecture, infrastructure and the technical lead circle; the technical lead circle reminded everyone to handle the bot-generated pull requests as part of daily work. A new discussion asks for C and Classic AUTOSAR support in the communication layer (LoLa / mw::com, the inter-application messaging). Also worth watching: 78 issues were closed in one day, mostly old ones.

Releases

• tooling v2.3.1 — new version of the shared tooling used across modules; the communication module bumped to it the same day. (release)

From the meetings

Architecture Community — (minutes)

• Decisions: none recorded.
• Action items: none recorded.
• Open questions: agenda for 2026-10-12: an item from @basheerFZ (linked to score issue [Contribution Proposal] SOME/IP Stack LG Electronics #2807) and a review of the project board.

Infrastructure Community — (minutes)

• Decisions: none recorded.
• Action items: "@kgraeper will provide use cases in #infrastructure slack channel, and a summary for these meeting minutes".
• Open questions: "do all classifications now move to their respective repositories? (process meeting tomorrow)"; "do we transform all existing tool classifications?"; "BUILD.bazel currently stilly unclear". Also noted: "qnx sdp: empty repos created" and "coverage per component".

Technical Lead Circle — (minutes, bot overview follow-up)

• Decisions: none recorded.
• Action items: bot-generated PRs should be taken into daily work (overview: https://eclipse-score.github.io/.github/#policy-sync).
• Module updates as recorded: BAS release done last week with a breaking change, removing other deprecated parts; COM release done, not yet in ref-int; LOG feature renaming and two new components to come; PER merge into ref-int done, issues with Rust and C++ in parallel; SEC aiming for re-integration by mid-November; TIM ramping up.
• @AlexanderLanin's follow-up describes the three bots (Renovate, Dependabot, score-bot).

Discussions worth following

• LoLa / mw::com support for C and Classic AUTOSAR (Architecture Community) — request to let applications on a safety core or in Classic AUTOSAR act as regular publishers/subscribers. (discussion)
• Communication FT Weekly [2026-10-5] — new weekly thread with status items on SOME/IP, Flatbuffers, Rust API and Methods & Fields. (discussion)
• Diagnostics – Weekly — first integration into S-CORE should use existing components; @FScholPer to check how new apps can be registered in core. (comment)

Code changes

Libraries and middleware

baselibs

• [Documentation] String manipulation now has its own requirements and test links. (#580)
• [Change] The JSON writer now serializes numbers using their stored type, fixing lost precision on doubles. (#657)

communication

• [Change] Rust API method renamed to get_instance_specifier to match what it returns. (#1138)
• [Change] Calling OfferService multiple times no longer re-offers an already offered service. (#1149)
• [Change] Tooling bumped to 2.3.1 and safety analyses adapted. (#1243)
• [Change] Rust integration test now runs in regular test runs (skipped under sanitizers); unmaintained paste crate replaced by pastey. (#1267, #1268)
• [Bug fix / Refactoring] Code-quality findings in samples and tutorials resolved. (#1250, #1277)
• [Formatting / Bug fix] Build-file tidy-ups: autofixes, docstrings, and apparent repository names. (#1272, #1273, #1274)

lifecycle

• [Change] Launch Manager configuration picture in the feature architecture extended. (#717)

persistency

• [Change] Migrated from deprecated score::ResultBlank to score::Result<void>. (#455)
• [Bug fix] Test helper now taken from score_tools instead of score_tooling. (#463)

Tooling and integration

docs-as-code

• [New feature] New valid_inspected status marks requirements and architecture elements as formally inspected. (#893)
• [Refactoring] Internal Bazel improvement: bundle-local Needs exposed as JSON files; no change to documentation output. (#901)
• [Tests] Several tool requirements now fully verified. (#905, #907, #910, #911)

module_template

• [Change] Safety analysis templates fixed (safety relevance and root cause added). (#189)

reference_integration

• [Change] Lifecycle, logging and persistency module tests now run in the docs job, so requirement coverage appears in verification reports. (#385)

tooling

• [Change] PlantUML identifier handling cleaned up. (#496)
• [Change] Root causes now link directly to failure modes in safety analysis rules. (#498)

Automated dependency updates: 9 merged across 9 repositories.

Issues

• Opened: safety analysis templates outdated (docs-as-code#903, module_template#190, both already closed); Rust Certification (score#3301); moving OpenSSL to a separate repo (inc_security_crypto#272); flaky communication test (communication#1269).
• 17 issues opened, 78 closed.

S-CORE Daily is generated automatically from public eclipse-score activity for the window shown. Links go to the sources; corrections welcome as replies.

[dcalavrezo-qorix]

S-CORE Daily — 2026-10-06

Headline: On 6 October, S-CORE released score-crates v0.0.13, merged 43 pull requests across 18 repositories (many of them static-analysis clean-ups in communication), and discussed which test tooling must not leak into user-facing dependencies.

In plain terms

Most of the day's work was housekeeping that makes the code cleaner and safer: a long series of small fixes in the communication module resolved dozens of code-quality warnings. A new Linux system-log backend for the logging module was merged, and the lifecycle module gained a new setting plus corrected architecture diagrams. The Release Community discussed that testing tools used for integration tests should not be hidden as "dev-only" dependencies, so people building on S-CORE do not inherit them unintentionally. Worth watching: modules are asked to commit to the DR8 verification workflow, and a follow-up check of which modules currently fail it is planned.

Releases

• score-crates v0.0.13 — fixes lockfile generation (release 0.0.12 had been reported unusable) and pins a workflow to a fixed commit instead of main; includes one first-time contributor. (release)

From the meetings

Release Community (minutes, by @PiotrKorkus)

• Decisions / conclusions:
  • "score_itf is framework for running integration tests, so ITF cannot be a dev_dependency (same for its dependencies e.g. rules_oci)".
  • "Actual users of SCORE might not want to use ITF, so we should not leak our dev_dependecies used for verification."
  • Define a list of public targets: one public target per module for each of libraries, binaries, unit test suite and integration test suite.
• Action items: @PiotrKorkus will check which modules are currently failing the DR8 workflow integration and discuss updates at next Monday's meeting.
• Open questions: "we need commitment from the Modules if we proceed with DR8"; changing the dev-dependency handling will influence DR8.

Base Libs FT (minutes, by @4og)

• Agenda: nlohmann_json backend removal (baselibs#632). No decisions recorded.

Security & Crypto FT (minutes, by @sunildevda)

• Agenda for 7 Oct: check participants, PRs closed since last meeting, status of ongoing PRs. No decisions recorded.

SW Dev Process Community (minutes, by @aschemmel-tech)

• Action items: epic for AI development process "safety" piloting — "who could do it?" (link to be added by @masc2023).
• Open questions: "Is a module an architectural element?"

Discussions worth following

• Logging CFT Weekly 2026-10-06 — new weekly notes from Logging FT, including a reminder to handle bot-generated policy-sync PRs.
• LoLa / mw::com support for C and Classic AUTOSAR — a reply states S-CORE targets large ECUs and points to eclipse-openbsw for classic use cases (comment).

Code changes

Infrastructure and CI

• .eclipsefdn — [Change] Add OpenSSL bazelification repository to the organization config (#234); [Change] baselibs bypass restricted to PR merges, a team member added (#235).
• .github — [Bug fix] Pages dashboard keeps the existing view when the policy report is unavailable (#116).
• cicd-workflows — [Bug fix] Documentation previews now work for fork PRs when an owner has multiple forks (#244).
• coverage_tool — [Change] Tests of coverage workflows used by downstream consumers (#22).
• config_management — [CI] Fix CI exclusion (#68); [Change] Consolidated version bumps (#71).
• inc_diagnostics — [Maintenance] Policy-sync update of gitignore (#20).
• score-crates — [Change] Corrected lockfile generation, closing the "Release 0.0.12 unusable" issue (#78).
• reference_integration — [Change] Added a missing test requirement to get the pipeline green again (#386).

Modules

• communication — [Bug fix] Eleven small code-quality fixes (initialisation, avoiding copies, modern C++ idioms, justified suppressions) (#1292, #1293, #1294, #1295, #1296, #1298, #1299, #1300, #1302, #1304, #1306). [Change] The API-surface documentation check no longer crashes when undocumented symbols exist (#1054).
• lifecycle — [Change] Runmask/affinity configuration is now exposed (#721); corrected state and alive-supervision diagrams (#736, #737); CodeQL report attached to releases and docs published on release (#745, #747).
• logging — [New feature] Linux syslog backend for system log mode (#271).
• persistency — [New feature] License handling moved to the score_sbom tool, producing SPDX and CycloneDX SBOMs (#430); [Bug fix] unique pip hub name (#466); [Change] score_crates updated to 0.0.13 (#467).
• inc_security_crypto — [Change] QEMU RAM disk increased to 1 GB (#274).

Tooling and documentation

• docs-as-code — [New feature] Needs marked invalid are exempt from checks (#914).
• tooling — [Change] Nested qualified declarations, rooted form and :: support (#501).
• process_description — [Change] Attribute renamed to tool_version (#814); Documentation Management Plan template added (#818).
• score — [Change] Lifecycle feature requirements clarified (#3281); pytest tool verification report (#2717); [Documentation] incubation path added to the FEP guide (#3299).
• mcp-servers — [Maintenance] Three automated dependency bumps (#37, #38, #39).

Automated dependency updates: 4 merged (coverage_tool 1, inc_diagnostics 1, inc_security_crypto 1, reference_integration 1).

Issues

• Highlighted: tools#56 repo-sync should add non-dev dependencies (ties to the Release Community discussion); docs-as-code#918 decide how to continue with metrics.json; lifecycle#750 process exit codes logged incorrectly (bug, good first issue); coverage_tool#23 scope evaluated in exec configuration (bug); score#3305 system monitoring driver/sensor framework request (feature_request).
• Counts: 25 opened, 15 closed.

---

S-CORE Daily is generated automatically from public eclipse-score activity for the window shown. Links go to the sources; corrections welcome as replies.

[dcalavrezo-qorix]

S-CORE Daily — 2026-10-07

Headline: On 7 October, S-CORE published the first QNX SDP module (v0.0.1, pre-release) and score v0.7.3, and merged 69 pull requests across 19 repositories.

In plain terms

A new module, qnx_sdp, appeared. It hosts build targets for manually building the QNX SDP (QNX's software development platform) and is now listed in the Bazel registry. The score release v0.7.3 bundles new requirements and documentation fixes, though a registry change today removes its entry because the release was deleted. Much of the day's work was in safety analysis, code-quality clean-ups in communication, and documentation tooling. One thing to watch: a breaking change in the PlantUML tooling that requires diagram names to match the actual implementation.

Releases

• qnx_sdp v0.0.1 (pre-release) — initial commit for QNX SDP generation; first contribution by @nradakovic. Release
• score v0.7.3 — new time-feature ASIL requirements, logging feature requirements exported for consumption, a design record on the module folder structure, safety manual link fixes and dependency updates. Note: the Bazel registry change #525 states this release was deleted and removes score_platform 0.7.3 from the registry. Release

From the meetings

Technical Lead Circle — Tech Lead Sync (minutes by @antonkri)

• Decisions: none recorded.
• Action items: none recorded.
• Open questions / agenda: QNX tarball download (@nradakovic); reasoning for the reference_integration repo (score#3306); S-Core Compatibility Test Suite (score#3315); missing label for Component Request (baselibs#632); budget for infrastructure topics.

Infrastructure Community — Weekly Rust (minutes by @dcalavrezo-qorix)

• Decisions: none recorded.
• Action items: none recorded.
• Notes: "no show"; "RUST coding guidelines PR still opened" (score#3262).

Lifecycle Feature Team — @SimonKozik posted empty templates for upcoming meetings: 2026-10-28, 2026-11-04, 2026-11-11.

Discussions worth following

• Infrastructure/Process Workshop "Docs-As-Code" (new, Technical Lead Circle) — proposes a workshop on the docs-as-code approach used to generate and maintain requirements, architecture, test results and traceability.
• S-CORE & QNX — @AlexanderLanin asked @waynebeaton for an update on the technical user for QNX license/download (comment).

Code changes

Breaking change

tooling

• [Change] PlantUML tooling now uses the diagram element name rather than the alias for IDs, so names must match the implementation — #508

Infrastructure & tooling

tooling

• [Change] Related PlantUML work: sequence-diagram IDs and validators, clearer diagnostics and a more reliable linker — #506, #509
• [Change] Dependable elements now derive their assumptions of use from safety-analysis measures — #510
• [Change] Added a component design-name test — #504

docs-as-code

• [New feature] Requirement reference-coverage pie charts and gap tables in the platform verification report — #896, #921
• [Tests] Better requirement-based test coverage and metadata clean-up — #906, #908, #909, #912, #922, #925
• [Maintenance] Workflow reference bump — #882

coverage_tool

• [Change] Coverage scope is now evaluated for the target platform, so QNX reports include the right files — #24

bazel_registry

• [New feature] Added the qnx_sdp module — #526
• [Change] Removed score_platform 0.7.3 — #525

.eclipsefdn

• [Change] QNX SDP repositories granted access to QNX secrets — #228

qnx_sdp

• [Change] Initial commit for QNX SDP generation — #1

toolchains_rust

• [CI / automation] Workflow compiling and running a Rust Hello World on QNX under QEMU (aarch64) — #45

mcp-servers

• [Change] Added a requirements-resolve layer — #29

Platform & modules

communication

• [Change] Safety analysis (fault trees) for event sending, allocation, subscribe/unsubscribe, receive handlers and API misuse; safety design moved to its own folder — #1280, #1282, #1283, #1284, #1286, #1307, #1308, #1309, #1310
• [Change] Dual-QEMU integration test for the transport layer on QNX — #1150
• [Change] SOME/IP stack base split — #1159
• [Bug fix / Refactoring] Static-analysis clean-ups (casts, default arguments, bounds checks, spans) and tuned analysis settings — #1305, #1314, #1315, #1316, #1317, #1318, #1321, #1322, #1323, #1324, #1325, #1326, #1328, #1336, #1337, #1338

baselibs

• [Change] Flatbuffers upgraded to fix dependency issues — #662
• [Change] Schema helper for JSON-schema generation; QNX x86_64 test fix — #621, #658

lifecycle

• [Change] Alive-monitor testability, new unit tests, mock reorganisation, code-scanning fixes and API casing aligned to S-CORE — #710, #731, #744, #753, #754, #756

persistency

• [Build] Dependency and toolchain clean-up; docs build excluded from merge-queue runs — #470, #473

time

• [Change] Component requirements for ts_client and time_slave; test-suite fix — #149, #151, #238

inc_security_crypto

• [Change] Uses shared memory from communication; updated dependencies — #279

Process & documentation

score

• [Change] Quality Management Plan updated; documentation build fixed; folder-structure guideline now has no exceptions — #3309, #3310, #3312

process_description

• [Change] Architecture element definition and interface documentation guidance updated — #815, #819

module_template

• [Change] Documentation management plan tables added — #193

Automated dependency updates: 4 merged (inc_security_crypto 1, reference_integration 2, testing_tools 1).

Issues

• Bug: Concurrent lifecycle PRs leave a broken requirement link despite passing checks — opened and closed.
• Bug: coverage_tool scope evaluated for host, not target — closed.
• Discuss-with-process: valid_from mandatory in metamodel — closed.
• Roll out SBOM generation to all S-CORE modules — opened (infrastructure, process).

4 issues opened, 7 closed.

---

S-CORE Daily is generated automatically from public eclipse-score activity for the window shown. Links go to the sources; corrections welcome as replies.

[dcalavrezo-qorix]

S-CORE Daily — 2026-10-08

Headline: On 8 October, S-CORE published itf v0.6.0 and merged 49 pull requests across 16 repositories, with much of the activity in lifecycle, persistency, and time.

In plain terms

The integration test framework (ITF) got a new release with better QEMU virtual-machine support and core-dump extraction from containers. The Persistency team reorganised its C++ and Rust code and added the ability to load a chosen snapshot of stored data. The Lifecycle module (which starts and stops applications) received naming cleanups, more tests and clearer design diagrams. Documentation, traceability and safety-analysis work continued in several modules. Watch for new "adopt the global toolchain configuration" issues opened in several modules.

Releases

• itf v0.6.0 — adds an extension hook and Ubuntu/EB Linux support for the QEMU plugin, a QEMU disk image parameter, core-dump extraction from containers in the Docker plugin, and a Bazel 8.6.0 update. Release

From the meetings

Persistency FT — minutes by @umaucher, 2026-10-08 (comment)

• Decisions: none recorded.
• Action items: none recorded.
• Open questions: none recorded.
• Participants listed as present: @PandaeDo, @umaucher, @Ahmed-Elsaka-JC, @arkjedrz, @karolnowak. The minutes list persistency issues ci: Fix multiple PR comments with docs link #411, process: define documentation_management.rst #436, Logging CFT Weekly [2025-02-25] #439 as updated, docs: Improved the publishing of docs to GH pages #267 and python: provide debugger #445 as closed, and several PRs (ITF module entry in eclipse-score/bazel_registry #456–tooling: Correct Stakeholders' requirements ids to be meaningful. #477) as new, updated or merged.

Discussions worth following

• S-CORE Daily (Show and tell) — received a new comment with the 2026-10-07 edition (comment).

Code changes

.eclipsefdn

• [Change] Homepage added to the communication repository and merge queue enabled for tooling — repository settings housekeeping (#236).

cicd-workflows

• [New feature] Superseded pending approvals for fork PRs are now cancelled, reducing stale waiting runs (#245).
• [Bug fix] Restored documentation preview publishing for fork pull requests (#247).

communication

• [Change] Fault tree analyses (FTAs) added or linked for failure modes, improving the traceability report (#1279, #1332).
• [Change] Safety sentinel skeleton design split according to component design (#1281); link to code of conduct added (#1345).
• [Build] Fixed clang-tidy configuration that silently disabled 8 checks, plus resulting findings (#1334).
• [Bug fix] override/final usage aligned with MISRA C++ rule 13.3.1 (#1348).

coverage_tool

• [Change] Tests consolidated under a common tests/ directory (#31).
• [CI / automation] Formatting checks now run through pre-commit (#32).

docs-as-code

• [Change] FMEA attribute root_cause renamed to failure_root_cause for clarity (#916); docs-publish workflow reference updated (#931).
• [Tests] Requirements coverage fix for docs_saf_attrs_mandatory (#923).

inc_security_crypto

• [Change] OpenSSL provider now supports AES-CBC, ECDSA (P-256/384/521) and a CTR-DRBG random number generator (#181).

inc_someip_gateway

• [Bug fix] Purely remote services no longer misclassified as having local instances (#309).
• [Bug fix] Deadlock and flaky test fixed; 100/100 runs passed after the fix (#316).

lifecycle

• [Change] Feature requirements clarified (#718); Launch Manager sequence diagrams extended (#741); verification report extended with traceability gap tables (#766).
• [Change] "fallback" renamed to "fallback_run_target" so logs match configuration names (#742); internal aborting/cancelled graph states merged (#748); steady clock used instead of processor time for timestamps (#764).
• [Tests] Integration tests for rejected and replaced Run Target activations (#733); unit tests for lifecycle client coverage (#758, #759); YAML line limit set to 120 (#760).

logging

• [Bug fix] Datarouter test configuration packaged at a stable path for root and external use (#351).

persistency

• [Change] C++ library reorganised (old targets deprecated, headers moved, tests moved) (#460, #461).
• [Change] A selected snapshot can now be loaded, or an empty store started (#464).
• [Change] Rust and test-scenario directory structure flattened (#471, #472, #474); index file updated to the module template (#468).
• [Bug fix] Switched to the copyright checker from tools (#476).

process_description

• [Change] Verification requirements updated to include architectural elements (#820).

reference_integration

• [New feature] Experimental Safety Relevance Assertion Capability (SRAC) sidecar proof of concept (#370).
• [Change] Logging integration tests re-enabled with datarouter packaging fix (#387); QNX images migrated to score_rules_imagefs 0.1.0 (#389); itf pinned to v0.6.0 (#391).

score

• [Change] Reference integration section added to the SW verification plan (#3313); Quality Management Plan review finalised (#3316).

time

• [Change] Component requirements for time_daemon added; detailed designs of time_slave and time_daemon migrated to doxygen (#153, #193, #194); docs-publish workflow added (#221).

Automated dependency updates: 6 merged (baselibs 2, inc_someip_gateway 3, reference_integration 1), plus GitHub Actions bumps in lifecycle (#763) and module_template (#194).

Issues

• bazel_cpp_toolchains: toolchain v1.0.4 incompatible with newer rules_cc (#160).
• communication: two new flaky-test reports (#1343, #1344).
• inc_someip_gateway, logging, persistency: validate and adopt the global toolchain configuration (#323, #353, #478).

17 issues opened, 24 closed.

S-CORE Daily is generated automatically from public eclipse-score activity for the window shown. Links go to the sources; corrections welcome as replies.

[dcalavrezo-qorix]

S-CORE Daily — 2026-10-11

Headline: Over the weekend of 9–11 October, S-CORE merged 33 pull requests across 16 repositories, with no new releases.

In plain terms

Over the weekend (9–11 October) S-CORE had no new releases, but 33 pull requests were merged across 16 repositories. Much of the work was documentation and process tidying: templates, checklists and spelling fixes, plus safety analyses for the communication module. The Time team's weekly meeting reported that its callbacks implementation is almost done, after a race condition was found and fixed. One crash fix landed in the SOME/IP gateway. Worth watching: the proposal to add more committers in Time, and a new issue about an S-CORE v1.0 release that follows the Eclipse Foundation process.

Window: 2026-10-09 → 2026-10-11 (covers more than one day).

From the meetings

Time FT — weekly 2026-10-09 (minutes, posted by @lavrovvalera)

• Decisions: "Proposal: currently to go with the easiest solution for the moment" (for the two-atomics design in the callbacks implementation; options discussed were one odd/even atomic counter or two buffers).
• Progress: callbacks implementation almost done; new unit test for shmemhandler; a race in the current implementation was found and fixed.
• Action items: none listed explicitly. Noted: the proposal to add more committers is ongoing, and "we need to make the reviews more often" (pattern: one +1 could be merged).
• Open questions: how to refactor the two atomics (single atomic, double buffering, cache-line layout needs more thought).

Discussions worth following

• S-CORE Daily (Show and tell) — the previous issue (2026-10-08) was posted as a new comment (link).

Code changes

.eclipsefdn

• [Change] Access to qnx_sdp_pkg limited to S-CORE committers, as it is used only by QNX verification gates in CI (#237).

bazel_cpp_toolchains

• [New feature] Support for the QNX io-pkt Driver Development Kit (network drivers) in the toolchain (#161).

coverage_tool

• [Change] End-to-end pytest set up with CI and requirement traceability (#33).
• [CI / automation] Shared copyright hook from tools replaces the local check (#34).

tools

• [New feature] synchronize_file for run-tool, so repositories can share a common launcher file (#54).

config_management

• [Change] Adopts the LLVM pipeline from score_tooling 2.2.1 (#72).

docs-as-code

• [Maintenance] Python dependency group bumped, 8 updates (#915).

communication

• [Change] Safety analyses (fault trees) added for several failure modes, e.g. longer-than-expected function blocks, too many sample pointers, unstopped find-service, incomplete event map, wrong returned size (#1132, #1289, #1313, #1320, #1327).

inc_someip_gateway

• [Bug fix] Fixes a possible crash (null pointer) in someipd caused by a race when creating a local service (#318).

lifecycle

• [Change] Component requirement headings moved, missing Baselibs dependencies added to Launch Manager, and a Launch Manager Rust macro added (#765, #769, #772).

persistency

• [Change] Component integration tests reorganised, with a follow-up target fix (#475, #486).
• [CI / automation] CI workflows bumped to address intermittent documentation deployment failures (#482).

time

• [Change] Coverage pipeline migrated to score_coverage 0.3.1 (#235); component requirement links fixed (#247).

module_template

• [Change] Architecture inspection checklist, templates and user-manual link cleaned up (#195, #196, #197, #198).

process_description

• [Change] Module user manual added to the release management process, plus formatting, spelling and link fixes (#821, #822, #823, #824, #825).

score

• [Change] Lifecycle glossary made more detailed, plus spelling and wording fixes (#3321, #3322, #3323).

Automated dependency updates: 17 merged (inc_security_crypto 3, inc_someip_gateway 1, logging 1, module_template 1, process_description 1, time 10).

Issues

• Eclipse Foundation process compliant S-Core release v1.0 — new.
• Clarification of QNX Tarball procedure — new.
• rust_kvs: flush() does not sync KVS and hash files to storage — new.
• JSON parser: nesting depth, hexadecimal numbers, \u escapes — new.
• Five new automated flaky-test reports in communication.

16 issues opened, 8 closed.

S-CORE Daily is generated automatically from public eclipse-score activity for the window shown. Links go to the sources; corrections welcome as replies.

[dcalavrezo-qorix]

S-CORE Daily — 2026-10-12

Headline

Coverage tooling reached v0.4.0, the persistency key-value store gained configurable limits, and the QNX SDP packaging repository got its first CI jobs.

In plain terms

A new release of the coverage tool (v0.4.0) is out, and it is already being used for on-target coverage on QNX in the base libraries. The persistency component (the key-value storage) now has compile-time size limits, a key-length rule and a configurable snapshot count, closing several open requirements. The communication component continued its safety documentation work and an internal rework. On the infrastructure side, QNX packaging and CI got attention, and the infrastructure and safety teams posted minutes covering open questions on classifications, umbrella targets and the November audit preparation.

Releases

• coverage_tool v0.4.0 — Coverage scope is now evaluated per platform; adds downstream coverage workflow tests, consolidated end-to-end tests with requirement traceability, pre-commit based formatting checks and clearer architecture docs. (release)

From the meetings

Infrastructure Community (minutes by @AlexanderLanin)

• Decisions: none recorded.
• Action items: DR for umbrella targets (docs: add DR-int standard umbrella targets for S-CORE modules #3324) to be discussed soon — "please read and provide feedback!"; QNX SDP package "in progress by @nradakovic".
• Open questions: "do all classifications now move to their respective repositories?" (process meeting tomorrow); "do we transform all existing tool classifications?"; "BUILD.bazel currently stilly unclear". Also noted: coverage per component update (docs-as-code#937).

SW Dev Process Community — Safety Team (minutes by @aschemmel-tech)

• Decisions: none recorded.
• Action items: preparing the audit agenda (work in progress) for Nov-04 (supporting processes), Nov-05 (development processes) and Nov-06 (supporting processes), with topic owners @aschemmel-tech, @masc2023, @RolandJentschETAS, @PandaeDo and @pahmann.
• Open questions: "Status, which modules shall be 'safe' for v1.0"; whether two items on "safety anomaly" shift to Problem Mgt; the "S-CORE AI concept" slot is still marked "?".

Discussions worth following

• Communication FT Weekly [2026-10-12] — new weekly thread for the Communication feature team, listing agenda items such as SOME/IP status. (discussion)

Code changes

baselibs

• [Change] QNX on-target coverage via the new coverage backend — enables coverage measurement on QNX hardware for C++ tests (#626)
• [Documentation] JSON parser backend choice removed; vaJson is now the only backend (#660)

cicd-workflows

• [New feature] Retry the QNX SDP download in a separate step to survive transient timeouts (#246)
• [Bug fix] Support matrix builds and nested workspaces when uploading QNX test logs (#248)

communication

• [Change] Deprecated GetSampleSize() API removed; use GetDataTypeSizeInfo().Size() — breaking for users of the old API (#997)
• [Change] Rework of shared-memory event storage size allocation (#1256)
• [Change] Safety analysis (FTA) additions for three failure modes, plus dependability cleanup (#1169, #1253, #1311, #1099)
• [Change] Documentation: shared-memory public API diagram, safety sentinel units, README improvements (#1354, #1363, #1364)

persistency

• [Change] Maximum KVS storage size configurable at compile time (#165)
• [New feature] Maximum key length of 32 bytes enforced in C++ (#308)
• [New feature] Maximum snapshot count now configurable (#383)

docs-as-code

• [New feature] Module verification reports use a dedicated need type (#933), then reverted to the "document" type per the process plan, with an optional belongs_to link to follow (#941)

qnx_sdp_pkg

• [Change] Initial release targets and CI jobs for the QNX SDP package, plus a credentials fix (#1, #2)

Other repositories

• .eclipsefdn: bypass actors added (#238)
• config_management: QNX build enabled (#74)
• coverage_tool: 0.4.0 release date set (#35)
• lifecycle: feature architecture content restructured by functionality (#768)
• module_template: score-qnx-aarch64 added (#199)
• process_description: change impact tooling corrections (#827)
• score: design decision include path added (#3196)
• tooling: Rust crate versions pinned (#515); merge-queue CI trigger fixed (#516)

Automated dependency updates: 11 merged across 9 repositories.

Issues

• Several toolchain update trackers opened in score: Bazel 8.7.0/9.x, rules_cc, rules_python, aspect_rules_py (#3330, #3331, #3328, #3329, #3332).
• Persistency: boolean values stored as 0/1 (#495).
• Flaky test reported in communication (#1361).

18 issues opened, 8 closed.

---

S-CORE Daily is generated automatically from public eclipse-score activity for the window shown. Links go to the sources; corrections welcome as replies.

[dcalavrezo-qorix]

S-CORE Daily — 2026-10-13

Headline

Four releases landed (coverage tool, docs-as-code, and two devcontainer patch releases), and the SOME/IP gateway moved to an IPC binding built on top of the communication framework.

In plain terms

Several tooling releases shipped: a fix so the coverage tool no longer produces empty reports for some libraries, a docs-as-code release with metamodel and compatibility changes, and two devcontainer (the shared development environment) patch releases. The first devcontainer release, 1.11.1, had to be replaced after a rebuild changed its checksum, so repositories were moved to 1.11.2. The SOME/IP gateway incubation repository merged a large change that reuses the communication framework (mw::com) for its internal messaging. Community meetings covered the release workflow (DR8), dashboards and the Security & Crypto status. Watch for follow-up work on the gateway and for module owners fixing failing checks ahead of the new workflow.

Releases

• coverage_tool v0.4.1 — Measuring system headers no longer empties the report; the reporter now understands file names printed relative to the root. (release)
• devcontainer v1.11.1 — Updated bundled tools (apm, opencode) and simplified running tools outside the container. Superseded by v1.11.2 (see below). (release)
• devcontainer v1.11.2 — Re-release after a build failure; the re-created 1.11.1 no longer matched the checksum stored in the Bazel registry. (release)
• docs-as-code v8.4.0 — external_needs accepts public docs targets; metamodel updates (valid_inspected status, invalid needs bypass checks, new info-only check on dfa/fmea). Compatibility change: root_cause renamed to failure_root_cause in feat_fmea and comp_fmea; the score_pytest macro and test attributes plugin were removed in favour of score_tools. (release)

From the meetings

Release Community (minutes by @PiotrKorkus) — 13.10.2026

• Decisions: "We will keep the dashboards splitted, as reference_integration one is linked to the PR / release changes from ref_int." Dashboard data from reference_integration will be moved there; an entry point for all dashboards is to be created in the central repo, and the S-CORE webpage should link to them.
• Action items: @PiotrKorkus will prepare a PR in reference_integration for the DR8 workflow; module owners to prepare fixes / requests for workarounds (failing: communication, lifecycle, config management); Piotr to contact Leonardo about AutoSD failures on main.
• Open questions: combined documentation from reference_integration should also be packed as a zip and added to release assets (download options were discussed).

SW Dev Process Community (minutes by @masc2023) — meeting Oct-15

• Agenda: docs-as-code PR 943 in relation to the decision record template. No decisions or action items recorded yet.

Security & Crypto FT (minutes by @sunildevda)

• Agenda: participant check, PRs closed since last meeting, status of ongoing PRs. No decisions or action items recorded.

Discussions worth following

• Logging CFT Weekly 2026-10-13 — new weekly notes; bot-generated policy-sync PRs should be picked up in daily work.
• CMake-based pub/sub example using score::mw::com — a maintainer replied there is no capacity to additionally support CMake (comment).

Code changes

bazel_registry

• [Breaking change] yank devcontainer 1.11.1 — checksum no longer matches after re-release (#529).

inc_someip_gateway

• [Breaking change] IPC binding on top of mw::com — reduces code and inherits safety properties from the communication framework (#291); communication bumped to 0.5.0 (#338).

Documentation and process

• docs-as-code: [New feature] module verification reports use the dedicated mod_ver_report type again (#944); info-only check for saf_attrs_mitigated_by (#936); score_devcontainer marked as dev dependency (#951).
• score: [Documentation] decision record DR-011 on AI agent context packaging tooling (#3188); [Change] draft decision record proposing DDS communication support beneath mw::com (#3263).
• .github: [Change] link to code of conduct (#122).

Infrastructure and tooling

• cicd-workflows: [New feature] published docs link shown in the Actions UI (#230).
• coverage_tool: [Change] reporter reads root-relative llvm-cov names (#36); release notes dated (#37).
• devcontainer: [Bug fix] re-release after build failure (#168).
• tooling: [Change] PlantUML parser supports free functions in class diagrams (#511) and has an optimized class AST/parser (#517).

Modules

• communication: [Change] SOME/IP diagram added (#1374).
• config_management: [Maintenance] dummy change to validate QNX CI (#75).
• inc_security_crypto: [New feature] multi-slot support, faster initialization and token initialization improvements (#276); [Bug fix] moved to released devcontainer 1.11.2 (#285).
• lifecycle: [Change] unit tests for report_running_impl.cpp reaching full coverage (#757); Launch Manager performance design decisions (#771); [Bug fix] recovery action reported from recovery rather than by name (#773).
• persistency: [Change] safety plan updated (#483); [CI] docs workflow split into build and publish (#499); [Formatting] _ suffix for non-public fields (#501).
• time: [Change] VehicleClock callbacks delivered from a worker thread (#215).

Automated updates: 16 dependency bumps merged, plus policy-sync PRs moving repositories (docs-as-code, inc_someip_gateway, infrastructure, lifecycle, module_template, score) to devcontainer 1.11.2 (example).

Issues

• Highlighted: score_devcontainer 1.11.1 archive checksum no longer matches the registry; Flaky test in communication; DDS gateway closed.
• 22 opened, 4 closed.

---

S-CORE Daily is generated automatically from public eclipse-score activity for the window shown. Links go to the sources; corrections welcome as replies.

[dcalavrezo-qorix]

S-CORE Daily — 2026-10-14

Headline

Two releases landed — baselibs v0.2.15 (JSON parser consolidated, with breaking changes) and tooling v3.0.0 (safety-analysis rules reorganized) — alongside 29 merged pull requests across 18 repositories.

In plain terms

Two shared building blocks were released with breaking changes: the base C++ libraries now use a single JSON parser, and the documentation/safety tooling split its safety-analysis rules into three parts. Projects that build on either should review the release notes before upgrading. Four teams posted meeting minutes; the Base Libs team is looking at what can be achieved before a safety audit in about three weeks, and the Tech Lead circle discussed combining the 2026 progress review and the v1.0 release review. A discussion on using the communication middleware on C-only RTOS hardware was reopened. Persistency and lifecycle documentation and tests saw steady progress.

Releases

• baselibs v0.2.15 — Breaking change: score/json now uses vaJson as its only parser; the nlohmann parser was removed. The --//score/json:base_library flag is a deprecated no-op and should be removed from build configurations. Not intended for production use (no completed safety assessment). (release)
• tooling v3.0.0 — Breaking changes: rules_score splits safety analysis into failure_modes, fault_trees and safety_analysis, with renamed attributes; a dependable element now derives its own assumptions of use from the safety analysis. PlantUML tooling takes identifiers from written names, and a new check compares free functions in class diagrams with C++ code. (release)

From the meetings

Technical Lead Circle — Tech Lead Sync (minutes, by @antonkri)

• Decisions: none recorded in the briefing excerpt.
• Action items: none recorded in the briefing excerpt.
• Open questions: "EMO proposes to put 2026 Progress Review and Release Review for S-Core v1.0 together, as there are no any differences between Progress and Release review. Do we agree?"

Infrastructure Community — Weekly Rust (minutes, by @dcalavrezo-qorix)

• Decisions: none recorded.
• Action items: none recorded.
• Open questions: the Rust coding guidelines PR (score#3262) is still open. A Ferrocene version issue was clarified.

Base Libs FT — Weekly (minutes, by @4og)

• Decisions: none recorded.
• Action items: "@4og to add @fscr to S-CORE Contributors"; @pahmann was nominated by the S-CORE Process community to look at non-functional requirements shown as not covered in the verification report (process_description#813).
• Open questions: what can be achieved before the safety audit in 3 weeks, including feature architecture inspection fixes (baselibs#188); a devcontainer issue was discussed on Slack.

Lifecycle FT (reply, by @MaciejKaszynski)

• A simplified recovery-actions diagram for v1 was shared.

Discussions worth following

• LoLa / mw::com support for C and Classic AUTOSAR — the request is about running the communication middleware on RTOS hardware without C++; @crimson11 reopened the discussion, noting there is currently official support only for C++/Rust bindings. (comment, comment)
• Interest Group: HW Accelerators/AI — weekly notes; agenda item on where to locate AutoSD skills. (comment)
• Infrastructure/Process Workshop "Docs-As-Code" — workshop participants and minutes posted by @anmittag. (participants, minutes)

Code changes

.eclipsefdn

• [Change] Unarchive and rename the AI platform repository to start work on the AI platform feature (#240)

baselibs

• [Documentation] Requirement inspection updates and a switch to a valid_inspected status across components (#678, #688)

cicd-workflows

• [Change] Newer action versions with hash pinning for supply-chain safety (#251)

communication

• [Change] Safety-analysis updates: new fault trees and documentation moved to match the new high-level architecture (#1297, #1362, #1366, #1367)
• [Change] Fewer compiler warnings (#1372)
• [Change] Newer docs tooling forced to work around a broken devcontainer release (#1379)

config_management

• [Maintenance] Dummy change to check QNX secret debug logs (#77)

coverage_tool

• [Change] Coverage summary checks migrated to pytest, making them traceable to requirements (#38)

docs-as-code

• [Change] Updated recommended chart color palette (#954)

inc_someip_gateway / rules_imagefs

• [Bug fix] Image builds now support directories, removing a workaround for listing libraries (gateway#326, rules_imagefs#29)

lifecycle

• [Change] Launch Manager now waits, with a timeout, for processes configured to end in a terminated state (#738)
• [Change] Glossary split into detailed and feature level (#761)
• [Change] New unit tests, reaching 100% coverage for one file (#767); build fix adopted from baselibs (#790)

module_template

• [Maintenance] Devcontainer bumped to v1.11.2 (#204)

persistency

• [Change] Rust client can load a selected snapshot or start an empty store (#484)
• [Change] First user manual, plus safety manual and security document updates (#485, #491, #492)

score_cpp_policies

• [Bug fix] A compiler warning is now applied to C code only (#46)

tooling

• [Change] Free-function validation between PlantUML and C++ (#518); views can be split into overview and detail files (#521); fixes for a missing toctree document and duplicate transitive dependencies (#519, #522)

Automated dependency updates: 9 merged (cicd-actions 1, inc_security_crypto 2, inc_someip_gateway 1, lifecycle 2, logging 2, reference_integration 1).

Issues

• baselibs — a set of follow-ups after the JSON parser consolidation: compatibility checks, documentation refresh and ASIL-B claim definition (#680–#684).
• lifecycle — bug: synchronisation of wait() and kill() (#792).
• score — feature request: System Monitoring (SMon) middleware (#3340).
• infrastructure — requirement updates after the Docs-As-Code workshop (#69).

22 issues opened, 3 closed.

S-CORE Daily is generated automatically from public eclipse-score activity for the window shown. Links go to the sources; corrections welcome as replies.

[dcalavrezo-qorix]

S-CORE Daily — 2026-10-15

Headline

The first mcp-servers release (v0.1.0) shipped, five community meetings posted minutes, and 43 pull requests were merged across 21 repositories.

In plain terms

A new module, mcp-servers, published its first release; it provides the scaffold and data schema for an "Agent Context Attention Layer" (tooling that gives AI assistants focused project context). Work continued on core building blocks: the JSON library in baselibs was simplified to a single writer, and lifecycle (start-up and shutdown handling of software) saw cleanups and test-coverage gains. One change in the SOME/IP gateway alters how message payloads are accessed and is marked breaking. Several communities planned upcoming topics, such as downloadable images for S-CORE v1.0 and how to present the AI concept in the audit.

Releases

• mcp-servers v0.1.0 — first release: monorepo scaffold and Phase 0 schema for the Agent Context Attention Layer, plus routine dependency bumps. (release)

From the meetings

Persistency FT (minutes, by @umaucher)

• Decisions / notes:
  • IDE support: "We can have a config suggestions but could not enforce it" (comment).
  • Component requirements: "in general keep PR's simple and only fix / implement one thing"; split the score_platform v0.7.3 integration from new component requirements, with any contentious new requirements possibly in a third PR.
  • Key handling for the key-value store is referenced in persistency#504.
• Action items: none listed.
• Open questions: none listed.

Technical Lead Circle — Tech Lead Sync (minutes, by @antonkri; agenda for 2026-10-19)

• Decisions: none recorded.
• Agenda / open questions: downloadable images for S-Core v1.0 (AutoSD and EB images "would be great"; QNX "probably will not allow" a downloadable image for everyone → "check"); showcase of the S-Core process end-to-end (candidates: persistency, components from baselibs; "Clarify with module responsibles and set-up tracking").

Architecture Community (minutes, by @arsibo; 2026-10-19)

• Agenda: @mina-hamdi on score#3333; @sunildevda on migrating hashing support from Baselib to Security Crypto.
• No decisions or action items recorded.

Testing Community (TST) (minutes, by @antonkri; 21.10.2026)

• Agenda: further development and maintenance of ITF (integration test framework). Participant: @PiotrKorkus. No decisions recorded.

SW Dev Process Community (minutes, by @aschemmel-tech; Oct-22)

• Agenda: how to present the AI concept in the audit, with information currently spread across score#3188, process_description#805, score#3260 and score#3307.

Discussions worth following

• S-CORE Daily (Show and tell) — received the previous issue (2026-10-14) as a new comment (link). No new discussions were opened.

Code changes

Breaking changes

inc_someip_gateway

• [Breaking change] Payload as a read-only view of the full SOME/IP message — the gateway now always exposes the complete message instead of a separate header accessor (#342)

Platform and modules

baselibs

• [Change] JSON writer simplified: only the vaJson writer remains and the old json_serialize writer is removed (#675); related compiler-warning fixes (#690, #693); QNX workflow update (#676)

communication

• [Change] Feature requirements for mw::com adapted (#1090); new assumption of use forbidding moving of service element members (#1385)
• [Change] Dependencies upgraded (baselibs 0.2.15, ITF 0.6.0, newer toolchain rules) with stricter host warnings (#1386); single toolchain-builder version enforced (#1370); CI link fix (#1390)

config_management

• [Bug fix] devcontainer pinned to 1.11.2 because 1.11.1 was yanked upstream (#81)

inc_security_crypto

• [Change] Proofs of concept and design decision for IPC selection added (#169)

inc_someip_gateway

• [Bug fix] someipd now shuts down on SIGTERM/SIGINT instead of hanging (#350); possible fix for a CI-only flaky test (#341)

lifecycle

• [Change] OS handler ignores stop/continue signals and logs the real termination reason (#786); IPC code moved so it appears in coverage (#787); ControlProvider refactored to 100% coverage (#789); documentation diagrams (#795, #798)

persistency

• [Bug fix] Key-value store and hash files are synced to storage on flush, avoiding data loss or hash mismatch after power loss (#489)

Tooling and infrastructure

docs-as-code

• [New feature] Verification report pie charts split into ASIL and QM (#946)
• [Change] New valid_from attribute with version validation in the metamodel (#956); invalid requirement references removed (#966); metadata annotation tests (#973)

tooling

• [Change] component() accepts assumed system requirements (#523); skills sync gains repo_skills_target (#524); units rendered in separate directories (#526)

cicd-actions

• [Bug fix] Cache step summaries are now opt-in (#49)
• [New feature] Stale token rewrites removed before new ones are added (#54)

cicd-workflows

• [Change] Renovate enabled for the openssl repository (#254)

sbom-tool

• [Bug fix] Multiple package versions preserved in SBOM output (#19)

rules_rust

• [Bug fix] Backport fixing -imacros path handling in cargo build scripts (#23)

qnx_sdp

• [Change] Improvements and fixes for QNX SDP generation (#3)

mcp-servers

• [Change] Server sources pinned to the v0.1.0 tag and graphify to 0.9.53 (#44)

ai_platform

• [Change] Synced with the current module template (#1)

Process and organization

process_description

• [Change] Security Management Getting Started page title and list rendering fixed (#831)

.github

• [Change] Profile README refreshed automatically (#117)

Automated dependency updates: 14 merged (ai_platform 4, cicd-actions 2, cicd-workflows 1, devcontainer 1, inc_security_crypto 3, inc_someip_gateway 1, lifecycle 1, logging 1).

Issues

• cicd-actions: setup-bazel-cache tests fail on main (bug)
• communication: two flaky tests reported (#1388, #1389)
• mcp-servers: bug report #45
• lifecycle: process exit codes logged incorrectly closed
• score: Release v0.8 tracking issue closed

18 issues opened, 21 closed.

---

S-CORE Daily is generated automatically from public eclipse-score activity for the window shown. Links go to the sources; corrections welcome as replies.

[dcalavrezo-qorix]

S-CORE Daily — 2026-10-18

Headline

Over the weekend window (16–18 October), process_description v2.2.0 was released and 52 pull requests were merged across 26 repositories, many of them adding legal files and cleaning up compiler warnings.

In plain terms

This issue covers three days (Friday 16 to Sunday 18 October). The process description, which defines how S-CORE teams work, got a new release (v2.2.0), and the documentation tooling was updated to follow it. Many repositories received the standard LICENSE and NOTICE files that the Eclipse Foundation requires, and the communication module saw a large round of code-quality fixes. The Time team's weekly meeting recorded follow-ups on committers, testing and release reporting. Worth watching: further work on SBOMs (the software bill of materials, i.e. a list of what software is inside a product) and on code-coverage reporting.

Releases

• process_description v2.2.0 — adds workpackages to tool requirements, updates the implementation process requirement, fixes a missing "satisfies" link, and picks up docs-as-code updates up to v8.2.0. No breaking or pre-release flag. (release)

From the meetings

Time FT — weekly of 2026-10-16 (minutes)

• Decisions
  • "Callback implementation is merged."
  • "the merge queue is a benfitial" (beneficial) — also for committers merging changes.
  • SW requirements review: "Propose: to finish the feature resq and then come back to SW reqs."
• Action items
  • @BjoernAtBosch: create a ticket to cross-check whether the data passed from TimeSlave to TimeDaemon needs extending (safe and non-safe data validation).
  • @lavrovvalera: create tickets for the merge queue, for moving the SW requirements review to a different PI, for checking migration to Ubuntu 26, for module verification reports via Sphinx-needs, for a module KPI board (requirements and code coverage), and to check or create a ticket for a module release process.
• Open questions
  • Ubuntu 26: can configuration be centralized within the module, or is "latest-greatest" simpler (noting it may cause unexpected issues)?
  • How to store reports for releases; whether the reference integration solves this.
  • Also noted: TimeDaemon integration into a vendor-specific project is ongoing; @BjoernAtBosch is away until 26 October.

Follow-up by @gordon9901: integration test status update — TimeDaemon component integration test PR submitted (time#122) with major review comments addressed; two further PRs prepared. (comment)

Code changes

.eclipsefdn

• [Change] Dedicated maintainers team for the private QNX SDP package repository (#241)

.github

• [Change] Bug report template gets a notification field, following audit findings (#126)

baselibs

• [Change] Fix sign-conversion warning in argument handling, closing a long-open issue (#695)
• [Change] Fix formatter script and task name; allow fork checkout in the QNX coverage workflow (gated by approval) (#691, #692)
• [Documentation] Safety plan status report corrected (#701)

communication

• [Bug fix] Static-analysis cleanups (cognitive complexity, pointer arithmetic, MISRA C++ rules, a clang-tidy alert), behaviour unchanged (#1331, #1347, #1352, #1353, #1408)
• [Bug fix] Two small fixes so the CodeQL scanner and compilers accept the code (#1395, #1402)
• [Change] Compiler warning cleanups, clang warnings now treated as errors, Ferrocene toolchain builder 1.3.1 (#1373, #1394, #1396, #1399)
• [Change] Failure mode analysis for code and configuration getting out of sync (#1143)

config_management

• [Change] Removed a temporary QNX secret-debug job (#82)

coverage_tool

• [Change] An executable's own sources are now included in coverage, so untested binaries show up as zero coverage (#44)

docs-as-code

• [New feature] Safety-to-requirement link check (info only); source links respect component boundaries; configurable docs build directory (#874, #958, #974)
• [Documentation] Revised test-link requirements (#967)
• [Maintenance] Moved to process_description 2.2.0 (#977)

lifecycle

• [Change] New unit tests reaching full coverage for the lifecycle manager; a shadowed-variable warning fixed (#777, #803)

logging

• [Change] Migration to the non-deprecated struct-visitable macro; dependable element for mw_log; Rust toolchain fix; codeowners update (#343, #350, #361, #364)

module_template

• [Change] Moved to "valid_inspected" state (#206)

persistency

• [Change] C++ keys are now validated (non-empty, printable ASCII) with a new InvalidKey error replacing KeyTooLong — may affect callers using other keys (#508)
• [Change] Updated component requirements; dependency paths follow the testing_tools relocation (#443, #512)

process_description

• [Change] Problem resolution process clarified to close audit findings (#832)

qnx_sdp

• [New feature] Reworked QNX credential helper (URL validation, environment or .netrc credentials) (#5)

sbom-tool

• [Bug fix] Package checksums now come from the downloaded archives, not registry metadata (#17)
• [New feature] SPDX output includes package-to-package dependency relationships (#22)

score

• [Change] Verification plan updated to match the process description and docs-as-code (#3344)

Legal files (LICENSE / NOTICE)

• [Maintenance] Added or completed for the Eclipse Foundation handbook in cicd-actions (#55), dash-license-scan (#11), dev_playground (#2), eclipse-score-website-preview (#1), infrastructure (#70), openssl (#2), os_images (#40), rules_imagefs (#30), sbom-tool (#23), score_rust_policies (#20)

Automated dependency updates: 2 merged (ai_platform 1, inc_security_crypto 1).

Issues

• persistency: Separate JSON and hash file operations are inevitably not atomic — new design concern.
• sbom-tool: Handle declared and concluded licenses independently
• coverage_tool: main function missing in coverage report — bug, opened and closed in this window.
• inc_someip_gateway: someipd: withdraw the offer while the remote service is unavailable

15 issues opened, 10 closed.

S-CORE Daily is generated automatically from public eclipse-score activity for the window shown. Links go to the sources; corrections welcome as replies.

[dcalavrezo-qorix]

S-CORE Daily — 2026-10-19

Headline

Three releases (coverage_tool, process_description, tooling) and 45 merged pull requests across 18 repositories on 19 October, with a breaking documentation-layout change in tooling v3.0.1.

In plain terms

Monday brought three releases: a coverage-reporting fix, a process-description update responding to audit findings, and a tooling release that changes how unit documentation is laid out (a breaking change for anyone building documentation with it). Much of the code activity was tidying: compiler-warning clean-ups, legal NOTICE files, and removal of deprecated names. Four meeting minutes were posted; the Infrastructure community discussed standardizing code-scanning rule sets, pending agreement on C++ coding guidelines. The Technical Lead Circle covered downloadable images and an end-to-end process showcase for S-CORE v1.0.

Releases

• tooling v3.0.1 — Breaking: unit pages now render to units/<unit>/index.rst with design files in units/<unit>/design/; duplicate unit names in one element and file collisions now fail the build. Also adds a .devcontainer/run-tool launcher and lets component requirements derive from assumed system requirements. (release)
• process_description v2.2.1 — Two fixes addressing audit findings (quality management and change management). (release)
• coverage_tool v0.4.2 — The sources of an executable (cc_binary) now appear at 0 % coverage instead of being missing from the report; coverage summary checks moved to pytest. (release)

From the meetings

Technical Lead Circle (minutes, by @FScholPer)

• Decisions: none recorded.
• Action items: Vanilla Pi image — @FScholPer; demo showcase — @antonkri; persistency status at Thursday's TL meeting — @PandaeDo; baselibs components status — @aschemmel-tech; ask about AutoSD and EB downloadable images — @opajonk and @ondra.
• Open questions: downloadable images for S-Core v1.0 (QNX probably cannot offer a public image — "check"); which modules show the process end-to-end; feedback on the Verification report; Alignment Board reviewed every second week.

Infrastructure Community (minutes, by @dcalavrezo-qorix)

• Decisions: none formal. Minutes: "we need an agreement on C++ coding guidelines - afterwards we can decide on transposing those into tools"; a new team was created for the qnx_sdp maintainers.
• Action items: follow up on score PR docs: propose portable safety traceability and SBOM exchange #3318 — to be presented in the TAM from tomorrow.
• Open questions: proposed common CodeQL baseline (code scanning, CERT C++ L1, MISRA C++ mandatory/required, a custom design-complexity suite); slow job execution observed in some repos.

SW Dev Process Community – Safety Team (minutes, by @aschemmel-tech)

• Agenda for the 20 October meeting: score PR Use valid_inspected state in reqs #3341 and process_description issue Logging CFT Weekly [2025-03-04] #556 (Action_70).

Base Libs FT (minutes, by @4og)

• No meeting on 2026-10-21.

Discussions worth following

• Communication FT Weekly [2026-10-19] — new weekly thread with status on SOME/IP, Flatbuffers, Rust API, Methods & Fields and CI. (discussion)
• S-CORE Fortnightly and S-CORE Daily — the previous digests were posted. (Fortnightly, Daily)

Code changes

baselibs

• [Change] Removed deprecated C++ macro aliases (STRUCT_VISITABLE, MEMCPY_SERIALIZABLE, etc.); new code must use the SCORE_ names (#623).
• [Change] Untested-file coverage notes built unoptimised for consistent line data (#704).
• [New feature] CI check, format and lockfile workflows migrated to the new implementation (#708).

cicd-workflows

• [Change] Callers can configure Bazel PR-check targets (#255).

communication

• [Change] Failure mode linked to a new component requirement; safety-sentinel event docs split into Proxy/Skeleton (#1349, #1393).
• [Build/Docs] Removed a no-op JSON option; fixed a sandbox script path in CONTRIBUTING (#1411, #1412).

coverage_tool

• [Documentation] Release notes dated for 0.4.2 (#45).

docs-as-code

• [Change] Verification metrics centralized as an add-on (#949); [New feature] larger pie charts in verification reports (#979).

inc_ecu_model

• [Change] Franca preprocessing added and Franca/Protobuf parsers adapted (#30, #32).
• [Maintenance] NOTICE file added (#31); same for bazel_registry_ui (#19).

inc_someip_gateway

• [Tests] Config path for the gateway IPC test is now configurable (#345).
• [Documentation] Clearer startup/event sequence diagrams (#346).
• [Refactoring] Final_action replaced by baselibs ScopeExit (#355).

lifecycle

• [Bug fix] Heap allocation removed from process-group getters/setters (#699).
• [Change] Recovery-action requirements reworded (#774); requirement state changed to valid_inspected (#806).
• [Change] Compiler warning fixes (#802, #816); watchdog fd no longer inherited and move-constructor members fixed (#809, #810).
• [Change] score_coverage bumped to 0.4.2 (#804).

mcp-servers

• [Change] Release pipeline added; MCP sources pinned to commit SHAs (#46).

persistency

• [Change] Rust keys must now be non-empty printable ASCII; new InvalidKey error replaces KeyTooLong (#509).

process_description

• [Change] Audit-finding fixes for change management and quality management (#834, #835); valid_inspected state (#836).

reference_integration

• [Bug fix] Newer AutoSD OCI image (#404).

score

• [Change] Baselibs OSAL feature requirement added (#3293); change-management and quality-management plan alignment with audit findings (#3347, #3348).
• [Documentation] Tool mapping for a removed requirement dropped (#3345).

score_cpp_policies

• [Change] Compiler-warning policy adjustments (#47, #49).

tooling

• [Change] Fixes to the rst-to-trlc parser (#464); PlantUML component-diagram parser guide (#525).

Automated dependency updates: 8 merged (baselibs 1, docs-as-code 1, inc_someip_gateway 2, persistency 1, tooling 3).

Issues

• Feature request: external read-only telemetry and lifecycle observation over mw::com
• Re-perform the Baselibs feature DFA for the OSAL architecture
• Flaky test in communication (flaky-test)

19 issues opened, 11 closed.

---

S-CORE Daily is generated automatically from public eclipse-score activity for the window shown. Links go to the sources; corrections welcome as replies.

[dcalavrezo-qorix]

S-CORE Daily — 2026-10-20

Headline

A first pre-release of the QNX SDP package landed, and 26 pull requests merged across 11 repositories, with documentation-tooling fixes and build-warning cleanups leading the day.

In plain terms

A new repository, qnx_sdp_pkg, published its first pre-release (v0.0.1-rc1); it packages the QNX software development platform for use in S-CORE builds. Several modules (baselibs, persistency, lifecycle, communication) tightened their code quality and continuous-integration set-up, and the documentation tooling received fixes that unblock modules adopting a new "module verification report" format. Three community meetings posted minutes, including the Release Community's decisions on release image artifacts and on when warnings become build errors. Worth watching: the plan to treat warnings as errors in the reference integration is deferred until S-CORE v1.0.

Releases

• qnx_sdp_pkg v0.0.1-rc1 — pre-release. First release: initial release targets and CI jobs, a credentials fix, build verification for the QNX SDP, and a corrected license file in the release workflow.

From the meetings

Release Community — minutes by @PiotrKorkus

• Decisions:
  • Image artifact in ref_int: "Rolling release created nightly if there are changes merged to main and mandatory image on release attached to the assets."
  • Warnings as errors: "Will not be enabled until SCORE v1.0, Modules need to fix the warning in their repos first, then once we have stable builds this option can be enabled in ref_int."
• Action items: DR8 workflow failing for communication and config management — "@antonkri will contact the teams".
• Open questions: none recorded. A dashboards update (multiple views of dependency versions across repositories and reference integration) was presented.

Security & Crypto FT — minutes by @sunildevda

• Agenda for the 21 Oct meeting: check participants, closed and ongoing PRs (issue 261 → @prabakaranklst), and the migration of the hashing feature from Baselibs to Security Crypto. No decisions or actions recorded yet.

SW Dev Process Community – Safety Team — minutes by @aschemmel-tech

• Agenda for 27 Oct: discuss score PR 3341. No decisions or actions recorded yet.

Discussions worth following

• Logging CFT Weekly [2026-10-20] — new weekly notes from the Logging feature team, including a reminder to act on bot-generated policy-sync PRs.
• S-CORE Daily — the 2026-10-19 edition was posted (comment).

Code changes

baselibs

• [Documentation] Module verification report moves to the dedicated mod_ver_report need type, pinned to docs-as-code main (#672).
• [Change] Fixes a missing-braces compile error under strict warnings (#707).
• [Bug fix / Change] QNX coverage workflow cache key fixed so caches restore and save again; CI actions re-pinned (#709, #715).
• [Change] Docs workflows migrated to the shared docs.yml workflow (#713).

cicd-workflows

• [Change] Daily workflow gets an opt-out for automatic stale-PR handling; existing callers unaffected (#257).

communication

• [Change] Baselib warnings are now treated as errors and toolchain warnings improved (#1401, #1403).
• [Change] Declares the dependable element for memory/shared, the first step of the S-CORE tutorial (#1414).

docs-as-code

• [Bug fix] Fixes a docs build crash caused by resolving links before needs are frozen (#982).
• [Bug fix] Link check no longer fails on responses like 403 Forbidden (#980).
• [Bug fix] Adds a feature-requirement option to metrics generation (#978).

inc_someip_gateway

• [Tests] Adds Service Discovery conformance tests, part of the TC8 test series (#320).

lifecycle

• [Change] Uses baselibs' monotonic semaphore wait instead of polling, to reduce CPU load (#811); reuses FNV-1a hash from baselibs (#807).
• [Change] Launch Manager no longer leaks supplementary group IDs to child processes (#825).
• [Change] CI: link check step added and a runner-uid fix (#819, #824).

persistency

• [Change] C++ implementation marked noexcept and the single-point-of-return rule dropped, allowing simpler functions (#533, #535).
• [Documentation] Module verification report migrated to mod_ver_report (#537).
• [CI / automation] Shared workflows bumped, actions pinned (#524).

qnx_sdp_pkg

• [Change / Bug fix] Build verification for the QNX SDP and corrected license file in the release workflow (#3, #5).

score

• [Change] Descriptions added to Launch Manager architecture elements following architecture-inspection feedback (#3317).
• [Change] Fills the open "tbd" items in the platform safety manual (#3352).

Automated dependency updates: 4 merged (inc_security_crypto 3, logging 1).

Issues

• baselibs: hash: Retire SHA-1 support
• baselibs: Semaphore::sem_timedwait_monotonic() is hard to use
• time: Require a merge queue with blocking merge-result CI validation

14 issues opened, 6 closed.

---

S-CORE Daily is generated automatically from public eclipse-score activity for the window shown. Links go to the sources; corrections welcome as replies.

[dcalavrezo-qorix]

S-CORE Daily — 2026-10-21

Headline

Two releases (docs-as-code v8.5.0 and score_cpp_policies v0.1.2) shipped, and 31 pull requests merged across 18 repositories, led by compiler-warning cleanups and persistency hardening.

In plain terms

The documentation tooling gained a new release that adds more precise links between bundles and code, and starts showing hints when safety levels of linked items don't line up. The shared C++ warning rules also had a new release, and several modules (lifecycle, persistency, communication) are already adopting them and fixing the issues those stricter rules uncover. The persistency module now writes stored files more safely (atomically, with restricted permissions). Worth watching: the safety-link hint in the docs tooling may become a hard error in the future.

Releases

• docs-as-code v8.5.0 — bundles get a code_targets attribute; the build now shows an informational hint when an item has no link to a requirement with the same safety value (not yet an error; follow-up tracked in issue Improvement: Testing of metamodel loading / parsing #985); updated to process_description 2.2.0 (marked as a compatibility change); fixes for a premature needs freeze, link checking, metrics and pie charts. (release)
• score_cpp_policies v0.1.2 — sanitizer migration docs, a type sanitizer, and corrections to compiler-warning sets (C-only warnings no longer applied to C++, -Wuseless-cast removed from all). Two first-time contributors. (release)

From the meetings

Infrastructure Community — Weekly Rust (2026-10-21) (minutes)

• Decisions: none recorded.
• Action items: none recorded.
• Open questions: new comments on the Rust coding guidelines PR are still open (PR 3262). Participants: @dcalavrezo-qorix, @PLeVasseur.

Security & Crypto FT — a follow-up reply by @christianbe9 containing only a screenshot; no text minutes. (comment)

Discussions worth following

• Interest Group: HW Accelerators/AI — weekly notes posted by @FScholPer; agenda was planning next steps for an MCP server, with a draft GUI for graph exploration mentioned. (comment)
• S-CORE Daily — the previous edition (2026-10-20) was synced to the discussion. (comment)

Code changes

Infrastructure and tooling

.eclipsefdn

• [Change] Merge queue enabled for the Time repository, following the squash-merge approach of Lifecycle and Persistency (#242)

bazel_cpp_toolchains

• [Change] New type attribute for SDP downloads whose URL has no file extension, so the archive is extracted correctly (#163)

cicd-workflows

• [Change] Opt-in require-bzlmod-lock input fails the PR check when the lockfile is missing instead of silently skipping (#258)

time

• [Change] Docs and quality-pack publishing fixed for branches from renamed forks (#258)

reference_integration

• [Bug fix] Fixed libclang toolchain API and bumped a pin (#406)

Modules

communication

• [Change] Configuration can now be parsed from a FlatBuffers binary (#1270)
• [Bug fix] Remaining buildifier findings resolved (#1275); compiler warnings cleaned up (#1415)
• [Documentation] Shared-memory overview corrected after review (#1419)

lifecycle

• [Change] Warning cleanups aligned with the new policy set: designated initializers removed, sign-conversion fixes, and an off-by-one buffer bug fixed in signal_safe_log (#818, #832, #833, #837)
• [Change] Alive shared memory now opened exclusively, closing a theoretical security gap (#822); safer hash-map insertion (#836)
• [Change] Health monitor docs structure aligned (#834)
• [Documentation] Module verification report migrated to the new mod_ver_report type (#820)

logging

• [Documentation] Module verification report migrated to the mod_ver_report type (#367)

persistency

• [Change] Stored files get 640 permissions and atomic writes (temp file, sync, rename) (#503)
• [Build] Build configs split and renamed; score_cpp_policies adopted with C++ warnings as errors (#525, #531)
• [Change] Code-quality and comment-style cleanups (#529, #558)
• [Change] Safety plan and user manual entries updated/fixed (#548, #549)

config_management

• [Bug fix] Missing include added in a test (#85)

Incubation and tools

inc_ecu_model

• [Change] All parsers integrated (#33)

mcp-servers

• [Change] SDLC harness added (#23)

Automated dependency updates: 10 merged (baselibs 1, communication 1, inc_security_crypto 4, module_template 1, persistency 1, process_description 1, score 1), plus 3 in docs-as-code.

Issues

• communication — bug: a method call on an expired skeleton scope aborts the provider after a kSkeletonAlreadyDestroyed reply (#1420)
• docs-as-code — enforce safety-aware derivation (#985)
• sbom-tool — Rust crates from git get incorrect crates.io download URLs (#28)

5 opened, 7 closed.

---

S-CORE Daily is generated automatically from public eclipse-score activity for the window shown. Links go to the sources; corrections welcome as replies.

[dcalavrezo-qorix]

S-CORE Daily — 2026-10-22

Headline

Two releases (bazel_cpp_toolchains v1.0.5 and docs-as-code v8.5.1) shipped, 27 pull requests merged across 17 repositories, and the Tech Lead Sync reviewed Persistency's compliance status and the open Misra-check question for S-CORE v1.0.

In plain terms

Two building blocks of the project got new releases: the C++ build toolchains (including one removal that may affect users of an old compiler package) and the documentation tooling (a security-motivated dependency refresh). The Tech Lead Sync reported that Persistency, the pilot module for the safety process, shows full traceability to the process, and noted that the set of Misra coding-rule checks (a standard for safe C/C++ code) for S-CORE v1.0 still needs to be agreed. Elsewhere, Lifecycle, mcp-servers and Persistency saw steady engineering work. Several new issues were opened against communication, SOME/IP gateway and time modules; they are worth watching.

Releases

• bazel_cpp_toolchains v1.0.5 — GCC version flag now derived from the resolved toolchain, rules_cc bumped to 0.2.25, support for the io-pkt Driver Development Kit, a new type attribute on the SDP tag class. Breaking: EBclfsa 0.1.0 was removed (superseded by 2.0.0-beta). Release
• docs-as-code v8.5.1 — Maintenance patch release; main reason is updating the certifi Python dependency for security reasons. The release notes state there is no actual indication of risk. No features or fixes for users. Release

From the meetings

Tech Lead Sync (Technical Lead Circle) — minutes by @antonkri

• Decisions / conclusions:
  • Persistency: "All processes are applied." Linkage reported at 100 % (31 of 31 work products realize a process work product); audit Improvement: Add copyright header for all .yml files. #6: 29 clauses OK, 3 actions, 1 open.
  • Communication "does follow its own process, we will do Component Qualification for it."
  • Baselibs: main focus is Result and BitManipulation.
• Action items:
  • "We need to agree on set of Misra checks that will apply for S-Core v1.0 -> @antonkri"
• Open questions:
  • Misra checks with CodeQL are important for S-CORE v1.0; related open discussions are score#3262, score#2984 and score_rust_policies#11.
  • Downloadable images: first PR and Add Raspberry pi image in ref int reference_integration#403 are referenced.

Persistency Feature Team — minutes by @umaucher

• Decisions / guidance:
  • PR handling: "avoid rebasing if not needed (requires new approval for the QNX builds) use the 'Update branch' -> 'Update with merge commit' if needed".
  • Outcome of the reset_key discussion is recorded in persistency#527.
• Action items:
  • Push the C++ code-style guideline (namespace matches folder structure) in the Monday TL sync.
  • Raise Dependabot/Renovate setup in the TL sync.
  • persistency#563 needs review plus help with testing/mocking.
• Open questions: Do both Dependabot and Renovate need to be used? Generic setup for all repos? Tagging of cicd-workflows/actions? Meeting time shift to 13:30 is being polled on Slack.
• Status noted: 8 new issues, 11 closed; 20 new PRs, many merged.

Discussions worth following

• S-CORE Daily (Show and tell) — received one comment (link) carrying the 2026-10-21 edition.

Code changes

baselibs

• [Documentation] Remove nlohmann_json from safety planning; add document lists to the start page for the safety package — (#721, #722)

bazel_cpp_toolchains

• [Breaking change] Remove EBclfsa 0.1.0 — superseded months ago by 2.0.0-beta (#165)
• [Change] Migrate copyright checker to score_tools and refresh headers (#166)

cicd-workflows

• [Bug fix] Prefetch QNX SDP during analysis so retries cover a qnx.com timeout (#260)

communication

• [Change] Migrate flags to features; pin CI to Ubuntu 24.04 so builds stay reproducible (#1424, #1428)

devcontainer

• [Bug fix] Renovate configuration and lockfile handling (#171)

docs-as-code

• [Maintenance] Upgrade Python dependencies, keep sphinx-needs on 8.x (#989)

inc_someip_gateway

• [Maintenance] Port IPC benchmarks to the mw::com implementation to help phase out the other IPC (#359)

lifecycle

• [Change] New Component class with pluggable start/stop/ready strategies (#705)
• [Change] Docs for new ControlClient APIs, release notes (#796, #841)
• [Change] More unit tests, including 100 % coverage of the alive worker factory and an empty-sgids sandbox check (#799, #835)

logging

• [Change] Remove a misleading comment in the data router (#368)

mcp-servers

• [Change] Central code-graph caching artifacts, serving from a user cache, and an agent-context devcontainer feature for AI tooling (#47, #49, #50)

persistency

• [CI / automation] Skip the QNX build for Dependabot PRs (it lacks required secrets) and add manual dispatch (#559)

process_description

• [Change] Add AI-supported development process execution concept (pilot) (#809)

score

• [Change] Fix audit findings in PMP-PRM and update process (#3343)

tooling

• [Change] Fix certified-scope violation-detection bugs in Bazel rules (#533)

Automated dependency updates: 17 merged (devcontainer 1, inc_security_crypto 2, inc_someip_gateway 3, kyron 1, mcp-servers 1, module_template 2, persistency 6, process_description 1).

Issues

• communication: first GetNewSamples after Subscribe returns pre-subscription samples; destroying a subscribed proxy aborts
• inc_someip_gateway: wrong payload bytes after gatewayd restart; someipd keeps offering a service after provider stops; gatewayd missing score_com_serializer.so
• time: TimeJumpsValidator vs. time-leap requirements; no separate startup timeout / hard-coded SVT parameters

21 issues opened, 5 closed.

S-CORE Daily is generated automatically from public eclipse-score activity for the window shown. Links go to the sources; corrections welcome as replies.