Skip to content

Bumps directs deps - baselibs and communication #87

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
RSingh1511 wants to merge 5 commits into
base: main
Choose a base branch
from
Open

Bumps directs deps - baselibs and communication #87

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
ab24e33
fix: bump score_baselibs to 0.2.5 and score_communication to 0.1.4
RSingh1511 Apr 15, 2026
fb7374d
Merge branch 'main' into jiwe_bumps_direct_deps
RSingh1511 Apr 21, 2026
b4e7dbb
remove unnecessary git_override for score_baselibs
RSingh1511 Apr 23, 2026
d36fa4d
fix: bump score_baselibs 0.2.6, update recorder_interface path
RSingh1511 Apr 23, 2026
4584365
Pin score_communication to working commit
RSingh1511 Apr 24, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 15 additions & 8 deletions MODULE.bazel
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,13 @@ bazel_dep(name = "score_rust_policies", version = "0.0.3")
bazel_dep(name = "score_process", version = "1.4.3", dev_dependency = True)
bazel_dep(name = "score_platform", version = "0.5.3", dev_dependency = True)

# Pin score_process to 1.4.3 — v1.4.4 added folder_templates with doc__ IDs
# that collide with score_platform's own IDs (upstream bug in process_description).
Copy link
Copy Markdown
Contributor

@rmaddikery rmaddikery Apr 23, 2026

Choose a reason for hiding this comment

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

Please link/add the issue id here

Copy link
Copy Markdown
Contributor Author

@RSingh1511 RSingh1511 Apr 23, 2026

Choose a reason for hiding this comment

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

Please link/add the issue id here

Fixed in eclipse-score/score#2657
but not yet released (latest is v0.5.4, fix is only on main).
Remove after score_platform v0.7 release.

single_version_override(
module_name = "score_process",
version = "1.4.3",
)

# Toolchains and extensions
bazel_dep(name = "score_bazel_cpp_toolchains", version = "0.2.2", dev_dependency = True)
bazel_dep(name = "score_toolchains_rust", version = "0.4.0", dev_dependency = True)
Expand Down Expand Up @@ -92,17 +99,17 @@ python.toolchain(

bazel_dep(name = "googletest", version = "1.17.0.bcr.1")
bazel_dep(name = "rapidjson", version = "1.1.0")
bazel_dep(name = "score_baselibs", version = "0.2.4")
git_override(
module_name = "score_baselibs",
commit = "4b67ce1929575801405c77f7e3c79ab36156a976",
remote = "https://github.com/eclipse-score/baselibs.git",
)
bazel_dep(name = "score_baselibs", version = "0.2.5")
bazel_dep(name = "score_communication", version = "0.1.4")

bazel_dep(name = "score_communication", version = "0.1.2")
# TODO: Remove once score_communication fixes the visibility issue in a new release.
# score_communication v0.2.0 (latest registry release) exposes internal targets
# (e.g. @score_logging) via visibility labels that are not resolvable from this
# repo, causing "no such target" errors at analysis time. This override pins to
# commit 406aaef (post-0.1.4), which does not have the broken visibility labels.
git_override(
module_name = "score_communication",
commit = "56448a5589a5f7d3921b873e8127b824a8c1ca95",
commit = "406aaef064f6baf8a6a09bfb3523e75bdaced916",
remote = "https://github.com/eclipse-score/communication.git",
)

Expand Down
Loading
Loading