Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

chore: Update and release workspace members for Stackable Release 26.11.0

Offen
  • Stimmt etwas nicht?
#1,305 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
25/100
Issue-Typ
Refactoring
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
rust
Bereich
build-system, devops, release

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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
Vorherrschende Sprache
Rust
Sterne
169
Forks
20
Ø Merge
1 T. 2 Std.
Gemergte PRs (30 T.)
25

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus stackabletech/operator-rs

Alle Issues in stackabletech/operator-rs

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.