From 3792b3b6eeb5bfb8c346e9da8261839bd2aed0cb Mon Sep 17 00:00:00 2001 From: mgravell Date: Thu, 10 Sep 2026 11:31:54 +0100 Subject: [PATCH] Bump to 3.2 Three consumer-visible changes in this cycle that a build bump would under-signal: - net6.0 dropped from TargetFrameworks (#3208). Anyone still targeting it does not get a worse version, they get no version. - System.IO.Hashing's declared floor moved from 10.0.5 to 10.0.12 (#3210), on every target framework. - ScriptEvaluateReadOnly now genuinely sends EVAL_RO where the server and command map allow it, so a script that *writes* on that API starts being rejected on 7.0+ where plain EVAL used to let it through. Plus the new surface from #3201 - RespResult, RedisKeyOrValue, the *Resp family, and the un-gated RespReader API - which is additive but substantial. assemblyVersion stays at 3.0 deliberately: it is decoupled from the package version precisely so that a minor bump is not a binding break, and moving it would be one for anyone with a compiled reference or a binding redirect. Confirmed against a local pack - package 3.2.0, assembly still 3.0.0.0. versionHeightOffset went with it: it was scoped to 3.1 via versionHeightOffsetAppliesTo, so it stopped applying the moment the version changed. Verified the computed version is identical with and without it. --- version.json | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/version.json b/version.json index ab7b283f6..120d4645c 100644 --- a/version.json +++ b/version.json @@ -1,7 +1,5 @@ { - "version": "3.1", - "versionHeightOffset": -2, - "versionHeightOffsetAppliesTo": "3.1", + "version": "3.2", "assemblyVersion": "3.0", "publicReleaseRefSpec": [ "^refs/heads/main$",