Repository navigation
chore(deps): update dependency score_tooling to v2.3.1 - #377
Open
eclipse-score-bot wants to merge 1 commit into
Open
eclipse-score-bot wants to merge 1 commit into
eclipse-score-bot wants to merge 1 commit into
Conversation
eclipse-score-bot
requested review from
antonkri,
arsibo,
hoppe-and-dreams,
pawelrutkaq and
rmaddikery
as code owners
October 26, 2026 11:37
eclipse-score-bot
requested a deployment
to
workflow-approval
October 26, 2026 11:37 — with
GitHub Actions
Waiting
Contributor
License Check Results🚀 The license check job ran with the Bazel command: bazel run --lockfile_mode=error //:license-checkStatus: Click to expand output |
eclipse-score-bot
force-pushed
the
renovate/score_tooling-2.x
branch
from
October 27, 2026 13:21
00368ff to
6ccc17d
Compare
eclipse-score-bot
requested a deployment
to
workflow-approval
October 27, 2026 13:21 — with
GitHub Actions
Waiting
eclipse-score-bot
force-pushed
the
renovate/score_tooling-2.x
branch
from
October 28, 2026 09:15
6ccc17d to
bbafb8e
Compare
eclipse-score-bot
requested a deployment
to
workflow-approval
October 28, 2026 09:15 — with
GitHub Actions
Waiting
eclipse-score-bot
force-pushed
the
renovate/score_tooling-2.x
branch
from
October 28, 2026 10:09
bbafb8e to
e1394b6
Compare
eclipse-score-bot
requested a deployment
to
workflow-approval
October 28, 2026 10:09 — with
GitHub Actions
Waiting
eclipse-score-bot
force-pushed
the
renovate/score_tooling-2.x
branch
from
October 28, 2026 11:10
e1394b6 to
137858a
Compare
eclipse-score-bot
requested a deployment
to
workflow-approval
October 28, 2026 11:10 — with
GitHub Actions
Waiting
eclipse-score-bot
force-pushed
the
renovate/score_tooling-2.x
branch
from
October 28, 2026 12:11
137858a to
33e0d31
Compare
eclipse-score-bot
requested a deployment
to
workflow-approval
October 28, 2026 12:11 — with
GitHub Actions
Waiting
eclipse-score-bot
force-pushed
the
renovate/score_tooling-2.x
branch
from
October 28, 2026 14:09
33e0d31 to
48c6b7c
Compare
eclipse-score-bot
requested a deployment
to
workflow-approval
October 28, 2026 14:09 — with
GitHub Actions
Waiting
eclipse-score-bot
force-pushed
the
renovate/score_tooling-2.x
branch
from
October 28, 2026 15:09
48c6b7c to
c62b88a
Compare
eclipse-score-bot
requested a deployment
to
workflow-approval
October 28, 2026 15:10 — with
GitHub Actions
Waiting
This branch is waiting to be deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.2.0→2.3.1Release Notes
eclipse-score/tooling (score_tooling)
v2.3.1Release v2.3.x contains breaking changes:
Renames (Bazel)
fmea(...) is now safety_analysis(...).
dependability_analysis(fmea = [...]) is now dependability_analysis(safety_analysis = [...]).
The controlmeasures attribute is replaced by safetymeasures. These files hold Mitigation, AoU and CompReq records.
New optional attribute fta_package sets the package name of the generated RootCause records. It defaults to _fta.
unit(...) and component(...) get an optional design_name. Use it when the PlantUML <>/<> name differs from the Bazel target name.
FTA .puml diagrams
$TopEvent(...) is now $FailureMode(name, "Pkg.FailureMode", ...). It accepts up to 8 failure modes per node.
$BasicEvent(name, "Pkg.Alias", conn) is now $RootCause(name, "Alias", conn). The alias is a plain name without a package prefix.
Root causes are generated as TRLC records in fta_events.trlc (package <fta_package>). They are not written by hand.
Each root cause links to the failure modes of the tree it sits under.
TRLC model (ScoreReq)
Removed: ControlMeasure, PreventiveMeasure and Measure.
Removed: the mitigates field on AoU and Mitigation.
Added: RootCause, the abstract SafetyMeasure, and FailureMode-to-RootCause links.
Mitigation no longer extends AssumedSystemReq. It now requires root_causes = [...] and justification.
AoU can have optional root_causes = [...].
CompReq.derived_from can reference a RootCause, unversioned. This makes the CompReq a control measure for that root cause.
CompReq.derived_from may only reference AoUs received from other dependable elements. An element's own AoUs are never a source.
Wiring (BUILD)
A safety_analysis target that an AoU references via root_causes must be listed in the deps of assumptions_of_use.
The same target must also be passed via safetymeasures to safety_analysis(...).
Migration:
BUILD
fmea becomes safety_analysis.
controlmeasures becomes safetymeasures.
dependability_analysis(fmea=...) becomes dependability_analysis(safety_analysis=...).
FTA .puml
$TopEvent becomes $FailureMode.
$BasicEvent(n, "Pkg.Alias", c) becomes $RootCause(n, "Alias", c). The alias is a plain identifier with no package prefix.
TRLC measures
Add import _fta, the generated package. It defaults to the target name plus _fta.
Delete ControlMeasure and PreventiveMeasure records and all mitigates fields.
Convert each former measure:
Mitigation: add root_causes = [_fta.] and justification.
CompReq: add derived_from = [_fta.], with no @version. Add the safety_analysis target to that component_requirements target's deps.
AoU: add root_causes = [_fta.]. Add the safety_analysis target to the assumptions_of_use deps, and pass the file in safetymeasures.
Coverage
Every $RootCause needs a Mitigation, AoU or CompReq. Otherwise release maturity fails.
Every FailureMode needs a $RootCause under it.
v2.3.0What's Changed
Full Changelog: eclipse-score/tooling@v2.2.3...v2.3.0
v2.2.3What's Changed
Full Changelog: eclipse-score/tooling@v2.2.2...v2.2.3
v2.2.2What's Changed
New Contributors
Full Changelog: eclipse-score/tooling@v2.2.0...v2.2.2
v2.2.1What's Changed
Full Changelog: eclipse-score/tooling@v2.1.1...v2.2.1
This PR was generated by #infrastructure automation. Contact us if you have any questions or feedback.