Drop dev-tools base bump from 2.8.1 release

The dev-tools 1.16.1->1.17.0 base-image fix (for the Rust 1.95.0 musl
cross-compile) moves to the CI PR #165, which also adds a build-on-PR
check. 2.8.1 is now purely the version bump + CRD lifecycle fix.

Author: pcholakov

docker/Dockerfile

@@ -1,8 +1,8 @@
-FROM --platform=$BUILDPLATFORM ghcr.io/restatedev/dev-tools:1.17.0 AS planner
+FROM --platform=$BUILDPLATFORM ghcr.io/restatedev/dev-tools:1.16.1 AS planner
 COPY .. .
 RUN just chef-prepare
 
-FROM --platform=$BUILDPLATFORM ghcr.io/restatedev/dev-tools:1.17.0 AS base
+FROM --platform=$BUILDPLATFORM ghcr.io/restatedev/dev-tools:1.16.1 AS base
 COPY --from=planner /restate/recipe.json recipe.json
 COPY ../justfile justfile
 

release-notes/v2.8.1.md

@@ -4,8 +4,6 @@ This is a bug fix release, see [v2.8.0 release notes](https://github.com/restate
 
 ## Bug Fixes
 
-- **Fix: the release build now works with the Rust 1.95.0 toolchain** — the release Docker base image is bumped from `ghcr.io/restatedev/dev-tools:1.16.1` to `1.17.0`, which bakes the Rust 1.95.0 toolchain and its musl standard library needed by the musl cross-compile.
-
 - **Fix: templated CRDs are now retained on uninstall** — with the default `installCrds: true`, the chart's CRDs (`RestateCluster`, `RestateDeployment`, `RestateCloudEnvironment`) now carry the `helm.sh/resource-policy: keep` annotation. They are no longer deleted on `helm uninstall` or when switching to `installCrds: false`, so your custom resources are not cascade-deleted. This corrects the uninstall caveat noted in v2.8.0.
 
 ## Upgrading an existing (<= 2.7) install