Skip to content

Configure Renovate#61

Closed
eclipse-score-bot wants to merge 1 commit intomainfrom
renovate/configure
Closed

Configure Renovate#61
eclipse-score-bot wants to merge 1 commit intomainfrom
renovate/configure

Conversation

@eclipse-score-bot
Copy link
Copy Markdown
Contributor

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

📚 See our Reading List for relevant documentation you may be interested in reading.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.


Detected Package Files

  • MODULE.bazel (bazel-module)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Enable Renovate Dependency Dashboard creation.
  • Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
  • Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Show only the Age and Confidence Merge Confidence badges for pull requests.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.
  • Ensure that every dependency pinned by digest and sourced from Forgejo contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
  • Correctly link to the source code for golang.org/x packages
  • Link to pkg.go.dev/... for golang.org/x packages' title

What to Expect

With your current configuration, Renovate will create 10 Pull Requests:

EXPERIMENTAL DO NOT MERGE - googletest update
  • Schedule: ["at any time"]
  • Branch name: renovate/googletest-1.x
  • Merge into: main
  • Upgrade googletest to 1.17.0.bcr.2
EXPERIMENTAL DO NOT MERGE - rules_cc update
  • Schedule: ["at any time"]
  • Branch name: renovate/rules_cc-0.x
  • Merge into: main
  • Upgrade rules_cc to 0.2.17
EXPERIMENTAL DO NOT MERGE - score_docs_as_code update
  • Schedule: ["at any time"]
  • Branch name: renovate/score_docs_as_code-2.x
  • Merge into: main
  • Upgrade score_docs_as_code to 2.3.3
EXPERIMENTAL DO NOT MERGE - aspect_rules_lint update
  • Schedule: ["at any time"]
  • Branch name: renovate/aspect_rules_lint-1.x
  • Merge into: main
  • Upgrade aspect_rules_lint to 1.13.0
EXPERIMENTAL DO NOT MERGE - buildifier_prebuilt update
  • Schedule: ["at any time"]
  • Branch name: renovate/buildifier_prebuilt-8.x
  • Merge into: main
  • Upgrade buildifier_prebuilt to 8.5.1.2
EXPERIMENTAL DO NOT MERGE - rules_python update
  • Schedule: ["at any time"]
  • Branch name: renovate/rules_python-1.x
  • Merge into: main
  • Upgrade rules_python to 1.9.0
EXPERIMENTAL DO NOT MERGE - score_tooling update
  • Schedule: ["at any time"]
  • Branch name: renovate/score_tooling-1.x
  • Merge into: main
  • Upgrade score_tooling to 1.2.0
EXPERIMENTAL DO NOT MERGE - toolchains_llvm update
  • Schedule: ["at any time"]
  • Branch name: renovate/toolchains_llvm-1.x
  • Merge into: main
  • Upgrade toolchains_llvm to 1.7.0
EXPERIMENTAL DO NOT MERGE - aspect_rules_lint update
  • Schedule: ["at any time"]
  • Branch name: renovate/aspect_rules_lint-2.x
  • Merge into: main
  • Upgrade aspect_rules_lint to 2.5.0
EXPERIMENTAL DO NOT MERGE - score_docs_as_code update
  • Schedule: ["at any time"]
  • Branch name: renovate/score_docs_as_code-4.x
  • Merge into: main
  • Upgrade score_docs_as_code to 4.0.1

🚸 PR creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prHourlyLimit for details.


❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.


This PR has been generated by Renovate Bot.

@github-actions
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]
2026/04/16 21:47:13 Downloading https://releases.bazel.build/8.3.0/release/bazel-8.3.0-linux-x86_64...
Extracting Bazel installation...
Starting local Bazel server (8.3.0) and connecting to it...
INFO: Invocation ID: b9fffba1-e3f5-41f8-b827-3fec96a97b5c
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
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
Analyzing: target //:license-check (1 packages loaded, 0 targets configured)
Analyzing: target //:license-check (1 packages loaded, 0 targets configured)

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

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

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

Analyzing: target //:license-check (144 packages loaded, 1319 targets configured)

Analyzing: target //:license-check (145 packages loaded, 2378 targets configured)

Analyzing: target //:license-check (152 packages loaded, 2804 targets configured)

Analyzing: target //:license-check (152 packages loaded, 2804 targets configured)

Analyzing: target //:license-check (152 packages loaded, 2804 targets configured)

Analyzing: target //:license-check (153 packages loaded, 2805 targets configured)

Analyzing: target //:license-check (155 packages loaded, 4811 targets configured)

Analyzing: target //:license-check (156 packages loaded, 4935 targets configured)

Analyzing: target //:license-check (157 packages loaded, 5055 targets configured)

Analyzing: target //:license-check (157 packages loaded, 5055 targets configured)

Analyzing: target //:license-check (157 packages loaded, 5055 targets configured)

Analyzing: target //:license-check (157 packages loaded, 5055 targets configured)

Analyzing: target //:license-check (157 packages loaded, 5055 targets configured)

INFO: Analyzed target //:license-check (158 packages loaded, 6990 targets configured).
[9 / 13] JavaToolchainCompileClasses external/rules_java+/toolchains/platformclasspath_classes; 0s disk-cache
INFO: From Generating Dash formatted dependency file ...:
INFO: Successfully converted 2 packages from Cargo.lock to bazel-out/k8-fastbuild/bin/formatted.txt
[11 / 13] 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: 202.344s, Critical Path: 2.40s
INFO: 13 processes: 9 internal, 3 processwrapper-sandbox, 1 worker.
INFO: Build completed successfully, 13 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>]

@github-actions
Copy link
Copy Markdown

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

@eclipse-score-bot eclipse-score-bot deleted the renovate/configure branch April 16, 2026 22:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Development

Successfully merging this pull request may close these issues.

2 participants