Skip to content

Conversation

@AlexanderLanin
Copy link
Member

@AlexanderLanin AlexanderLanin commented Nov 12, 2025

Users that do not explicitly depend on score_process 1.3.1 themselfes, will get a resolution error as they pull docs-as-code 2, which pulls process 1.2, which pulls docs-as-code 1.

Workaround for users that have docs-as-code <= 2.0.1:

Add bazel_dep(name = "score_process", version = "1.3.1")

Copilot AI review requested due to automatic review settings November 12, 2025 10:18
@AlexanderLanin AlexanderLanin changed the title Bump version to 2.0.2 and update score_process dependency to 1.3.1 Fix: bump version to 2.0.2 and update score_process dependency to 1.3.1 Nov 12, 2025
@github-actions
Copy link

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run //src: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: 9394ff85-06ff-43f5-bb2d-9958d046ea31
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
    currently loading: src
Analyzing: target //src:license-check (1 packages loaded, 0 targets configured)
Analyzing: target //src:license-check (1 packages loaded, 0 targets configured)

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

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

Analyzing: target //src:license-check (126 packages loaded, 2180 targets configured)

Analyzing: target //src:license-check (129 packages loaded, 2435 targets configured)

Analyzing: target //src:license-check (135 packages loaded, 2484 targets configured)

INFO: Analyzed target //src:license-check (137 packages loaded, 4500 targets configured).
INFO: Found 1 target...
Target //src:license.check.license_check up-to-date:
  bazel-bin/src/license.check.license_check
  bazel-bin/src/license.check.license_check.jar
INFO: Elapsed time: 15.598s, Critical Path: 0.39s
INFO: 13 processes: 4 disk cache hit, 9 internal.
INFO: Build completed successfully, 13 total actions
INFO: Running command line: bazel-bin/src/license.check.license_check src/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>]

Copilot finished reviewing on behalf of AlexanderLanin November 12, 2025 10:19
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR bumps the version of score_docs_as_code from 2.0.1 to 2.0.2 and updates the score_process dependency from 1.2.0 to 1.3.1 to resolve a circular dependency resolution error where users pulling docs-as-code 2 would encounter conflicts due to the transitive dependency chain through score_process 1.2.

  • Version bumped to 2.0.2 in MODULE.bazel
  • Updated score_process dependency from 1.2.0 to 1.3.1 with explanatory comment
  • Added documentation clarifying the dependency update rationale

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@github-actions
Copy link

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

@AlexanderLanin AlexanderLanin merged commit df4e6a3 into eclipse-score:main Nov 12, 2025
19 checks passed
@AlexanderLanin AlexanderLanin deleted the process_update branch November 12, 2025 11:04
@github-project-automation github-project-automation bot moved this from Draft to Done in Infrastructure Nov 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants