Hacktoberfest 2026:メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

chore: Update and release workspace members for Stackable Release 26.11.0

オープン
#1,305 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
リファクタリング
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
rust

調査の方向性

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日 2時間
マージ済み PR(30日)
25

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

stackabletech/operator-rs のほかの issue

stackabletech/operator-rs の issue をすべて見る

似ている issue

Rust の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。