[PandaeDo]

Update safety management artefacts to update to the latest changes

[github-actions]

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run --lockfile_mode=error //:license-check

Status: ⚠️ Needs Review

Click to expand output

[License Check Output]
Starting local Bazel server (8.7.0) and connecting to it...
INFO: Invocation ID: d459d2c9-80ca-47d5-96f4-0c81e3ac418e
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Loading: 
Loading: 2 packages loaded
Loading: 2 packages loaded
    currently loading: 
Loading: 2 packages loaded
    currently loading: 
Loading: 2 packages loaded
    currently loading: 
Loading: 2 packages loaded
    currently loading: 
Loading: 2 packages loaded
    currently loading: 
Loading: 2 packages loaded
    currently loading: 
Analyzing: target //:license-check (3 packages loaded, 0 targets configured)
Analyzing: target //:license-check (3 packages loaded, 0 targets configured)

Analyzing: target //:license-check (87 packages loaded, 14 targets configured)

Analyzing: target //:license-check (92 packages loaded, 14 targets configured)

Analyzing: target //:license-check (150 packages loaded, 2319 targets configured)

Analyzing: target //:license-check (163 packages loaded, 7394 targets configured)

Analyzing: target //:license-check (170 packages loaded, 9846 targets configured)

Analyzing: target //:license-check (171 packages loaded, 9970 targets configured)

Analyzing: target //:license-check (172 packages loaded, 14063 targets configured)

Analyzing: target //:license-check (175 packages loaded, 15951 targets configured)

Analyzing: target //:license-check (175 packages loaded, 15951 targets configured)

Analyzing: target //:license-check (175 packages loaded, 15951 targets configured)

INFO: Analyzed target //:license-check (176 packages loaded, 16077 targets configured).
[13 / 16] Generating Dash formatted dependency file ...; 0s disk-cache, processwrapper-sandbox ... (2 actions, 1 running)
INFO: From Generating Dash formatted dependency file ...:
INFO: Successfully converted 50 packages from Cargo.lock to bazel-out/k8-fastbuild/bin/formatted.txt
[15 / 16] Building license.check.license_check.jar (); 0s disk-cache, multiplex-worker
INFO: Found 1 target...
Target //:license.check.license_check up-to-date:
  bazel-bin/license.check.license_check
  bazel-bin/license.check.license_check.jar
INFO: Elapsed time: 29.843s, Critical Path: 2.16s
INFO: 16 processes: 12 internal, 3 processwrapper-sandbox, 1 worker.
INFO: Build completed successfully, 16 total actions
INFO: Running command line: bazel-bin/license.check.license_check ./formatted.txt <args omitted>
[main] INFO Querying Eclipse Foundation for license data for 42 items.
[main] INFO Found 32 items.
[main] INFO Querying ClearlyDefined for license data for 10 items.
[main] INFO Found 10 items.
[main] INFO License information could not be automatically verified for the following content:
[main] INFO 
[main] INFO crate/cratesio/-/lazy_static/1.5.1
[main] INFO 
[main] INFO This content is either not correctly mapped by the system, or requires review.

[janis-qorix]

Good improvements and important updates regarding

• current status of safety analyses
• different implementation regarding KVS with Rust / C++

[umaucher]

not blocking but topic we need to address IMHO ... links like this are not specific and always point to "latest" status ... question if we need to have "exact" links e.g. for releases?

[PandaeDo]

I would say that's sufficient that the safety plan points to the source code. When we create a safety case then I would be a better if we have a exact link. But it will also be understandable in combination with the release itself. I'll take this into the process community to discuss it there.