Skip to content

Feat: Upgrade deps#67

Merged
RolandJentschETAS merged 4 commits into
mainfrom
MSP_update_deps
May 11, 2026
Merged

Feat: Upgrade deps#67
RolandJentschETAS merged 4 commits into
mainfrom
MSP_update_deps

Conversation

@MaximilianSoerenPollak
Copy link
Copy Markdown
Contributor

No description provided.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 29, 2026

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]
Extracting Bazel installation...
Starting local Bazel server (8.3.0) and connecting to it...
INFO: Invocation ID: fb570116-2341-489d-81c4-63befa2b0c90
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Loading: 
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
Analyzing: target //:license-check (1 packages loaded, 0 targets configured)
Analyzing: target //:license-check (1 packages loaded, 0 targets configured)

Analyzing: target //:license-check (26 packages loaded, 9 targets configured)

Analyzing: target //:license-check (77 packages loaded, 9 targets configured)

Analyzing: target //:license-check (80 packages loaded, 9 targets configured)

Analyzing: target //:license-check (86 packages loaded, 9 targets configured)

Analyzing: target //:license-check (143 packages loaded, 2707 targets configured)

Analyzing: target //:license-check (147 packages loaded, 5944 targets configured)

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

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

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

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

Analyzing: target //:license-check (151 packages loaded, 7947 targets configured)

Analyzing: target //:license-check (159 packages loaded, 9977 targets configured)

Analyzing: target //:license-check (160 packages loaded, 10097 targets configured)

Analyzing: target //:license-check (160 packages loaded, 10097 targets configured)

Analyzing: target //:license-check (160 packages loaded, 10097 targets configured)

Analyzing: target //:license-check (160 packages loaded, 10097 targets configured)

INFO: Analyzed target //:license-check (161 packages loaded, 12032 targets configured).
[12 / 16] JavaToolchainCompileClasses external/rules_java+/toolchains/platformclasspath_classes; 0s disk-cache
[13 / 16] Generating Dash formatted dependency file ...; 0s disk-cache, processwrapper-sandbox ... (2 actions, 1 running)
[13 / 16] Generating Dash formatted dependency file ...; 1s disk-cache, processwrapper-sandbox ... (2 actions running)
INFO: From Generating Dash formatted dependency file ...:
INFO: Successfully converted 2 packages from Cargo.lock to bazel-out/k8-fastbuild/bin/formatted.txt
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: 217.449s, Critical Path: 3.42s
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>
usage: org.eclipse.dash.licenses.cli.Main [-batch <int>] [-cd <url>]
       [-confidence <int>] [-ef <url>] [-excludeSources <sources>] [-help] [-lic
       <url>] [-project <shortname>] [-repo <url>] [-review] [-summary <file>]
       [-timeout <seconds>] [-token <token>]

@MaximilianSoerenPollak
Copy link
Copy Markdown
Contributor Author

@RolandJentschETAS

I just encountered this build error here:

/home/runner/work/module_template/module_template/score/component_example/docs/architecture/index.rst:75: WARNING: Need 'comp__mod_temp_component_name_template' has unknown outgoing link 'feat__feature_name' in field 'belongs_to' [needs.link_outgoing]
/home/runner/work/module_template/module_template/score/component_example/docs/detailed_design/detailed_design_example.rst:28: WARNING: Need 'dd_sta__example_feature__approver' has unknown outgoing link 'sw_unit__example_feature__unit1' in field 'includes' [needs.link_outgoing]
/home/runner/work/module_template/module_template/score/component_example/docs/detailed_design/detailed_design_example.rst:28: WARNING: Need 'dd_sta__example_feature__approver' has unknown outgoing link 'sw_unit__example_feature__unit2' in field 'includes' [needs.link_outgoing]
/home/runner/work/module_template/module_template/score/component_example/docs/requirements/index.rst:40: WARNING: Need 'comp_req__mod_temp_component_name__some_title' has unknown outgoing link 'feat_req__feature_name__some_title' in field 'satisfies' [needs.link_outgoing]

Do you happen to know where I need to put those missing things etc.?
Or will you take care of this or how should we proceed.

@RolandJentschETAS
Copy link
Copy Markdown
Contributor

@RolandJentschETAS

I just encountered this build error here:

/home/runner/work/module_template/module_template/score/component_example/docs/architecture/index.rst:75: WARNING: Need 'comp__mod_temp_component_name_template' has unknown outgoing link 'feat__feature_name' in field 'belongs_to' [needs.link_outgoing]
/home/runner/work/module_template/module_template/score/component_example/docs/detailed_design/detailed_design_example.rst:28: WARNING: Need 'dd_sta__example_feature__approver' has unknown outgoing link 'sw_unit__example_feature__unit1' in field 'includes' [needs.link_outgoing]
/home/runner/work/module_template/module_template/score/component_example/docs/detailed_design/detailed_design_example.rst:28: WARNING: Need 'dd_sta__example_feature__approver' has unknown outgoing link 'sw_unit__example_feature__unit2' in field 'includes' [needs.link_outgoing]
/home/runner/work/module_template/module_template/score/component_example/docs/requirements/index.rst:40: WARNING: Need 'comp_req__mod_temp_component_name__some_title' has unknown outgoing link 'feat_req__feature_name__some_title' in field 'satisfies' [needs.link_outgoing]

Do you happen to know where I need to put those missing things etc.? Or will you take care of this or how should we proceed.

Let me tomorrow check, whats going on there. It could be, that there are multiple reasons for it. For example it might be one or two of them are fixed in process 1.5.4.

@github-actions
Copy link
Copy Markdown

The created documentation from the pull request is available at: docu-html

@RolandJentschETAS
Copy link
Copy Markdown
Contributor

@RolandJentschETAS
I just encountered this build error here:

/home/runner/work/module_template/module_template/score/component_example/docs/architecture/index.rst:75: WARNING: Need 'comp__mod_temp_component_name_template' has unknown outgoing link 'feat__feature_name' in field 'belongs_to' [needs.link_outgoing]
/home/runner/work/module_template/module_template/score/component_example/docs/detailed_design/detailed_design_example.rst:28: WARNING: Need 'dd_sta__example_feature__approver' has unknown outgoing link 'sw_unit__example_feature__unit1' in field 'includes' [needs.link_outgoing]
/home/runner/work/module_template/module_template/score/component_example/docs/detailed_design/detailed_design_example.rst:28: WARNING: Need 'dd_sta__example_feature__approver' has unknown outgoing link 'sw_unit__example_feature__unit2' in field 'includes' [needs.link_outgoing]
/home/runner/work/module_template/module_template/score/component_example/docs/requirements/index.rst:40: WARNING: Need 'comp_req__mod_temp_component_name__some_title' has unknown outgoing link 'feat_req__feature_name__some_title' in field 'satisfies' [needs.link_outgoing]

Do you happen to know where I need to put those missing things etc.? Or will you take care of this or how should we proceed.

Let me tomorrow check, whats going on there. It could be, that there are multiple reasons for it. For example it might be one or two of them are fixed in process 1.5.4.

Fixed.

Signed-off-by: RolandJentschETAS <135332348+RolandJentschETAS@users.noreply.github.com>
@RolandJentschETAS RolandJentschETAS merged commit baacd99 into main May 11, 2026
9 checks passed
@RolandJentschETAS RolandJentschETAS deleted the MSP_update_deps branch May 11, 2026 09:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

2 participants