NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
NuGet
NuGet, #2601 most downloaded on NuGet
Common library for the Light, simple and fast convention-based code-first POCO, OrmLite. Support for Creating and Dropping Table Schemas from POCOs, Complex Property types transparently stored in schemaless text blobs. OrmLite is a suite extension methods on ADO.NET's underlying IDbConnection providing DRY, typed access for common data usage patterns that map to clean, simple POCOs. Great support for testing where OrmLite methods can be mocked.
Latest stable
10.4.2
Last release 1 months ago
19 Oct 2026
Release timing varies
gaps range from 2 weeks to 5 months
Nearly every release is documented
notes for 55 of the last 60 stable releases
4 versions withdrawn
withdrawn after publishing
127 years old
112 releases · first in 1900
Drag across the ruler to compare, or tap a release to open it.
v10.4.2 Release Notes
v10.4.2 includes the path traversal fix for FilesUploadFeature and FileSystemVirtualFiles . Applications exposing filesystem-backed uploads could allow an uploading user to create or overwrite files outside the configured upload root, subject to the application process's filesystem permissions. The default upload access requires authentication; applications explicitly allowing anonymous uploads could expose the issue without authentication.
The fix validates original and transformed upload filenames, checks resolved upload/download/replacement/deletion paths, and enforces filesystem containment before writes, appends and deletions. Containment uses platform-appropriate path casing and rejects symbolic links below the configured root. Path-bearing upload filenames and links below virtual-file roots are now rejected; a configured root that is itself a trusted symbolic link remains supported.
Security reports can be submitted through GitHub private vulnerability reporting or the security reporting portal . See the public security policy for reporting and coordinated-disclosure guidance. Public non-security bugs continue to belong in ServiceStack/Issues .
New GitHub Actions workflows generate release-specific dependency evidence and monitor it for newly published advisories:
Workflow What it does
security-core.yml Validates the evidence tooling on relevant changes and rescans retained release dependency graphs daily or on manual dispatch. Scan reports are retained even when a finding fails the job.
package-security.yml Generates and validates SBOMs, package hashes, framework-specific dependency graphs and any reviewed VEX from the exact successful package-build artifacts. Evidence generation runs separately from packing.
release-security.yml Attaches a security-evidence ZIP and checksum to a published GitHub release after successful generation.
nuget-push.yml Verifies matching package/security evidence before NuGet publication. Dependency advisory findings are reported as warnings, so other fixes can still be published; integrity and provenance failures remain blocking.
The daily security-core.yml scan can fail when a retained release graph matches a new advisory. This monitoring failure does not block publishing other updates. Package security evidence and NuGet publication retain the findings and report them as warnings; missing or invalid evidence and package/provenance mismatches still block publication.
Coverage follows the configured package inventory . A managed dependency scan is not a penetration test or a complete assessment of first-party code or embedded native libraries. VEX assessments require a reviewed, vulnerability-specific decision; a clean scan does not create one automatically. See the security tooling documentation for generation, verification and download instructions.
The daily workflow detected newly published advisories in System.Security.Cryptography.Pkcs resolved through the Oracle and SQL Server drivers in the recorded 10.4.0 dependency baselines:
CVE-2026-84008 / GHSA-846f-f764-76mx : denial of service in SignedCms.CheckSignature .
CVE-2026-70162 / GHSA-2fmv-rv2c-59x7 : denial of service in EnvelopedCms.Decode on Windows.
These are separate from the upload path traversal fix. A dependency advisory match requires application-specific impact assessment; it does not by itself establish that a database operation exposes the vulnerable cryptography API.
ServiceStack library packages do not add direct references to override a dependency's transitive packages. We will adopt the corrected upstream dependency in a major ServiceStack release after the upstream driver (for example, Microsoft.Data.SqlClient ) updates its dependency requirements. Customers who need an earlier mitigation can explicitly reference a compatible patched dependency in their own application.
For the recorded 10.4.0 baselines, the applicable Pkcs updates are:
Application uses Target framework Recorded Pkcs version Patched minimum in that major
ServiceStack.OrmLite.Oracle net8.0 , net10.0 8.0.1 8.0.2
ServiceStack.OrmLite.SqlServer.Data net8.0 8.0.1 8.0.2
ServiceStack.OrmLite.SqlServer.Data net10.0 9.0.18 9.0.21
Add the reference to your application's .csproj , not the ServiceStack library project. For an application using ServiceStack.OrmLite.SqlServer.Data and targeting both .NET 8 and .NET 10:
<ItemGroup Condition="'$(TargetFramework)' == 'net8.0'"> <PackageReference Include="System.Security.Cryptography.Pkcs" Version="8.0.2" /> </ItemGroup> <ItemGroup Condition="'$(TargetFramework)' == 'net10.0'"> <PackageReference Include="System.Security.Cryptography.Pkcs" Version="9.0.21" /> </ItemGroup>
For the Oracle baseline on .NET 8 or .NET 10:
<ItemGroup> <PackageReference Include="System.Security.Cryptography.Pkcs" Version="8.0.2" /> </ItemGroup>
Use the example matching your provider and actual resolved package major; do not add both alternatives to the same application or downgrade a newer fixed dependency. If your graph differs, consult the linked advisories for a compatible patched version. Applications using Central Package Management should declare the version in Directory.Packages.props and add the corresponding versionless application PackageReference .
Restore and inspect the application's complete dependency graph, then rebuild, test database connectivity and relevant application behavior, and redeploy. With the .NET 10 SDK:
dotnet restore dotnet package list --include-transitive dotnet package list --include-transitive --vulnerable
Update affected .NET runtimes as directed by Microsoft as well; a package reference does not service the installed runtime. The retained 10.4.0 baseline remains unchanged, so its daily scan can continue to report the original versions after an application has applied its own override. Keep the application's resolved graph and retest evidence separately; this does not retroactively change the archived SBOM or establish that an older release is unaffected.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
v10.4 Release Notes
v10.3 Release Notes
v10.2 Release Notes
Nothing published for this version
v10.1 Release Notes
The MCP Server's approval policy has been upgraded from a simple boolean ( RejectToolsRequiringApproval ) to a three-mode ApprovalMode enum:
Mode Behavior
ConfirmationToken New default. Write/destructive calls return a requires_confirmation response with a signed, short-lived token. The AI assistant presents the summary to the user for explicit confirmation, then re-invokes with the token. The server validates user identity, target API, payload hash, expiry and single-use replay before executing.
Reject Fail-closed - refuses any tool requiring interactive approval (the previous default).
DelegateToClient Executes immediately, relying on the MCP client's native confirmation dialog.
Mcp = { ToolGroups = ["api_tools"], // Default ApprovalMode = McpApprovalMode.ConfirmationToken, // Default ConfirmationTokenExpiry = TimeSpan.FromMinutes(5), // Default }
For production deployments, configure a shared SigningSecret (≥ 32 bytes) and register a distributed ICacheClient for cross-instance replay protection. See MCP Server - Approval for details.
The old RejectToolsRequiringApproval property is marked [Obsolete] and maps to Reject (true) or DelegateToClient (false).
A new [Mcp(Description = ...)] attribute lets you provide imperative, agent-facing instructions for DTOs exposed over MCP - such as mandatory prerequisites or confirmation steps - without polluting the regular [Description] used by AI.Chat API Tools, API Explorers, Admin UIs and OpenAPI generators:
[Description("Submits and charges a coffee shop order.")] [Mcp(Description = """ Submits and charges a coffee shop order. IMPORTANT: Before calling this API you MUST first call PreviewCoffeeShopOrder, present the itemized summary and total price to the human customer verbatim, and WAIT for their explicit natural-language confirmation of both the items and the total in a subsequent user turn. """)] [Tool("the user wants to place an order", Safety = ToolSafety.Write, RequiresApproval = true)] public class CreateCoffeeShopOrder : IPost, IReturn<CreateCoffeeShopOrderResponse> { }
When set, MCP responses ( api_search , api_describe , confirmation summaries) prefer [MCP(Description)] over the regular [Description] . All non-MCP consumers continue to see the original [Description] .
Most MCP API Assistants can infer the need for confirmation from the MCP annotations, but some require explicit instructions to avoid circumventing the 2-phase confirmation without seeking explicit human approval. The [Mcp] attribute provides a way to communicate those instructions without affecting other consumers.
api_search and api_describe now return MCP-flavored summaries when called over the MCP transport.
api_call output schema includes confirmationToken , expiresInSeconds , summary and instruction fields for the two-phase flow.
Empty args on parameterless APIs (e.g. IGet DTOs with no properties) now correctly emit {} instead of null to satisfy strict MCP schema validation.
The motivation for this architectural upgrade came after extreme long-running agent workflows caused single thread message JSON payloads to grow past 200MB. This monolithic column approach eventually degraded database tooling (even causing database IDE JDBC drivers to run out of memory) and strained the browser DOM until the UI froze and crashed.
To scale reliably for complex autonomous tasks, the agent execution was re-architected into a durable, slice-based system that is significantly more responsive, memory-efficient, and resilient:
AI.Chat agents can now run complex, multi-step tasks that span many model and tool exchanges without being tied to a single browser request. You can close your browser, refresh the page, or lose connectivity mid-run and return to find the agent's progress exactly where it left off.
Resumable execution - Long tool-calling workflows no longer fail after hitting a fixed iteration limit. The agent works in resumable slices, checkpointing progress to the database between each one. A run can continue across hundreds of model exchanges with a configurable budget (default 250 steps).
Survives disconnects - Run state, elapsed time, context usage, errors, cancellation, and tool-approval waits are all persisted. A page refresh reconnects to the live run. A partial streaming response is isolated from committed history, so an interrupted stream never damages earlier messages.
Automatic context compaction - A context usage indicator shows how much of the selected model's window is in use. When it reaches ~80%, AI.Chat automatically summarizes older working context while preserving current instructions and a recent verbatim tail, then continues the same run. The full original conversation remains available for review. A manual compact button creates a clean child thread instead, leaving the original unchanged.
Windowed message loading - Threads with thousands of messages no longer block the UI. The chat view loads the first 20 and latest 100 messages initially; the middle is fetched on demand. The sidebar uses an authoritative database message count and a compact preview rather than downloading every conversation.
SSE with automatic fallback - Real-time updates are delivered over Server-Sent Events for lower latency. If SSE is unavailable through a proxy or host configuration, the browser automatically falls back to reliable long polling. No configuration is required - the default "auto" transport handles both.
Provider compatibility - Text-only and strict providers (e.g. GLM) receive a compatible projection of the conversation. Multipart attachments, orphaned tool results, and malformed legacy tool history are cleaned up in the outbound copy without rewriting canonical history, reducing provider failures in long-running sessions.
Added two essential, zero-dependency core tools to enable web resource reading and fast codebase exploration:
fetch_url
Fetches HTTP/HTTPS URLs and converts HTML into clean, token-efficient Markdown.
Automatically strips boilerplate, scripts, stylesheets, and navigation layouts ( <script> , <style> , <nav> , <footer> , <aside> , etc.).
Accurately preserves headings, tables, code blocks, blockquotes, lists, emphasis, and hyperlinks (with relative URL resolution).
Returns raw text for non-HTML content (JSON, plain text) and includes configurable length limits and response truncation.
grep_search
Fast text and regular expression search across files and directory trees.
Automatically prunes non-source and virtual environment directories ( .git , node_modules , bin , obj , .venv , dist , build , etc.) and ignores binary files.
Supports file glob filtering (e.g. *.cs , *.py ), case-sensitivity options, and result capping with formatted relative path and line numbers.
v10.1 Release Notes
v10.1 Release Notes
v10 Release Notes
Nothing published for this version
v10 Release Notes
Nothing published for this version
v10 Release Notes
v8.10 Release Notes
v8.9 Release Notes
v8.8 Release Notes
v8.7 Release Notes
v8.7 Release Notes
v8.6 Release Notes
v8.5 Release Notes
v8.5 Release Notes
v8.4 Release Notes
v8.3 Release Notes
Nothing published for this version
v8.2 Release Notes
v8.1 Release Notes
v8.1 Release Notes
v8.0 Release Notes
v6.11 Release Notes
v6.10 Release Notes
Nothing published for this version
v6.9 Release Notes
v6.8 Release Notes
v6.7 Release Notes
v6.6 Release Notes
v6.5 Release Notes
v6.4 Release Notes
v6.3 Release Notes
v6.2 Release Notes
v6.1 Release Notes
v6.0.2 Release Notes
v6 Release Notes
Release Notes
v5.13 Release Notes
v5.13 Release Notes
v5.12 Release Notes
v5.11 Release Notes
Nothing published for this version
Release Notes
v5.10 Release Notes
Nothing published for this version
v5.9 Release Notes
v5.8 Release Notes
v5.7 Release Notes
v5.6 Release Notes
v5.5 Release Notes
v5.4 Release Notes
v5.2 Release Notes
v5.1 Release Notes
v5.0.2 Release Notes
One column per quarter.