Repository navigation
Take TelnetNegotiationCore from 2.12.0 to 4.5.2 - #67
Merged
Merged
Conversation
The 4.0 parser rewrite, the 3.0 OneOf removal and the 4.1.1 duplicate-plugin rule need no source change here. The two reflective reaches (CallbackOnByteAsync, CurrentEncoding's internal setter) and NAWSProtocol's subclassability are unchanged. 4.x needs Microsoft.Extensions.Logging.Abstractions 10.0.13, so that pin moves too. This is Phase 0 of the implementation plan: nothing else is in it, so a regression from the new parser points at one change. Later phases use the GMCP Core session, typed packages, PuebloProtocol and MCP 2.1 that this version brings. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WXyHEoxwX8GurTHxwPinQY
|
Warning Review limit reached
This review includes 2 billable files and costs up to $0.50.
Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing. Or wait 59 minutes for your next included review. View limit details
Comment |
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
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.
Requested by Grave · project thread
Phase 0 of the implementation plan. This PR changes only the version, and nothing else is in it. If the new parser causes a regression, it can only come from this change.
What changed
TelnetNegotiationCore2.12.0 → 4.5.2.Microsoft.Extensions.Logging.Abstractions10.0.2 → 10.0.13, because 4.5.2 depends on that patch and NU1605 treated the downgrade as an error.Why no source change
CallbackOnByteAsyncis stillinit-only andCurrentEncodingstill has aninternal set, so both reflective reaches inTelnetSessionstill work.NAWSProtocolis still public and non-sealed.Verification
dotnet build SharpMUTerm.slnx -c Release: 0 warnings, 0 errors.ScrollbackSpillTests.AReadOnlyCacheDirectory_DegradesToMemoryOnly. It fails because this sandbox runs as root, which ignores the read-only bit; it is unrelated to this change.UnsolicitedNegotiationTestsand the prompt tests (GA, EOR, packet-patch silence) pass unchanged.Changelog
None, because a player sees no change. This needs the
skip-changeloglabel.Generated by Claude Code