Skip to content

dotnet(deps) Bump Microsoft.CodeAnalysis.CSharp to 5.9.0 - #14

Closed
dependabot[bot] wants to merge 16 commits into
masterfrom
dependabot/nuget/dotnet-0c453febc3
Closed

dotnet(deps) Bump Microsoft.CodeAnalysis.CSharp to 5.9.0#14
dependabot[bot] wants to merge 16 commits into
masterfrom
dependabot/nuget/dotnet-0c453febc3

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 22, 2026

Copy link
Copy Markdown
Contributor

Pinned Microsoft.CodeAnalysis.CSharp at 5.9.0.

Release notes

Sourced from Microsoft.CodeAnalysis.CSharp's releases.

5.0.4

Release

5.0.2

Release Notes
Install Instructions

Repos

5.0.1

Release Notes
Install Instructions

Repo

Commits viewable in compare view.

Updated Microsoft.CodeAnalysis.CSharp from 5.6.0 to 5.9.0.

Release notes

Sourced from Microsoft.CodeAnalysis.CSharp's releases.

No release notes found for this version range.

Commits viewable in compare view.

@dependabot dependabot Bot added .NET Pull requests that update .NET code dependencies Pull requests that update a dependency file labels Aug 22, 2026
tony and others added 16 commits August 22, 2026 09:37
why: Provide a fail-closed Windows query path without implying tmux
parity.

what:
- Add exact-binary psmux routing and read-only public query types
- Harden transport, control-mode, MCP streaming, jobs, and budgets
- Add native and WSL release gates, docs, examples, and tests
why: The keyless unsubscribe dropped one arbitrary reference and
returned, so a resource subscribed against a second endpoint or a
second holder kept a callback and a control client alive that no
caller could reach afterwards.

what:
- Remove every subscriber's reference to the URI within an endpoint
- Visit every endpoint rather than returning after the first match
- Cover both leaks, bounding the waits so a regression names itself
why: A socket chosen by a name factory or by LIBTMUX_SOCKET_NAME leaves
the options empty, so a job reported no socket and rejected the very
socketName its own pane was reached through.

what:
- Carry the resolved socket path alongside the resolved name
- Expose the resolved pair and record it when a job starts
- Cover a factory socket, the default name, and a relative path
why: Hashing the rows below the cursor as one block replayed every one
of them when a single row was redrawn, so tmux_wait_for_text could
match text that was already on screen before the wait began.

what:
- Record a truncated digest per row for the tracked window
- Skip each unchanged row and report only what was rewritten
- Keep the whole-suffix hash as the skip-everything fast path
- Assert the worst-case token still decodes within its ceilings
why: dotnet format rejects a property whose type wraps onto its own
line, and the shape it rewrites to reads worse than the delegate the
signature was always describing.

what:
- Declare a CommandHandler delegate for the fake endpoint's override
- Note why a cursor that moved up reports the rows above its anchor
why: Resolution already guarantees a socket name or a socket path and
never both, so choosing between them again where a job records them
restates an invariant that lives elsewhere.

what:
- Assign both recorded fields straight from the resolved pair
why: A cursor sitting on the last row records no rows below it, which
is the shape almost every tail returns and the one whose null fields
a serializer change would silently stop round-tripping.

what:
- Round-trip a cursor with nothing below it
why: An MCP result carries its cursor twice, so hex digests cost two
bytes of every response per byte recorded; at the smallest configurable
ceiling a tail answered with a cursor and no lines at all.

what:
- Encode the tracked window as base64url rather than hex
- Decode it once per read instead of once per compared row
- Measure the budget against a real widest cursor, not a placeholder
why: kill-server is answered when the command lands rather than when
the server exits, so the replacement could be created on the dying
server and die with it, leaving the socket with no server and the
connect retries reporting only that discovery failed.

what:
- Wait for the recorded server process to go before starting a new one
- Fail on the replacement's own exit status instead of five seconds later
- Probe with list-sessions, since a socket file outlives its server
why: Trunk corrected these comments to v7.0.1 while this branch was in
flight, and the two lines the branch adds to release.yml were outside
that commit's reach. The rebase left a v7.0.1 SHA labelled v4.3.0, and
the version comment is the only readable half of a SHA pin.

what:
- Label both added actions/checkout pins v7.0.1
why: alpha.7 shipped tmux_run in TaskCapableTools.Waiting, so a client
that adopted the task handle experienced the old behaviour. The change
read as one clause inside a bullet about Task bounding, which is not
where a reader looks for an incompatibility.

what:
- Split the Task bounding entry from the tmux_run change
- State the break with the previous/new/reason/action frame
why: nuget.org renders the package README, and it carried 330 lines of
behaviour a reader does not need before installing. docs/mcp/ held only
the generated tool reference, so there was nowhere else for it.

what:
- Move waiting, result bounds, tiers, subscriptions and the stdout rule
  to docs/mcp/README.md
- Leave the package README as install, configuration and compatibility
- Register the new document in ReadmeExampleTests and sync_snippets, so
  its four blocks stay compiled and anchored
why: TmuxEventsDroppedEvent is new public API a caller has to branch on,
and control-mode.md described the marker without showing what handling
it looks like.

what:
- Add NoticeDroppedEvents, which treats the marker as cache
  invalidation rather than as a log line
- Anchor it under the buffer paragraph in docs/modes/control-mode.md
why: The LibTmux README named the psmux source commit and called a second
one unsafe. Both are bare SHAs, which WRITING.md bans outside evidentiary
artefacts, and the first duplicated PsmuxServer.SupportedCommit, so the
prose went stale the moment that constant moved. Somebody deciding
whether to install does not read upstream history.

what:
- State tmux, framework and platform support in a Compatibility table,
  after the API story rather than between it and the golden path
- Point at docs/psmux.md for the build the preview accepts
- Move the release variables and runner labels to CONTRIBUTING, which
  owns releases and where verify_workflows already checks the names
- Cut release-gate wording from the root README and the docs index
why: Windows and WSL callers had no supported way to read a tmux-like
session, and the MCP server could answer with a result no client could
hold, lose subscribers when a stream ended, or route a job to an
endpoint it did not start on.

what:
- Add PsmuxServer, PsmuxSession, PsmuxWindow and PsmuxPane: a
  query-only preview that pins one audited psmux build and rejects
  lifecycle, mutation, chaining, control mode and raw commands
- Add TmuxEventsDroppedEvent so a bounded control reader learns it
  fell behind instead of missing notifications silently
- Bound every serialized MCP tool and resource result, and tie tail
  cursors to the endpoint, server generation and pane that issued them
- Bound the MCP task store, and stop offering tmux_run as a task
- Keep hierarchy and pane-activity subscribers independent across a
  stream ending, and bind a job to its originating endpoint
---
updated-dependencies:
- dependency-name: Microsoft.CodeAnalysis.CSharp
  dependency-version: 5.9.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dotnet
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title dotnet(deps) Bump the dotnet group with 1 update dotnet(deps) Bump Microsoft.CodeAnalysis.CSharp to 5.9.0 Aug 22, 2026
@dependabot
dependabot Bot force-pushed the dependabot/nuget/dotnet-0c453febc3 branch from 45912b0 to 3790308 Compare August 22, 2026 16:26
@tony tony closed this Aug 22, 2026
@tony
tony deleted the dependabot/nuget/dotnet-0c453febc3 branch August 22, 2026 16:35
@dependabot @github

dependabot Bot commented on behalf of github Aug 22, 2026

Copy link
Copy Markdown
Contributor Author

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file .NET Pull requests that update .NET code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant