Bump to 3.2 - #3214
Merged
Merged
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Three consumer-visible changes this cycle that a build bump would under-signal:
TargetFrameworks(Drop net6.0 from TargetFrameworks #3208). Anyone still targeting it doesn't get a worse version, they get no version.System.IO.Hashing's declared floor moved10.0.5→10.0.12(Bump SourceLink past CVE-2026-62900, and System.IO.Hashing with it #3210), on every target framework.ScriptEvaluateReadOnlynow genuinely sendsEVAL_ROwhere the server (7.0+) and command map allow it — so a script that writes on that API starts being rejected where plainEVALused to let it through.Plus the new surface from #3201 —
RespResult,RedisKeyOrValue, the*Respfamily, and the un-gatedRespReaderAPI — additive, but substantial.assemblyVersionstays at 3.0Deliberately. It's decoupled from the package version precisely so a minor bump isn't a binding break; moving it would be one for anyone with a compiled reference or a binding redirect. Confirmed against a local pack:
versionHeightOffsetremovedIt was scoped to 3.1 via
versionHeightOffsetAppliesTo, so it stopped applying the moment the version changed — dead config rather than a live adjustment. Verified the computed version is byte-identical with and without it, so this is a tidy-up, not a behaviour change.The version height restarts at 0 for the new minor, which is why the first build is
3.2.0rather than continuing the 3.1 height.