Skip to content

Update dependency score_docs_as_code to v6 - #250

Open
eclipse-score-bot wants to merge 2 commits into
mainfrom
renovate/score_docs_as_code-6.x
Open

Update dependency score_docs_as_code to v6#250
eclipse-score-bot wants to merge 2 commits into
mainfrom
renovate/score_docs_as_code-6.x

Conversation

@eclipse-score-bot

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
score_docs_as_code bazel_dep major 4.6.06.0.0

Release Notes

eclipse-score/docs-as-code (score_docs_as_code)

v6.0.0

BREAKING CHANGE

  • dropped docs_combo target, since now everyone can declare a "combo" target however they want.
  • downgrade to rules_python 1.x

What's Changed

Internal

New Contributors

Full Changelog: eclipse-score/docs-as-code@v5.0.0...v6.0.0

v5.0.0

BREAKING CHANGES

What's Changed

Internal

New Contributors

Full Changelog: eclipse-score/docs-as-code@v4.6.1...v5.0.0

v4.6.1

What's Changed (compared to last release)

Full Changelog: eclipse-score/docs-as-code@v4.6.0...v4.6.1


What's Changed (Score 0.7 vs Score 0.8)

  • Added traceability metrics features. Metrics can now be calculated and viewed via metrics.json
  • Metamodel.yaml is now replaceable with your own metamodel
  • Renamed satisfies → derived_from
  • Restrictions for some uses of needextends
  • valid_from is now a mandatory attribute for some need types
  • Bazel upgrade from 8.4.2 => 8.6.0
  • Upgraded current tool requirements to reflect process 2.0
  • Changed version attribute to be an integer instead of string
  • Changed version in doc_tool to be tool_version to allow for global 'version' attribute.

Full Changelog: eclipse-score/docs-as-code@v4.0.3...v4.6.1


  • 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 Jul 30, 2026

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: d63d56ca-b07b-47b4-9cf1-e8a6d9097447
Computing main repo mapping: 
Computing main repo mapping: 
WARNING: For repository 'score_process', the root module requires module version score_process@1.5.4, but got score_process@2.0.1 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
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: 
Computing main repo mapping: 
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: 10.055s
INFO: 0 processes.
ERROR: Build did NOT complete successfully
ERROR: Build failed. Not running target

@eclipse-score-bot

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Backlog

Development

Successfully merging this pull request may close these issues.

3 participants