Skip to content

Update dependency score_baselibs to v0.2.14 - #37

Open
eclipse-score-bot wants to merge 1 commit into
mainfrom
renovate/score_baselibs-0.x
Open

Update dependency score_baselibs to v0.2.14#37
eclipse-score-bot wants to merge 1 commit into
mainfrom
renovate/score_baselibs-0.x

Conversation

@eclipse-score-bot

@eclipse-score-bot eclipse-score-bot commented Jun 29, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change
score_baselibs bazel_dep minor 0.1.3 → 0.2.14

Release Notes

eclipse-score/baselibs (score_baselibs)

v0.2.14

Module Name: baselibs
Release Tag: v0.2.14
Origin Release Tag: v0.2.13
Release Commit Hash: 09be72c
Release Date: 2026-09-29

Overview

The baselibs module provides a selection of basic C++ utility libraries for common use in the S-CORE project.

Disclaimer

This release is not intended for production use, as it does not include a safety argumentation or a completed safety assessment.
The work products compiled in the safety package are created with care according to the S-CORE process (https://eclipse-score.github.io/process_description/main/index.html). However, as a non-profit, open-source organization, the project cannot assume any liability for its content.

For details on the features, see https://eclipse-score.github.io/score/main/features/baselibs/index.html

Notable Changes

Breaking changes & deprecations
  • Deprecated //src Bazel aliases and the string and atomic shims in //score/memory have been removed. Consumers must use the replacement targets. #​598
  • The score::flatbuffers::LoadBuffer overload that accepted std::pmr::vector<uint8_t> now accepts score::cpp::pmr::vector<uint8_t> instead. Callers using the former type must update their containers. #​603
  • The v0.2.13 change to score::os::StatBuffer user and group IDs has been reverted because it caused other issues: st_uid and st_gid are again signed std::int64_t. The unsigned-ID fix described in the previous release notes is not present in this release. #​630
New features
  • NonRelocatableVector now provides pop_back(), clear(), and empty(). clear() destroys the elements without changing capacity. #​599
  • Linux applications can use the new, mockable score::os::Syslog wrapper for openlog, syslog, and closelog. #​502
  • score/json offers vaJson as an alternative serialization backend, selected with --//score/json:writer_library=vajson. The existing backend remains the default; vaJson emits compact JSON rather than the default backend's indented output. #​520
  • FutureCPP's score::cpp::inplace_vector range constructor now supports single-pass input iterators, and score::cpp::optional<T> can be constructed from std::optional<T>. #​613

Compatibility

The following platforms are supported using the bazel_cpp_toolchains (https://github.com/eclipse-score/bazel_cpp_toolchains):

  • x86_64-unknown-linux-gnu
  • aarch64-unknown-linux-gnu
  • x86_64-unknown-nto-qnx800
  • aarch64-unknown-nto-qnx800

Performed Verification

  • Build on all supported platforms
  • Unit test execution on all supported platforms (some test failures are expected on AArch64 and QNX targets).
  • Address and undefined behavior sanitized unit test execution
  • Leak sanitized unit test execution

Report: https://github.com/eclipse-score/baselibs/actions/runs/36578292759

Upgrade Instructions

Backward compatibility with the previous release is not guaranteed.

Contact Information

For any questions or support, please contact the Base Libs Feature Team (https://redirect.github.com/orgs/eclipse-score/discussions/1223) or raise an issue/discussion.

What's Changed

Full Changelog: eclipse-score/baselibs@v0.2.13...v0.2.14

v0.2.13

Module Name: baselibs
Release Tag: v0.2.13
Origin Release Tag: v0.2.12
Release Commit Hash: e7ddf3b
Release Date: 2026-09-17

Overview

The baselibs module provides a selection of basic C++ utility libraries for common use in the S-CORE project.

Disclaimer

This release is not intended for production use, as it does not include a safety argumentation or a completed safety assessment.
The work products compiled in the safety package are created with care according to the S-CORE process (https://eclipse-score.github.io/process_description/main/index.html). However, as a non-profit, open-source organization, the project cannot assume any liability for its content.

For details on the features, see https://eclipse-score.github.io/score/main/features/baselibs/index.html

Notable Changes

Breaking changes & deprecations
  • score/datetime_converter has been removed, completing its deprecation in v0.2.11. Use POSIX or C library time APIs where equivalent functionality is required. #​471
  • The unused score/os's cpuid, file_stream, and make_dev libraries, tests, and mocks have been removed. #​535
Coverage reporting migration
  • The LLVM source-based coverage migration announced in v0.2.12 is complete. bazel coverage --config=llvm_cov now produces one report for C++ and Rust, including line and branch data and 0% baselines for untested in-scope files. The pipeline is now supplied by score_coverage 0.2.0, which corrects source attribution and report links. #​533 #​584 #​589
New features
  • Rust applications can use a wrapper around score::cpp::stop_token, enabling integration with frameworks that require stop tokens, such as lifecycle. #​461
  • LockedPtr now provides the monadic transform and and_then operations for composing work on locked values. #​456 #​458
  • FlatBuffers JSON-schema generation now post-processes flatc output to restore rich attributes from schema-comment tokens, such as @title, and orders generated attributes deterministically. #​474
  • The OS abstraction now implements setenv and unsetenv, and the score/os:netdb Bazel target is publicly available. #​507 #​535
Bug fixes
  • score::os::StatBuffer now represents user and group IDs as unsigned 64-bit values, and FileUtils::ValidateGroup uses a matching conversion when comparing group IDs. #​563

Compatibility

The following platforms are supported using the bazel_cpp_toolchains (https://github.com/eclipse-score/bazel_cpp_toolchains):

  • x86_64-unknown-linux-gnu
  • aarch64-unknown-linux-gnu
  • x86_64-unknown-nto-qnx800
  • aarch64-unknown-nto-qnx800

Performed Verification

  • Build on all supported platforms
  • Unit test execution on all supported platforms (some test failures are expected on AArch64 and QNX targets).
  • Address and undefined behavior sanitized unit test execution
  • Leak sanitized unit test execution

Report: https://github.com/eclipse-score/baselibs/actions/runs/35227239830

Upgrade Instructions

Backward compatibility with the previous release is not guaranteed.

Contact Information

For any questions or support, please contact the Base Libs Feature Team (https://redirect.github.com/orgs/eclipse-score/discussions/1223) or raise an issue/discussion.

What's Changed

Full Changelog: eclipse-score/baselibs@v0.2.12...v0.2.13

v0.2.12

Module Name: baselibs
Release Tag: v0.2.12
Origin Release Tag: v0.2.11
Release Commit Hash: 33aad37
Release Date: 2026-08-26

Overview

The baselibs module provides a selection of basic C++ utility libraries for common use in the S-CORE project.

Disclaimer

This release is not intended for production use, as it does not include a safety argumentation or a completed safety assessment.
The work products compiled in the safety package are created with care according to the S-CORE process (https://eclipse-score.github.io/process_description/main/index.html). However, as a non-profit, open-source organization, the project cannot assume any liability for its content.

For details on the features, see https://eclipse-score.github.io/score/main/features/baselibs/index.html

Notable Changes

Breaking changes & deprecations
  • score/utils: StaticDestructionGuard<T>::GetStorage() now returns T& rather than raw StorageType&. Update consumers that reinterpret-cast its return value. The accessor now uses std::launder to access the placement-constructed object correctly under C++17 lifetime rules. #​476
  • The //:rust_coverage and //:rust_coverage_report targets, the Rust-coverage workflow, and the ferrocene-coverage configuration were removed pending migration to LLVM-based coverage after the score_tooling update. #​513
New features
  • json: deserialization errors now identify the failing struct field in UserMessage(), including missing fields, type mismatches, and nested-struct failures. #​467
Bug fixes
  • Bazel builds now retry repository downloads and use scaled network timeouts to better tolerate transient connectivity failures. #​484

Compatibility

The following platforms are supported using the bazel_cpp_toolchains (https://github.com/eclipse-score/bazel_cpp_toolchains):

  • x86_64-unknown-linux-gnu
  • aarch64-unknown-linux-gnu
  • x86_64-unknown-nto-qnx800
  • aarch64-unknown-nto-qnx800

Performed Verification

  • Build on all supported platforms
  • Unit test execution on all supported platforms (some test failures are expected on AArch64 and QNX targets).
  • Address and undefined behavior sanitized unit test execution
  • Leak sanitized unit test execution

Report: https://github.com/eclipse-score/baselibs/actions/runs/32955231366

Upgrade Instructions

Backward compatibility with the previous release is not guaranteed.

Contact Information

For any questions or support, please contact the Base Libs Feature Team (https://redirect.github.com/orgs/eclipse-score/discussions/1223) or raise an issue/discussion.

What's Changed

Full Changelog: eclipse-score/baselibs@v0.2.11...v0.2.12

v0.2.11

Module Name: baselibs
Release Tag: v0.2.11
Origin Release Tag: v0.2.10
Release Commit Hash: d6f4b39
Release Date: 2026-08-18

Overview

The baselibs module provides a selection of basic C++ utility libraries for common use in the S-CORE project.

Disclaimer

This release is not intended for production use, as it does not include a safety argumentation or a completed safety assessment.
The work products compiled in the safety package are created with care according to the S-CORE process. However, as a non-profit, open-source organization, the project cannot assume any liability for its content.

For details on the features, see https://eclipse-score.github.io/score/main/features/baselibs/index.html

Notable Changes

Completed migration: score/memory/shared moved to the https://github.com/eclipse-score/communication

Following the preparatory work announced in v0.2.10, the shared-memory implementation has now been moved out of this repository. score/memory/shared is fully migrated to score_communication; only thin migration shims remain at the previous //score/memory/shared:* labels for compatibility. Update your Bazel dependencies to score_communication and adjust include paths/namespaces accordingly. #​424 #​421

Breaking changes & deprecations
  • datetime_converter is now deprecated and will be removed in a future release. The implementation has had multiple correctness issues (most recently incorrect handling of leap seconds) and limited adoption; if you need this functionality, prefer relying directly on POSIX/libc time APIs. #​483
  • analysis/tracing: ServiceInstanceElement::element_id switched from score::cpp::variant to std::variant, continuing the interface migration started in v0.2.10. Update call sites and any code that pattern-matches on the old variant type. #​415
  • containers_rust ABI types (InlineVec, InlineQueue, InlineOption, InlineResult) dropped their T: Copy bound to support nested/movable payloads (e.g. InlineVec<InlineString<..>>). Since Rust forbids Copy + Drop, these types are no longer Copy; they implement Clone when their payload does. Memory layout (#[repr(C)]/#[repr(transparent)]) is unchanged. #​432
New features
  • result: new Rust FFI bindings (result_rs crate) let Rust code interoperate with score::Result<T>/score::result::Error across the language boundary and convert them into Rust's own Result. Companion libcpp/libcpp_derive crates model ABI-dependent C++ standard-library types (currently std::string_view and std::variant) with layout tests. #​403
  • New score/language/rust/memres Rust crate plus a C++ FFI layer let Rust code create and own score::cpp::pmr::memory_resource instances and pass them to C++, so allocations can be controlled across the language boundary, including a hermetic (no heap-fallback) mode. #​406
  • language/futurecpp was synced with the latest upstream release: score::cpp::jthread and the internal thread pool/cpu_context gained a priority_hint thread attribute. The score::cpp::variant was reimplemented as a thin wrapper around std::variant and now implicitly converts to and from std::variant; score::cpp::optional (already std::optional-backed) gained a matching implicit conversion to std::optional. Both ease migration to the std:: equivalents. #​466
  • examples/integration: added a score::Result usage demo and score_bazel_cpp_toolchains support. #​411 (closes #​363)
Bug fixes
  • memory: DataTypeSizeInfo now enforces alignof(std::max_align_t) as the maximum supported alignment; constructing it with a larger alignment now triggers a contract violation instead of silently accepting an unsupported over-aligned type. #​470
  • Rust: fixed a memory leak in score::thread's JoinInner::join(), where the result Arc was dropped via mem::forget without being read back first. Address/Undefined-Behavior/Leak sanitizer coverage (--config=asan_ubsan_lsan) was also extended to Rust builds, which had previously only covered C++. #​429
  • json/vajson: FromFile no longer parses directly off the file stream buffer, whose seek-based backtracking triggered an lseek/read syscall per seek (especially costly on QNX); it now buffers the file into memory first, like FromBuffer does, for about a 25% runtime improvement. #​431

Compatibility

The following platforms are supported using the bazel_cpp_toolchains:

  • x86_64-unknown-linux-gnu
  • aarch64-unknown-linux-gnu
  • x86_64-unknown-nto-qnx800
  • aarch64-unknown-nto-qnx800

Performed Verification

  • Build on all supported platforms
  • Unit test execution on all supported platforms (some test failures are expected on AArch64 and QNX targets).
  • Address and undefined behavior sanitized unit test execution
  • Leak sanitized unit test execution

Report: https://github.com/eclipse-score/baselibs/actions/runs/32123154514

Upgrade Instructions

Backward compatibility with the previous release is not guaranteed.

Contact Information

For any questions or support, please contact the Base Libs Feature Team (https://redirect.github.com/orgs/eclipse-score/discussions/1223) or raise an issue/discussion.

What's Changed

Full Changelog: eclipse-score/baselibs@v0.2.10...v0.2.11

v0.2.10

Module Name: baselibs
Release Tag: v0.2.10
Origin Release Tag: v0.2.9
Release Commit Hash: 174bcba
Release Date: 2026-07-28

Overview

The baselibs module provides a selection of basic C++ utility libraries for common use in the S-CORE project.

Disclaimer

This release is not intended for production use, as it does not include a safety argumentation or a completed safety assessment.
The work products compiled in the safety package are created with care according to the S-CORE process. However, as a non-profit, open-source organization, the project cannot assume any liability for its content.

For details on the features, see https://eclipse-score.github.io/score/main/features/baselibs/index.html

Notable Changes

Upcoming migration: score/memory moving to the communication repository

score/memory (in particular the shared-memory implementation under score/memory/shared) will be relocated into the communication module. This release contains only preparatory work. The actual code move is planned for the next release and will be a breaking change. Prepare to update your Bazel labels, include paths, and namespaces.

Already done in this release to enable the move:

  • AtomicIndirector moved from score/memory/shared to score/concurrency. A shim remains at //score/memory/shared:atomic_indirector (re-exporting into score::memory::shared) so unmigrated code keeps working.
    Migration: depend on //score/concurrency:atomic_indirector and use the score::concurrency namespace.
  • string_manipulation moved from score/memory to score/string_manipulation (StringLiteral, StringComparisonAdaptor, LazySplitStringView/split_string_view). Shims remain at the old //score/memory:* labels.
    Migration: depend on //score/string_manipulation and use the score::string_manipulation namespace (the deprecated StringLiteral stays in the top-level score namespace).
Breaking changes & deprecations
  • Static reflection / serialization macros renamed with a SCORE_ prefix. The old macros now emit deprecation warnings and forward to the new names:
    • STRUCT_VISITABLE → SCORE_STRUCT_VISITABLE
    • STRUCT_TRACEABLE → SCORE_STRUCT_TRACEABLE
    • MEMCPY_SERIALIZABLE → SCORE_MEMCPY_SERIALIZABLE
    • MEMCPY_SERIALIZABLE_IF → SCORE_MEMCPY_SERIALIZABLE_IF
  • result: Blank and ResultBlank are deprecated. Use void instead of score::result::Blank, and Result<void> instead of ResultBlank.
  • score::Result is now fully [[nodiscard]]. Ignoring a returned Result now produces a warning and can break -Werror builds. Consume/handle the returned value.
  • hash: public API switched from ResultBlank to Result<void>. IHashAlgorithm::Update / UpdateFromStream (and their mocks/impls) now return Result<void>. Update your overrides and MOCK_METHOD signatures.
  • analysis/tracing: generic_trace_api now uses std::variant instead of score::cpp::variant in its interface, stub, and mock signatures. Adapt call sites accordingly. More breaking changes are planned in the next release.
  • Rust components moved from //src/... to //score/.... The elementary component was renamed to allocator, plus renames on name clashes. Old //src/... labels remain as aliases with deprecation warnings; update to the new //score/... labels.
  • containers_rust: removed &'alloc from the allocator API (the lifetime was propagating unnecessarily). It is a breaking Rust API change.
New features
  • allocator: bounded lock-free allocation using an atomic bump pointer (CAS-based, capped retries for deterministic execution, graceful failure on exhaustion).
  • score::cpp::span: new size_bytes() method.
  • concurrency LockedPtr: added const overloads and [[nodiscard]] on member accessors.
  • os: new sem_timedwait_monotonic() (Linux uses sem_clockwait(), requires glibc ≥ 2.30); new QNX I/O and OCB wrappers (io_close_dup_default, io_lock_ocb_default, io_unlock_ocb_default) with mocks.
  • flatbuffers: buffer version identification and verification, plus Starlark rules that inject major/minor version into FlatBuffer binaries at build time; VersionReader gained a file_identifier sanity check; added a versioned-config example.
  • memory/shared: now rejects inter-VM shared-memory paths (the /intervm-shared-shmem/ prefix), returning nullptr and logging an error, since no portable inter-VM implementation exists yet.
Bug fixes
  • DateTimeConverter: fixed epoch-time calculation (off-by-one in date calculation, removed incorrect leap-year adjustment, improved conversion accuracy).
  • os: glibc < 2.30 warning changed to a #pragma message.
  • flatbuffers: mitigation for the transitive grpc-java dependency.
  • libacl not compiled with -fPIC causes linker failure on AArch64 PIE target #​172

Compatibility

The following platforms are supported using the bazel_cpp_toolchains:

  • x86_64-unknown-linux-gnu
  • aarch64-unknown-linux-gnu
  • x86_64-unknown-nto-qnx800
  • aarch64-unknown-nto-qnx800

Performed Verification

  • Build on all supported platforms
  • Unit test execution on all supported platforms (some test failures are expected on AArch64 and QNX targets).
  • Address and undefined behavior sanitized unit test execution
  • Leak sanitized unit test execution

Report: https://github.com/eclipse-score/baselibs/actions/runs/30361163145

Upgrade Instructions

Backward compatibility with the previous release is not guaranteed.

Contact Information

For any questions or support, please contact the Base Libs Feature Team (https://redirect.github.com/orgs/eclipse-score/discussions/1223) or raise an issue/discussion.

All changes

❗ Important

✂ PR body was truncated to here.

@github-actions

github-actions Bot commented Jun 29, 2026 •
edited
Loading

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/09/29 16:12:39 Downloading https://releases.bazel.build/8.6.0/release/bazel-8.6.0-linux-x86_64...
Extracting Bazel installation...
Starting local Bazel server (8.6.0) and connecting to it...
INFO: Invocation ID: c9d5bddd-06ef-4c75-88c4-a86075793bde
Computing main repo mapping: 
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:431:31: in <toplevel>
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: 
Computing main repo mapping: 
WARNING: For repository 'rules_python', the root module requires module version rules_python@1.4.1, but got rules_python@1.8.5 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'googletest', the root module requires module version googletest@1.17.0, but got googletest@1.17.0.bcr.2 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'rules_rust', the root module requires module version rules_rust@0.61.0, but got rules_rust@0.68.2-score in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'rules_cc', the root module requires module version rules_cc@0.2.1, but got rules_cc@0.2.17 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'score_tooling', the root module requires module version score_tooling@1.0.5, but got score_tooling@1.3.1 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'score_rust_policies', the root module requires module version score_rust_policies@0.0.3, but got score_rust_policies@0.0.5 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'aspect_rules_lint', the root module requires module version aspect_rules_lint@1.5.3, but got aspect_rules_lint@2.0.0 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'score_process', the root module requires module version score_process@1.4.2, but got score_process@2.0.2 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'score_communication', the root module requires module version score_communication@0.1.1, but got score_communication@0.1.2 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'score_bazel_platforms', the root module requires module version score_bazel_platforms@0.0.2, but got score_bazel_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 'bazel_gazelle', the root module requires module version gazelle@0.42.0, but got gazelle@0.44.0 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'score_crates', the root module requires module version score_crates@0.0.6, but got score_crates@0.0.11 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: 
Loading: 
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
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)

ERROR: Traceback (most recent call last):
	File "/home/runner/.bazel/external/score_tooling+/bazel/rules/rules_score/private/requirements.bzl", line 23, column 47, in <toplevel>
		load("@trlc//:trlc.bzl", "TrlcProviderInfo", "subrule_trlc_image_stage")
Error: file '@trlc//:trlc.bzl' does not contain symbol 'subrule_trlc_image_stage'
ERROR: /home/runner/work/scrample/scrample/BUILD:41:21: While resolving toolchains for target //:license.check.license_check (e849472): invalid registered toolchain '//bazel/rules/rules_score:sphinx_default_toolchain': error loading package '@@score_tooling+//bazel/rules/rules_score': at /home/runner/.bazel/external/score_tooling+/bazel/rules/rules_score/rules_score.bzl:49:5: at /home/runner/.bazel/external/score_tooling+/bazel/rules/rules_score/private/feature_requirements.bzl:23:6: initialization of module 'bazel/rules/rules_score/private/requirements.bzl' failed
ERROR: Analysis of target '//:license-check' failed; build aborted: Analysis failed
INFO: Elapsed time: 25.294s, Critical Path: 0.03s
INFO: 1 process: 1 internal.
ERROR: Build did NOT complete successfully
FAILED: 
ERROR: Build failed. Not running target

@eclipse-score-bot eclipse-score-bot changed the title Update dependency score_baselibs to v0.2.8 Update dependency score_baselibs to v0.2.9 Jun 30, 2026
@eclipse-score-bot
eclipse-score-bot force-pushed the renovate/score_baselibs-0.x branch from d707654 to 3354e3e Compare June 30, 2026 17:36
@eclipse-score-bot eclipse-score-bot changed the title Update dependency score_baselibs to v0.2.9 Update dependency score_baselibs to v0.2.10 Jul 28, 2026
@eclipse-score-bot
eclipse-score-bot force-pushed the renovate/score_baselibs-0.x branch from 3354e3e to ba0e944 Compare July 28, 2026 17:34
@eclipse-score-bot eclipse-score-bot changed the title Update dependency score_baselibs to v0.2.10 Update dependency score_baselibs to v0.2.11 Aug 18, 2026
@eclipse-score-bot
eclipse-score-bot force-pushed the renovate/score_baselibs-0.x branch from ba0e944 to b356957 Compare August 18, 2026 14:16
@eclipse-score-bot eclipse-score-bot changed the title Update dependency score_baselibs to v0.2.11 Update dependency score_baselibs to v0.2.12 Aug 26, 2026
@eclipse-score-bot
eclipse-score-bot force-pushed the renovate/score_baselibs-0.x branch from b356957 to 0557b2a Compare August 26, 2026 13:25
@eclipse-score-bot
eclipse-score-bot force-pushed the renovate/score_baselibs-0.x branch from 0557b2a to 934fb24 Compare September 17, 2026 16:14
@eclipse-score-bot eclipse-score-bot changed the title Update dependency score_baselibs to v0.2.12 Update dependency score_baselibs to v0.2.13 Sep 17, 2026
@eclipse-score-bot
eclipse-score-bot force-pushed the renovate/score_baselibs-0.x branch from 934fb24 to 3247b21 Compare September 29, 2026 16:12
@eclipse-score-bot eclipse-score-bot changed the title Update dependency score_baselibs to v0.2.13 Update dependency score_baselibs to v0.2.14 Sep 29, 2026

This branch is waiting to be deployed

1 waiting deployment
workflow-approval — 3247b21a Waiting Sep 29, 2026 by eclipse-score-bot via qnx-build / Build QNX target #145
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

automation renovate

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@eclipse-score-bot