Bump Suave from 2.6.2 to 3.4.5

[dependabot]

Updated Suave from 2.6.2 to 3.4.5.

Release notes

Sourced from Suave's releases.

3.4.5

• Packages now declare the Apache-2.0 license as an SPDX expression (licenseExpression, with licenseUrl kept at the canonical licenses.nuget.org address for older clients) and carry repository metadata
• Allow consuming projects to use FSharp.Core versions newer than 10.0.102 (#​840)
• Refresh README.md to describe current v3.x capabilities and remove the legacy Jekyll docs/ tree in favor of website/ (guides) and docs-api/ (API reference)
• Modernize the reverse proxy to use System.Net.Http.HttpClient (shared, static instance) instead of the obsolete WebRequest/HttpWebRequest API
• Proxy: set X-Forwarded-For from the client address (appending to any existing chain), target Host at the upstream authority, and forward the client's host/scheme as X-Forwarded-Host/X-Forwarded-Proto
• Fix HPACK empty string and overlong len decode

3.4.3

Fix CPU spin in WebSocket connection.

3.4.0

Full HTTP/2 support.

3.3.1

Support for multiple listening sockets via SO_REUSEPORT on Linux/BSD.
Plus many performance optimizations.

3.3.0

Adds optional FilePartSink to configuration record to allow intercepting of file uploads. (#​796)

3.2.3

New build targeting FSharp.Core 10.0.102

3.2.2

FIX: Remove incorrect raise exception within accept loop leading to premature exit.

3.2.1

• FIX: Rewrite connection shutdown sequence to avoid race conditions under high concurrency load.

3.2.0

• Target .NET 10

3.1.1

• FIX: Equal signs in query parameter values are not parsed correctly (#​774)

3.1.0

New in v3.1.0

• Target .NET 9
• Rewrite of internals using Task, Memory and Pipelines.
• Many optimizations focusing on reducing memory allocations, improving throughput, and lowering latency.
• Rate limiting, security headers, validation webparts and new router module.

Commits viewable in compare view.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

🤖 This is an automated response from Repo Assist.

Thanks for keeping dependencies fresh! I investigated the CI failure on this PR and wanted to share the root cause for maintainers before merge.

Root cause: Suave 3.4.5 is a breaking major-version change from 2.6.2 — its internal implementation moved from Async-based to Task-based APIs (part of modernizing towards System.Net.Http.HttpClient and .NET 9/10 support). This breaks src/fsdocs-tool/BuildCommand.fs, which currently:

• References HttpRuntime.logger, a member that no longer exists on the new HttpRuntime.
• Mixes Async<'a> code with Suave's new SocketOp<unit> / Task-based socket operation types, causing FS0039/type-mismatch errors around the watch/serve code path (roughly lines 30, 864, 872, 885, 1315).

Suggested path forward: This isn't a simple version bump — BuildCommand.fs's use of Suave for the fsdocs watch live-reload server needs to be updated to Suave's new API surface (Task-based socket ops, replacement for the removed logger, etc.) before this can merge. I'd recommend either:

1. Pinning Suave to 2.6.2 for now (closing/holding this PR) until someone has bandwidth to do the migration, or
2. Tackling the BuildCommand.fs migration as a follow-up PR alongside this bump.

Happy to leave the actual migration to a maintainer or future task given its non-trivial scope. No code changes proposed here — just documenting the diagnosis so this doesn't need to be re-investigated from scratch.

Generated by 🌈 Repo Assist, see workflow run. Learn more.
_{Comment /repo-assist to run again}

_{Add this agentic workflow to your repo}

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@ae8d551f07c7ed7619f8c58c7bb4c3ac89395d38