Bazel version compliance 9.x (PoC)
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 20/100
- Issue 類型
- 功能
- 描述清晰度
- 需要釐清
- 活躍度
- 活躍
- 領域
- build-system
研究方向
The issue names no files, tests, or entry points. Start by clarifying the scope of Bazel 9.x compliance and defining the proof-of-concept acceptance criteria; the work is done when those criteria are explicit and demonstrably met.
由索引模型根據 Issue 內容生成。
描述
Summary
Prepare this repository for Bazel 9 by investigating compatibility issues and applying the changes needed to use Bazel 9 in a dedicated feature branch.
This is a preparation effort only. The project must not switch its default or supported Bazel version to Bazel 9 until the wider project has completed its migration.
Motivation
Identifying and resolving Bazel 9 compatibility issues early will make the eventual project-wide migration easier and reduce the risk of a disruptive version upgrade. A dedicated feature branch lets us explore the required changes without changing the Bazel version used by the main development workflow.
Scope
- Create and maintain a feature branch for the Bazel 9 proof of concept.
- Attempt to build and test this repository with Bazel 9.
- Identify and fix compatibility issues in this repository that prevent Bazel 9 usage.
- Validate the changes with the relevant build and test workflows.
- Document remaining blockers, workarounds, and any changes that depend on other parts of the project migrating.
- Keep the existing default Bazel version and main development workflow unchanged.
Acceptance criteria
- Bazel 9 compatibility work is isolated to a dedicated feature branch.
- The repository can be built and the relevant tests can be run with Bazel 9, or remaining blockers are clearly documented.
- Changes required for Bazel 9 do not unintentionally break the currently supported Bazel version.
- The repository’s default Bazel version and normal development workflow are not switched to Bazel 9 as part of this PoC.
- The findings and any outstanding dependencies for the wider project migration are documented.
Out of scope
- Switching the main branch to Bazel 9.
- Coordinating or completing the migration of the whole project to Bazel 9.
- Addressing unrelated build or test issues.
Exit condition
Treat this PoC as preparation for a future project-wide migration. Do not promote the Bazel 9 changes to the normal development workflow until the wider project is ready to switch.
- 主要語言
- Starlark
- 星號
- 2
- 分支
- 11
- 平均合併
- 11 小時 27 分鐘
- 30 天內合併 PR
- 9
環境準備
在瀏覽器裡用你自己的 GitHub 帳號啟動這個專案的開發容器。
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 沒有貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
eclipse-score/bazel_cpp_toolchains 的其他 Issue
-
score_bazel_cpp_toolchains v1.0.4 is incompatible with rules_cc > 0.2.17 (persistency uses 0.2.22 already) in clarification with @nradakovic if we downgrade or there is another option可能已有人在做 @nradakovic 於 4 天前認領。 未關閉
eclipse-score/bazel_cpp_toolchains#160 · 2 則留言 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
action config documentation feature p3
難度 5/5 一週以上 新手友好度 15/100
eclipse-score/bazel_cpp_toolchains#158 ·
維護者通常 1 天內回覆
-
refinement needed
難度 5/5 一週以上 新手友好度 15/100
eclipse-score/bazel_cpp_toolchains#156 ·
維護者通常 1 天內回覆
-
refinement needed
難度 5/5 一週以上 新手友好度 20/100
eclipse-score/bazel_cpp_toolchains#155 ·
維護者通常 1 天內回覆
-
Add regression test for sysroot flags on assembly actions可能已有人在做 @nradakovic 於 27 天前認領。 未關閉
eclipse-score/bazel_cpp_toolchains#147 · 已指派 1 人 ·
維護者通常 1 天內回覆
查看 eclipse-score/bazel_cpp_toolchains 的全部 Issue
相似的 Issue
-
[Bug] Dev image build fails: `npm install` in the root Dockerfile runs out of memory (exit 134)可能已有人在做 @andest01 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 75/100
維護者通常 1 天內回覆
-
100 points complexity:trivial drips-wave enhancement good first issue trivial
難度 2/5 1-3 小時 新手友好度 68/100
sorotrail/SoroBeacon#438 ·
維護者通常 1 天內回覆
-
area: backend bug
難度 2/5 1-3 小時 新手友好度 68/100
snapotter-hq/SnapOtter#2415 ·
維護者通常 1 天內回覆
-
100 points complexity:trivial drips-wave good first issue test trivial
難度 2/5 1-3 小時 新手友好度 76/100
維護者通常 1 天內回覆
-
enhancement good first issue help wanted
難度 2/5 1-3 小時 新手友好度 85/100
維護者通常 1 天內回覆