Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

chore: Update and release workspace members for Stackable Release 26.11.0

Ouverte
  • Quelque chose ne va pas ?
#1,305 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
25/100
Type d'issue
Refactorisation
Clarté
Clairement spécifiée
Activité
Active
Stack technique
rust
Domaine
build-system, devops, release

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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
Langage dominant
Rust
Étoiles
169
Forks
20
Merge moyen
1 j 5 h
PR mergées (30 j)
22

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de stackabletech/operator-rs

Toutes les issues de stackabletech/operator-rs

Issues similaires

Plus d'issues Rust

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.