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 天 5 小时
30 天内合并 PR
22

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

stackabletech/operator-rs 的其他 Issue

查看 stackabletech/operator-rs 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。