Skip to content

tracking: Update major/minor|patch versions for 26.7.0 #1479

@NickLarsenNZ

Description

@NickLarsenNZ

Caution

Blocked until the release planning meeting on 2026-05-19

Part of stackabletech/issues#847.

Tooling updates

Tip

  • Rust version bump
  • Cargo dependency bumps
  • Cutting a release and using that in docker-images.
  • containerdebug
  • config-utils

Items which don't have a tracking issue

  • protoc updated in UBI Builder Dockerfiles (The earlier the better)
  • jmx_exporter (validate via hdfs-operator smoke tests)
  • krb5
  • tools (update the versions in version.py)
  • testing-tools (update the base, maybe keycloak)
  • statsd_exporter
  • csi-provisioner for secret-operator
  • csi-provisioner for listener-operator

Note

Update the product versions based on what has been decided upon in the Product Spreadsheet1.
Follow these rules when creating the tracking issues for individual images:

  • Major/minor changes:
    • Removal and deprecation of entire major or minor version branches
    • Adding a new major/minor version (optionally marking it as LTS)
  • Patch-level changes:
    • Removal and deprecation if individual patch-level versions
    • Marking a (new) patch-level version as LTS
    • Adding a new patch-level version

Important

Replace the items in the task lists below with the subsequent tracking issue.
Remove this and the above admonitions afterwards to de-clutter the tracking issue.

Product Container Images

Footnotes

  1. Currently this is a private spreadsheet

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions