Skip to content

chore(devcontainer): declare SCORE devcontainer dependency - #209

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

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

Conversation

@eclipse-score-bot

@eclipse-score-bot eclipse-score-bot commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Policy

score-devcontainer-dependency-alignment

Declare the SCORE devcontainer as a direct Bazel dependency using the
repository's Dockerfile image version.

Why this repository?

This repository matches this policy because MODULE.bazel exists and the policy value devcontainer_version is available because .devcontainer/Dockerfile contains exactly one ghcr.io/eclipse-score/devcontainer:vX.Y.Z FROM instruction.

Changes

  • MODULE.bazel: add Bazel dependency 'score_devcontainer' at version '1.8.0'
    • Declare the SCORE devcontainer as a direct Bazel dependency.
  • MODULE.bazel.lock: Regenerate MODULE.bazel.lock with bazel mod deps.

Tool revision

Generated from eclipse-score/tools at commit 5934dc0.


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 4, 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: 3ceb9c9d-c057-490d-9bc3-f94345602e6f
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
WARNING: For repository 'platforms', the root module requires module version platforms@1.0.0, but got platforms@1.1.0 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'score_platform', the root module requires module version score_platform@0.7.1, but got score_platform@0.7.2 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'rules_oci', the root module requires module version rules_oci@2.2.7, but got rules_oci@2.3.0 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'score_devcontainer', the root module requires module version score_devcontainer@1.8.0, but got score_devcontainer@1.11.0 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: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Loading: 
Loading: 3 packages loaded
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/time/time/BUILD
ERROR: no such target '//:license-check': target 'license-check' not declared in package '' defined by /home/runner/work/time/time/BUILD
INFO: Elapsed time: 15.065s
INFO: 0 processes.
ERROR: Build did NOT complete successfully
ERROR: Build failed. Not running target

@eclipse-score-bot
eclipse-score-bot force-pushed the repo-policy-sync/score-devcontainer-dependency-alignment branch from a1b2e34 to 7252e45 Compare September 9, 2026 01:13
@eclipse-score-bot
eclipse-score-bot force-pushed the repo-policy-sync/score-devcontainer-dependency-alignment branch from 7252e45 to 5a9a597 Compare September 22, 2026 09:18

This branch has not been deployed

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

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

1 participant