Hacktoberfest 2026：維護者為十月標記出來的 issue，仍然開放、適合新手。 瀏覽 Hacktoberfest issue

chore: Update and release workspace members for Stackable Release 26.11.0

未關閉
  • 哪裡不對？
#1,305 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
25/100
Issue 類型
重構
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
rust
領域
build-system, devops, release

研究方向

Start with the listed workflow files, rust-toolchain.toml, .pre-commit-config.yaml, .vscode/settings.json, workspace Cargo.toml files, and the two release scripts. Follow the checklist to update Rust and dependencies, resolve resulting code changes, verify crate versions, and push release tags; done means the workspace members and tooling are updated and the release tags are pushed. This spans release coordination and downstream compatibility checks.

由索引模型根據 Issue 內容生成。

描述

epic

Part of https://github.com/stackabletech/issues/issues/889.

[!NOTE]
During a Stackable release we update all dependencies in the operator-rs
repository. After these bumps, each workspace member is released using an
appropriate SemVer version. Later, each product operator repository can then
use the updates crates.

Replace the items in the task lists below with the applicable Pull Requests

  • Update Rust version and workflow actions, see below for more details.
  • Update Rust dependencies, see below for more details.
  • Adjust and then verify crate versions using .scripts/verify_crate_versions.sh.
  • Push the release tags using .scripts/tag_and_push_release.sh.

Update Rust Version and Workflow Actions

[!NOTE]
The PR is usually titled: chore: Bump Rust version and workflow actions

  • Adjust the version of the channel in the rust-toolchain.toml file. See https://releases.rs.
  • Adjust the version RUST_TOOLCHAIN_VERSION in the workflows:
    - .github/workflows/build.yml
    - .github/workflows/pre_commit.yaml
    - .github/workflows/publish-docs.yaml
  • Also adjust the nightly Rust toolchain version used for formatting (this should be kept in
    sync across here, operator-templating and docker-images).
    - .github/workflows/pre_commit.yaml
    - .pre-commit-config.yaml
    - .vscode/settings.json
  • Add a changelog entry.
  • Update any actions (using the Git commit hash) in the workflows. Hint: Also make sure that the
    cargo-udeps action is up-to-date, otherwise the CI might report errors.

Update Rust Dependencies

[!NOTE]
This PR is usually titled: chore: Bump Rust dependencies

  • Bump minor versions of dependencies in the Cargo.toml manifest.
  • Then run the cargo update command.
  • Fix any code which needs updating due to the dependency bumps.
  • Locally update any product operator to identify any breaking changes downstream.
    - Hint: Use the [patch."https://github.com/..."] mechanism to temporarily override the
    dependency.
  • Add a changelog entry if required.

Adjust and Verify Crate Versions

[!WARNING]
Currently, all workspace members use 0.X.Y versions. This means we can
introduce breaking changes in any version without needing to bump the major
level. But we still have the following rules:

  • Breaking changes (internally and externally) will bump the minor level of
    the version, so 0.X.Y becomes 0.X+1.Y.
  • All other non-breaking changes will bump the patch level of the version, so
    0.X.Y becomes 0.X.Y+1.

[!NOTE]
The PR is usually titled: chore: Release workspace members

  • Bump the crate versions in their appropriate Cargo.toml manifests.
  • Verify the previous step using .scripts/verify_crate_versions.sh.

Tooling updates

[!TIP]

Cutting a release and using that in docker-images.

  • containerdebug
  • config-utils
主要語言
Rust
星號
169
分支
20
平均合併
1 天 6 小時
30 天內合併 PR
21

環境準備

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

stackabletech/operator-rs 的其他 Issue

查看 stackabletech/operator-rs 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。