Skip to content

chore(bazel): align development-only dependencies - #32

Open
eclipse-score-bot wants to merge 1 commit into
mainfrom
repo-policy-sync/dev-dependency-alignment
Open

chore(bazel): align development-only dependencies#32
eclipse-score-bot wants to merge 1 commit into
mainfrom
repo-policy-sync/dev-dependency-alignment

Conversation

@eclipse-score-bot

Copy link
Copy Markdown
Contributor

Policy

dev-dependency-alignment

Keep Bazel toolchain, lint, image, and documentation dependencies in the
intended dependency graph. The listed build-support dependencies are
development-only, while score_docs_as_code is used by the normal build graph.

Why this repository?

This repository matches this policy because MODULE.bazel declares at least one of these direct Bazel dependencies: score_bazel_cpp_toolchains, aspect_rules_py, buildifier_prebuilt, aspect_rules_lint, toolchains_llvm, score_rules_imagefs, score_docs_as_code.

Changes

  • MODULE.bazel: remove dev_dependency from Bazel dependency 'score_docs_as_code'
    • Documentation rules are required by the normal build graph.

Tool revision

Generated from eclipse-score/tools at commit 2f46bfa.


This pull request is managed by SCORE Repository Policy Sync and may be updated by a later policy run.
Please report any issues to #score-infrastructure.

Note

This pull request is generated automatically. Review the proposed changes
before merging.

@github-actions

github-actions Bot commented Sep 12, 2026

Copy link
Copy Markdown

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run //: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: 8a54a591-8a10-416e-b630-aa68e607e181
Computing main repo mapping: 
Loading: 
Loading: 0 packages loaded
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
Loading: 1 packages loaded
Analyzing: target //:license-check (1 packages loaded, 0 targets configured)
Analyzing: target //:license-check (1 packages loaded, 0 targets configured)

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

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

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

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

Analyzing: target //:license-check (162 packages loaded, 8432 targets configured)

Analyzing: target //:license-check (169 packages loaded, 9541 targets configured)

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

INFO: Analyzed target //:license-check (175 packages loaded, 15774 targets configured).
[9 / 15] [Prepa] Writing repo mapping manifest for @@score_tooling+//dash/tool/formatters:dash_format_converter [for tool]
INFO: From Generating Dash formatted dependency file ...:
INFO: Successfully converted 2 packages from Cargo.lock to bazel-out/k8-fastbuild/bin/formatted.txt
[14 / 16] JavaToolchainCompileBootClasspath external/rules_java+/toolchains/platformclasspath.jar; 0s disk-cache, processwrapper-sandbox
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: 55.349s, Critical Path: 2.04s
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>]

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant