Skip to content

release: 0.13.233 - #233

Merged
MDA2AV merged 2 commits into
mainfrom
release/0.13.233
Sep 13, 2026
Merged

MDA2AV merged 2 commits into
mainfrom
release/0.13.233

Conversation

@MDA2AV

@MDA2AV MDA2AV commented Sep 13, 2026

Copy link
Copy Markdown
Owner

Description

Version bump across all 12 published packages, 0.13.2250.13.233, plus the one source fix the release is blocked on.

ioxide core
ioxide.file, ioxide.httpclient, ioxide.pg, ioxide.redis, ioxide.timer clients
ioxide.http2, ioxide.http3, ioxide.nghttp2, ioxide.nghttp3, ioxide.ngtcp2 protocols
ioxide.Kestrel serving

Same set as the 0.13.225 release; Research/ is unaffected, as before.

What it ships since 0.13.225

ioxide.Kestrel would not have built

Found while checking the bump: main does not compile on the installed .NET 11 preview SDK. The BCL added System.Net.Security.TlsSessionSYSLIB5007, experimental, subject to removal — and every file importing both that namespace and ioxide.tls now sees an ambiguous TlsSession:

error CS0104: 'TlsSession' is an ambiguous reference between
              'System.Net.Security.TlsSession' and 'ioxide.tls.TlsSession'

Of the twelve packages only ioxide.Kestrel is affected — the other eleven build clean either way — so releasing without this would publish eleven packages and fail the twelfth. Ioxide.Tests.Tls hits the same thing; no other test project does.

Neither import is droppable: the Kestrel feature reads TlsCipherSuite and the three algorithm enums out of System.Net.Security, and the TLS tests use SslStream from it. So it is a using-alias:

<ItemGroup>
  <Using Include="ioxide.tls.TlsSession" Alias="TlsSession" />
</ItemGroup>

Per project rather than per file, deliberately. The compiler first reported two files; aliasing those revealed two more it had not reached (KeyAndPostureReportingTests, TruncationTests), because it stops early. One ItemGroup covers every file in the project, and a file added later cannot reintroduce it.

Compile-time only, so nothing about the shipped packages changes. A consumer that imports both namespaces will meet the same ambiguity in its own code and needs its own alias — there is nothing this side can do about that short of renaming a public type.

Verified

Solution builds with 0 errors. Ioxide.Tests.Tls: 141 passed, 0 failed, 5 skipped, 7 pending.


🤖 Generated with Claude Code

ioxide.Kestrel stopped compiling on the installed SDK. .NET 11 added
System.Net.Security.TlsSession - SYSLIB5007, experimental, subject to removal -
and every file importing both that namespace and ioxide.tls now sees an
ambiguous TlsSession.

    error CS0104: 'TlsSession' is an ambiguous reference between
                  'System.Net.Security.TlsSession' and 'ioxide.tls.TlsSession'

Neither import is droppable: the Kestrel feature reads TlsCipherSuite and the
three algorithm enums out of System.Net.Security, and the TLS tests use
SslStream from it.

The alias is per PROJECT rather than per file, because the blast radius is not
what the compiler first shows. It reported two files; aliasing those revealed
two more it had not reached - KeyAndPostureReportingTests and TruncationTests.
One ItemGroup covers every file in the project and a file added later cannot
reintroduce it.

Compile-time only, so nothing about the shipped package changes. A consumer who
imports both namespaces will meet the same ambiguity in their own code and
needs their own alias; there is nothing this side can do about that short of
renaming a public type.

Of the twelve published packages only ioxide.Kestrel was affected - the other
eleven build clean either way, as does every test project but Ioxide.Tests.Tls.

Solution builds. Tls 141 passed, 0 failed, 5 skipped, 7 pending.

Claude-Session: https://claude.ai/code/session_01A7pFfapoNSX5fm5wyiJZ4L
@MDA2AV
MDA2AV merged commit a2dbd8a into main Sep 13, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant