Skip to content

Add release trigger to docs workflow#7

Draft
Saumya-R wants to merge 3 commits into
eclipse-score:mainfrom
qorix-group:saumya_doc_gen_release_tag
Draft

Add release trigger to docs workflow#7
Saumya-R wants to merge 3 commits into
eclipse-score:mainfrom
qorix-group:saumya_doc_gen_release_tag

Conversation

@Saumya-R
Copy link
Copy Markdown

No description provided.

Chahult and others added 3 commits March 16, 2026 08:40
…score#4)

* feat: add build acceptlist CI check for CfgD & CfgP targets

* fix: apply buildifier formatting and fix copyright headers

---------

Co-authored-by: chahul.turkar <chahul.turkar@bti.bmwgroup.com>
* feat: set CI configuration for config_management

- Add 4 CI workflows: tests.yml, static-analysis.yml,
  bzlmod-lock-check.yml, score-pr-checks.yml
- Update .bazelrc: score_communication tracing stub flag,
  score_variant=True, host_gcc config using @gcc_toolchain
- Align MODULE.bazel deps with OSS mirror (rules_python 1.8.3,
  platforms 1.0.0, rules_rust 0.68.1-score, rules_cc 0.2.16,
  aspect_rules_lint 2.0.0, score_logging 0.1.0)
- Pin score_baselibs to commit 052c2f271be4 (avoids non-dev
  toolchains_llvm conflict), add rules_boost archive_override
- Add score_docs_as_code, score_crates single_version_overrides
- Add score_lifecycle_health dep
- Remove MODULE.bazel.lock from .gitignore, commit fresh lockfile
- Fix copyright header in tests/rust/test_main.rs

* chore: configure CODEOWNERS with project maintainers

* chore: address review comments

- CODEOWNERS: apply suggested maintainers list
- workflows: replace ubuntu-latest with ubuntu-24.04 in all jobs

---------

Co-authored-by: chahul.turkar <chahul.turkar@bti.bmwgroup.com>
Signed-off-by: Saumya Rai <saumya.rai@qorix.ai>
@Saumya-R Saumya-R requested a review from PiotrKorkus April 24, 2026 06:12
@github-actions
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]
2026/04/24 06:12:55 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: de506054-1b21-45d4-a816-fe55277bc224
Computing main repo mapping: 
DEBUG: Rule 'rules_boost+' indicated that a canonical reproducible form can be obtained by modifying arguments integrity = "sha256-LTilyiMMjpYyAi1PW+8RycyAEHy9clo7915R0Bchb2E="
DEBUG: Repository rules_boost+ instantiated at:
  <builtin>: in <toplevel>
Repository rule http_archive defined at:
  /home/runner/.bazel/external/bazel_tools/tools/build_defs/repo/http.bzl:394:31: in <toplevel>
Computing main repo mapping: 
DEBUG: Rule 'score_lifecycle_health+' indicated that a canonical reproducible form can be obtained by modifying arguments commit = "50ca5ca3d635ed69b11f9f348cc1d9ed6dbefa2a" and dropping ["branch"]
DEBUG: Repository score_lifecycle_health+ instantiated at:
  <builtin>: in <toplevel>
Repository rule git_repository defined at:
  /home/runner/.bazel/external/bazel_tools/tools/build_defs/repo/git.bzl:208:33: in <toplevel>
DEBUG: Rule 'score_communication+' indicated that a canonical reproducible form can be obtained by modifying arguments commit = "b9ef6e2eea8f0db5c8356dbd8b1dcb1463f86d50" and dropping ["branch"]
DEBUG: Repository score_communication+ instantiated at:
  <builtin>: in <toplevel>
Repository rule git_repository defined at:
  /home/runner/.bazel/external/bazel_tools/tools/build_defs/repo/git.bzl:208:33: in <toplevel>
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
ERROR: Error computing the main repository mapping: score_communication@_ depends on boost.interprocess@1.83.0.bcr.4 with compatibility level 0, but score_baselibs@_ depends on boost.interprocess@1.87.0 with compatibility level 108700 which is different

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants