Update dependency score_bazel_cpp_toolchains to v1

[eclipse-score-bot]

This PR contains the following updates:

Package	Type	Update	Change
score_bazel_cpp_toolchains	bazel_dep	major	0.5.4 → 1.0.3

---

Release Notes

eclipse-score/bazel_cpp_toolchains (score_bazel_cpp_toolchains)

v1.0.3

What's Changed

• Add Ebclfsa 2.0.0-beta2 by @​lurtz in #​131

New Contributors

• @​lurtz made their first contribution in #​131

Full Changelog: eclipse-score/bazel_cpp_toolchains@v1.0.2...v1.0.3

v1.0.2

What's Changed

• fix(qnx): reorder user_link_flags after libraries_to_link by @​nradakovic in #​128

Full Changelog: eclipse-score/bazel_cpp_toolchains@v1.0.0...v1.0.2

v1.0.1

What's Changed

• Add extended documentation about toolchain model by @​nradakovic in #​64
• docs: Provide additional information in docs by @​nradakovic in #​65
• Update platform to new version by @​nradakovic in #​66
• refactor: extract constants and helpers for better maintainability by @​nradakovic in #​70
• Reorganize Tests and Documentation Structure by @​nradakovic in #​93
• Tests and documentation update by @​nradakovic in #​97
• Add list of toolchain features by @​nradakovic in #​98
• docs: add QNX toolchain integration contract by @​nradakovic in #​99
• Enable no_legacy_features on the Linux and QNX toolchains by @​nradakovic in #​95
• Add downstream migration guide for the explicit-feature model by @​nradakovic in #​101
• Add guardrail against Bazel legacy C++ feature regressions by @​nradakovic in #​102
• Update Bazel version to 8.4.2 by @​nradakovic in #​105
• Add pic feature to QNX cc_toolchain_config by @​nradakovic in #​108
• Rename workflow file ebclfsa by @​nradakovic in #​109
• Add QNX build and test workflow with emulated execution by @​nradakovic in #​106
• Add feature injection by @​nradakovic in #​52
• Enforce fully_static_link check regardless of NDEBUG by @​nradakovic in #​112
• Extract common explicit feature definitions into a shared module by @​armando-martins in #​113
• bump autosd toolchain to 0.0.2 by @​odra in #​115
• Add config for GCC 15.3.0 by @​nradakovic in #​117
• chore(bazel): require Bazel 8.6.0 by @​AlexanderLanin in #​116
• Revert "Extract common toolchain features (#​85) (#​113)" by @​nradakovic in #​120
• Bug fix for output exec path by @​nradakovic in #​121
• Nira feature reorder by @​nradakovic in #​123
• Add compiler warnings override test. by @​nradakovic in #​126
• Remove all warnings features by @​nradakovic in #​122

New Contributors

• @​armando-martins made their first contribution in #​113
• @​AlexanderLanin made their first contribution in #​116

Full Changelog: eclipse-score/bazel_cpp_toolchains@v0.5.4...v1.0.1

We are re-releasing new version due to issues with Bazel Registry.

v1.0.0

What's Changed

• Add extended documentation about toolchain model by @​nradakovic in #​64
• docs: Provide additional information in docs by @​nradakovic in #​65
• Update platform to new version by @​nradakovic in #​66
• refactor: extract constants and helpers for better maintainability by @​nradakovic in #​70
• Reorganize Tests and Documentation Structure by @​nradakovic in #​93
• Tests and documentation update by @​nradakovic in #​97
• Add list of toolchain features by @​nradakovic in #​98
• docs: add QNX toolchain integration contract by @​nradakovic in #​99
• Enable no_legacy_features on the Linux and QNX toolchains by @​nradakovic in #​95
• Add downstream migration guide for the explicit-feature model by @​nradakovic in #​101
• Add guardrail against Bazel legacy C++ feature regressions by @​nradakovic in #​102
• Update Bazel version to 8.4.2 by @​nradakovic in #​105
• Add pic feature to QNX cc_toolchain_config by @​nradakovic in #​108
• Rename workflow file ebclfsa by @​nradakovic in #​109
• Add QNX build and test workflow with emulated execution by @​nradakovic in #​106
• Add feature injection by @​nradakovic in #​52
• Enforce fully_static_link check regardless of NDEBUG by @​nradakovic in #​112
• Extract common explicit feature definitions into a shared module by @​armando-martins in #​113
• bump autosd toolchain to 0.0.2 by @​odra in #​115
• Add config for GCC 15.3.0 by @​nradakovic in #​117
• chore(bazel): require Bazel 8.6.0 by @​AlexanderLanin in #​116
• Revert "Extract common toolchain features (#​85) (#​113)" by @​nradakovic in #​120
• Bug fix for output exec path by @​nradakovic in #​121
• Nira feature reorder by @​nradakovic in #​123
• Add compiler warnings override test. by @​nradakovic in #​126
• Remove all warnings features by @​nradakovic in #​122

New Contributors

• @​armando-martins made their first contribution in #​113
• @​AlexanderLanin made their first contribution in #​116

Full Changelog: eclipse-score/bazel_cpp_toolchains@v0.5.4...v1.0.0

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by #infrastructure automation. Contact us if you have any questions or feedback.

[eclipse-score-bot]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: MODULE.bazel.lock

Command failed: bazel mod deps --lockfile_mode=update
 no actions running
ERROR: 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
ERROR: Direct dependency check failed.

[eclipse-score-bot]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[limdor]

This comment is unfortunately no longer true. If they do not provide warnings enabled by default, I would right now just not use them and define our own set of warnings, in this way we can have a mapping with our MISRA GEP.
The goal IMHO would be that S-CORE has a global MISRA GEP and then based on that score_bazel_cpp_toolchains could provide the warning groups. Until that is there, it does not make sense that we have a communication MISRA GEP, but the warnings are defined somewhere else. Otherwise it is quite easy that we end up with a MISRA GEP and a toolchain not in sync.