Skip to content

Update dependency score_process to v2#173

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

Update dependency score_process to v2#173
eclipse-score-bot wants to merge 1 commit into
mainfrom
renovate/score_process-2.x

Conversation

@eclipse-score-bot

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

Copy link
Copy Markdown

This PR contains the following updates:

Package Type Update Change
score_process bazel_dep major 1.5.4 → 2.0.1

Release Notes

eclipse-score/process_description (score_process)

v2.0.1

Release Note v2.0.1

| Module Name: Process description
| Release Tag: v2.0.1
| Origin Release Tag: v1.5.4...v2.0.0
| Release Date: 2026-07-02

Overview
^^^^^^^^

The module process_description provides a process model establishing organization rules
for developing open source software in the automotive industry, which can be used in
safety and security context.

The process model provides processes, which conform to state-of the art standards

ASPICE 4.0
ISO 26262
ISO 21434
ISO PAS 8926

Disclaimer

This release note does not "release for production", as it does not come with a safety
argumentation and a performed safety assessment.
The work products compiled in the safety package are created with care according to a
process satisfying standards, but the project, being a non-profit and open source
organization, can not take over any liability for its content.

Changes to the Module
^^^^^^^^^^^^^^^^^^^^^

New Features

Building blocks meta model is reworked.
(https://eclipse-score.github.io/process_description/main/index.html).
Contains now Features, Components as own elements, adapt linkage names, e.g.
Requirements are now "derived_from" parent requirements, correct some linkages between
elements

Module Templates removed from Folder Templates and
(https://eclipse-score.github.io/process_description/main/folder_templates/index.html)

moved now to module_templates folder
(https://eclipse-score.github.io/module_template/main/)

Implementation is now defined.

Now versioning of sphinx-needs elements is introduced. Thus this version is the first
baseline of the process_description.

The process model contains

  • General concepts e.g. for Building Blocks and their traceability
  • Process meta model for proper modeling
  • Process areas covering the required standards
  • Roles, Work Products, Workflows defining the process areas
  • Standard overview and coverage information
  • Folder templates for simplifying deployment for users
  • Glossary
  • Release Notes

Improvements

Bug Fixes

not applicable

Other changes by Label

not applicable

Compatibility
^^^^^^^^^^^^^

Doc-as-code, module_template

For a detailed list checkout here: https://github.com/eclipse-score/process_description/blob/main/MODULE.bazel

Performed Verification
^^^^^^^^^^^^^^^^^^^^^^

Initial Safety Audit by external assessor teams for every process area.

Known Issues

Known Vulnerabilities

None

Upgrade Instructions
^^^^^^^^^^^^^^^^^^^^

As Building Blocks Meta Model is adapted and Templates are removed, consider to use the compatible doc-as-code version and the module templates from the module_template repository.

Versionning is introduced. Updated with the latest doc-as-code version.

Contact Information
For any questions or support, please contact the SW Process Development Community (https://redirect.github.com/orgs/eclipse-score/discussions/108) or raise an issue/discussion.

v2.0.0

Release Note v2.0.0

| Module Name: Process description
| Release Tag: v2.0.0
| Origin Release Tag: v1.5.4
| Release Date: 2026-06-30

Overview
^^^^^^^^

The module process_description provides a process model establishing organization rules
for developing open source software in the automotive industry, which can be used in
safety and security context.

The process model provides processes, which conform to state-of the art standards

ASPICE 4.0
ISO 26262
ISO 21434
ISO PAS 8926

Disclaimer

This release note does not "release for production", as it does not come with a safety
argumentation and a performed safety assessment.
The work products compiled in the safety package are created with care according to a
process satisfying standards, but the project, being a non-profit and open source
organization, can not take over any liability for its content.

Changes to the Module
^^^^^^^^^^^^^^^^^^^^^

New Features

Building blocks meta model is reworked.
(https://eclipse-score.github.io/process_description/main/index.html).
Contains now Features, Components as own elements, adapt linkage names, e.g.
Requirements are now "derived_from" parent requirements, correct some linkages between
elements

Module Templates removed from Folder Templates and
(https://eclipse-score.github.io/process_description/main/folder_templates/index.html)

moved now to module_templates folder
(https://eclipse-score.github.io/module_template/main/)

Implementation is now defined.

Now versioning of sphinx-needs elements is introduced. Thus this version is the first
baseline of the process_description.

The process model contains

  • General concepts e.g. for Building Blocks and their traceability
  • Process meta model for proper modeling
  • Process areas covering the required standards
  • Roles, Work Products, Workflows defining the process areas
  • Standard overview and coverage information
  • Folder templates for simplifying deployment for users
  • Glossary
  • Release Notes

Improvements

Bug Fixes

not applicable

Other changes by Label

not applicable

Compatibility
^^^^^^^^^^^^^

Doc-as-code, module_template

For a detailed list checkout here: https://github.com/eclipse-score/process_description/blob/main/MODULE.bazel

Performed Verification
^^^^^^^^^^^^^^^^^^^^^^

Initial Safety Audit by external assessor teams for every process area.

Known Issues

Known Vulnerabilities

None

Upgrade Instructions
^^^^^^^^^^^^^^^^^^^^

As Building Blocks Meta Model is adapted and Templates are removed, consider to use the compatible doc-as-code version and the module templates from the module_template repository.

Versioning is introduced. Updated with the latest doc-as-code version.

Contact Information
For any questions or support, please contact the SW Process Development Community (https://redirect.github.com/orgs/eclipse-score/discussions/108) or raise an issue/discussion.

v1.6.0

What's Changed

Other Changes

New Contributors

Full Changelog: eclipse-score/process_description@v1.5.4...v1.6.0

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

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

@github-actions

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

Copy link
Copy Markdown

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.6.0) and connecting to it...
INFO: Invocation ID: c9528a20-e371-4fba-8401-f5aa3f695956
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
WARNING: For repository 'score_crates', the root module requires module version score_crates@0.0.9, but got score_crates@0.0.10 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
Computing main repo mapping: 
Loading: 
Loading: 4 packages loaded
Loading: 4 packages loaded
    currently loading: 
Loading: 4 packages loaded
    currently loading: 
WARNING: Target pattern parsing failed.
ERROR: Skipping '//:license-check': no such target '//:license-check': target 'license-check' not declared in package '' defined by /home/runner/work/logging/logging/BUILD
ERROR: no such target '//:license-check': target 'license-check' not declared in package '' defined by /home/runner/work/logging/logging/BUILD
INFO: Elapsed time: 13.826s
INFO: 0 processes.
ERROR: Build did NOT complete successfully
ERROR: Build failed. Not running target

@eclipse-score-bot
eclipse-score-bot force-pushed the renovate/score_process-2.x branch from 50acd57 to 2999513 Compare July 1, 2026 13:49
@eclipse-score-bot
eclipse-score-bot force-pushed the renovate/score_process-2.x branch from 2999513 to 33079a9 Compare July 3, 2026 09:04
@eclipse-score-bot
eclipse-score-bot force-pushed the renovate/score_process-2.x branch from 33079a9 to ea04f43 Compare July 3, 2026 10:55
@eclipse-score-bot
eclipse-score-bot force-pushed the renovate/score_process-2.x branch from ea04f43 to 742e2db Compare July 3, 2026 14:47
@eclipse-score-bot
eclipse-score-bot force-pushed the renovate/score_process-2.x branch from 742e2db to 6eb08c1 Compare July 7, 2026 12:48
@eclipse-score-bot
eclipse-score-bot force-pushed the renovate/score_process-2.x branch from 6eb08c1 to 6f532c1 Compare July 8, 2026 14:50
@eclipse-score-bot
eclipse-score-bot force-pushed the renovate/score_process-2.x branch from 6f532c1 to 18377ae Compare July 9, 2026 07:11
@eclipse-score-bot
eclipse-score-bot force-pushed the renovate/score_process-2.x branch from 18377ae to f7d29b5 Compare July 10, 2026 09:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@antonkri antonkri Awaiting requested review from antonkri antonkri is a code owner
@pawelrutkaq pawelrutkaq Awaiting requested review from pawelrutkaq pawelrutkaq is a code owner
@arsibo arsibo Awaiting requested review from arsibo arsibo is a code owner
@rmaddikery rmaddikery Awaiting requested review from rmaddikery rmaddikery is a code owner

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

automation renovate

Projects

LOG - Logging FT
Status: Backlog

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@eclipse-score-bot