chore: Release crates

[NickLarsenNZ]

Description

• stackable-certs-0.2.0
• stackable-operator-derive-0.2.0
• stackable-operator-0.66.0
• stackable-webhook-0.2.0

---

Operator upgrade instructions

Prerequisites

These appear to have already been done as part of the post-release tasks

• [x] operator-templating: bump the rust version in config/rust.yaml to 1.77 (https://github.com/stackabletech/operator-templating/pull/350)
  • [x] Generate the operator-templating PRs for all operators
• [x] docker-images: bump rust version in ubi8-rust-builder/Dockerfile (https://github.com/stackabletech/docker-images/pull/601)
• [x] Create tags for each crate (after merge)

  git checkout main
  git pull
  git log -1 --oneline # ensure the HEAD is the merge commit
  git tag -s stackable-certs-0.2.0
  git tag -s stackable-operator-derive-0.2.0
  git tag -s stackable-operator-0.66.0
  git tag -s stackable-webhook-0.2.0
  git push --tags

For each operator

• [x] Merge the generated operator-templating PRs (with the hash: ded546b)
• [ ] Fix the stackable-operator import tag in Cargo.toml (eg: 0.65.0 -> stackable-operator-0.66.0)
• [ ] Fix any of the other imports from the same repo based on their new tags (eg: stackable-certs-0.2.0)

Definition of Done Checklist

• Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant
• Please make sure all these things are done and tick the boxes

# Reviewer
- [ ] Code contains useful comments
- [ ] (Integration-)Test cases added
- [ ] Documentation added or updated
- [ ] Changelog updated
- [ ] Cargo.toml only contains references to git tags (not specific commits or branches)

# Acceptance
- [ ] Feature Tracker has been updated
- [ ] Proper release label has been added

[NickLarsenNZ]

@Techassi, can you please suggest what the new tags should look like?

Considering how they will look in the downstream crates:

stackable-operator = { git = "https://github.com/stackabletech/operator-rs.git", tag = "stackable-operator0.66.0" }

Depending on your response, the examples in the PR description might need updating.

[Techassi]

@Techassi, can you please suggest what the new tags should look like?

Considering how they will look in the downstream crates:

stackable-operator = { git = "https://github.com/stackabletech/operator-rs.git", tag = "stackable-operator0.66.0" }

Depending on your response, the examples in the PR description might need updating.

I would use stackable-<CRATE>-<VERSION>, because we already use the same format in stackable-cockpit (The tag looks like this: stackablectl-24.3.1)

---

Regarding how it will look in the downstream crates: For now, the "awkward" tag is mostly fine, because you only ever need to change the suffixed version. At some point in the future we want to publish these crates on crates.io anyway. The dependencies would then look like this:

stackable-operator = "0.66.0"
stackable-certs = "0.2.0"

Additionally, the tag format will most likely also change when we eventually publish the crates and they might get renamed.