NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
NuGet, #2365 most downloaded on NuGet
Code generation library for Orleans.Serialization
Latest stable
10.4.2
Last release 17 days ago
30 Oct 2026
Release timing varies
gaps range from 1 weeks to 6 months
Nearly every release is documented
notes for 59 of the last 60 stable releases
3 versions withdrawn
withdrawn after publishing
127 years old
116 releases · first in 1900
Drag across the ruler to compare, or tap a release to open it.
Support ILBasedSerializer as a fallback only after trying the configured fallback
Potentially-breaking changes
Non-breaking improvements
Microsoft.Orleans.Kubernetes.Hosting package (Fix: Orleans.Hosting.KubernetesHosting: System.MissingMethodException (#7364))Non-breaking bug fixes
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Add C# 9.0 record support to serializer
Non-breaking improvements
ILBasedSerializer when BinaryFormatter is disabled (#7198)TokenCredential support on Azure Event Hubs Stream Provider (#7166)MembershipVersion in GrainAddress (#7133)ValueTask and ValueTask<T> to be used in generic grain methods (#7190)Non-breaking bug fixes
PooledQueueCache, avoid cache miss if we know that we didn't miss any event (#7060)GenericMethodInvoker now correctly handles generic methods with overloads (#6844)EventHubReceiverProxy: ignore if offset isn't valid (#7192)GrainTimer (#7234)This release is based on 3.4.3, but without some changes made in 3.5.0, noticeably the Event Hubs library upgrade.
This release is based on 3.4.3, but without some changes made in 3.5.0, noticeably the Event Hubs library upgrade.
If possible, users should upgrade to 3.5.0 instead.
Prevent diagnostic notification messages from being dropped prematurely
Close connections asynchronously and improve gracefulness
Non-breaking improvements
Non-breaking bug fixes
The `Microsoft.Orleans.Kubernetes.Hosting` package is now marked as stable. This package is intended to help users who are deploying to Kubernetes by
The Microsoft.Orleans.Kubernetes.Hosting package is now marked as stable. This package is intended to help users who are deploying to Kubernetes by automating configuration of silos, monitoring Kubernetes for changes in the active pods, and terminating pods which are marked as defunct by the Orleans cluster. Please try it and give us your feedback. Documentation is available here and a sample project is available here.
Non-breaking improvements
LRU.Add() (#6872)IStorage that is not generic (#6928) (#6931)Non-breaking bug fixes
RunningRequestSenders (#6903)LinuxEnvironmentStatistics (#6842) (#6887)GrainDirectoryPartition, throw an exception instead of returning null if trying to register an activation on a non-valid silo (#6896) (#6901)OnActivateAsync() (#6891) (#6893)This release includes improvements to the cluster membership algorithm which are *opt-in* in this initial release. These changes are aimed at improvin
This release includes improvements to the cluster membership algorithm which are opt-in in this initial release. These changes are aimed at improving the accuracy of cluster membership when some or all nodes are in a degraded state. Details follow.
This PR implements some of the ideas from Lifeguard (paper, talk, blog) which can help during times of catastrophe, where a large portion of a cluster is in a state of partial failure. One cause for these kinds of partial failures is large scale thread pool starvation, which can cause a node to run slowly enough to not process messages in a timely manner. Slow nodes can therefore suspect healthy nodes simply because the slow node is not able to process the healthy node's timely response. If a sufficiently proportion of nodes in a cluster are slow (eg, due to an application bug), then healthy nodes may have trouble joining and remaining in the cluster, since the slow nodes can evict them. In this scenario, slow nodes will also be evicting each other. The intention is to improve cluster stability in these scenarios.
This PR introduces LocalSiloHealthMonitor which uses heuristics to score the local silo's health. A low score (0) represents a healthy node and a high score (1 to 8) represents an unhealthy node.
LocalSiloHealthMonitor implements the following heuristics:
Active in membershipFailing heuristics contribute to increased probe timeouts, which has two effects:
This effects of this feature are disabled by default in this release, with only passive background monitoring being enabled. The extended probe timeouts feature can be enabled by setting ClusterMembershipOptions.ExtendProbeTimeoutDuringDegradation to true. The passive background monitoring period can be configured by changing ClusterMembershipOptions.LocalHealthDegradationMonitoringPeriod from its default value of 10 seconds.
This PR adds support for indirectly pinging silos before suspecting/declaring them dead. When a silo is one missed probe away from being voted, the monitoring silo switches to indirect pings. In this mode, the silo picks a random other silo and sends it a request to probe the target silo. If that silo responds promptly with a negative acknowledgement (after waiting for a specified timeout), then the silo will be suspected/declared dead.
Additionally, when the vote limit to declare a silo dead is 2 silos, a negative acknowledgement counts for both required votes and the silos is unilaterally declared dead.
The feature is disabled by default in this release - only direct probes are used by-default - but could be enabled in a later release, or by users by setting ClusterMembershipOptions.EnableIndirectProbes to true.
This release includes improvements to the cluster membership algorithm which are *opt-in* in this initial release. These changes are aimed at improvin
This release includes improvements to the cluster membership algorithm which are opt-in in this initial release. These changes are aimed at improving the accuracy of cluster membership when some or all nodes are in a degraded state. Details follow.
This PR implements some of the ideas from Lifeguard (paper, talk, blog) which can help during times of catastrophe, where a large portion of a cluster is in a state of partial failure. One cause for these kinds of partial failures is large scale thread pool starvation, which can cause a node to run slowly enough to not process messages in a timely manner. Slow nodes can therefore suspect healthy nodes simply because the slow node is not able to process the healthy node's timely response. If a sufficiently proportion of nodes in a cluster are slow (eg, due to an application bug), then healthy nodes may have trouble joining and remaining in the cluster, since the slow nodes can evict them. In this scenario, slow nodes will also be evicting each other. The intention is to improve cluster stability in these scenarios.
This PR introduces LocalSiloHealthMonitor which uses heuristics to score the local silo's health. A low score (0) represents a healthy node and a high score (1 to 8) represents an unhealthy node.
LocalSiloHealthMonitor implements the following heuristics:
Active in membershipFailing heuristics contribute to increased probe timeouts, which has two effects:
This effects of this feature are disabled by default in this release, with only passive background monitoring being enabled. The extended probe timeouts feature can be enabled by setting ClusterMembershipOptions.ExtendProbeTimeoutDuringDegradation to true. The passive background monitoring period can be configured by changing ClusterMembershipOptions.LocalHealthDegradationMonitoringPeriod from its default value of 10 seconds.
This PR adds support for indirectly pinging silos before suspecting/declaring them dead. When a silo is one missed probe away from being voted, the monitoring silo switches to indirect pings. In this mode, the silo picks a random other silo and sends it a request to probe the target silo. If that silo responds promptly with a negative acknowledgement (after waiting for a specified timeout), then the silo will be suspected/declared dead.
Additionally, when the vote limit to declare a silo dead is 2 silos, a negative acknowledgement counts for both required votes and the silos is unilaterally declared dead.
The feature is disabled by default in this release - only direct probes are used by-default - but could be enabled in a later release, or by users by setting ClusterMembershipOptions.EnableIndirectProbes to true.
This release includes improvements to give developers additional context when a request does not return promptly. PR #6672 added these improvements. O
This release includes improvements to give developers additional context when a request does not return promptly. PR #6672 added these improvements. Orleans will periodically probe active grains to inspect their message queues and send status updates for certain requests which have been enqueued or executing for too long. These status messages will appear as warnings in the logs and will also be included in exceptions when a request timeout occurs. The information included can help a developer to identify what the grain is doing at the time of the request. For example, which messages are enqueued ahead of this message, and which messages are executing, how long they have been executing, how long this message has been enqueued, and the status of the grain's TaskScheduler.
This release adds a new pre-release package, Microsoft.Orleans.Hosting.Kubernetes, which adds richer integration for users hosting on Kubernetes. The package assists users by monitoring Kubernetes for silo pods and reflecting changes in cluster membership. For example, when a Pod is deleted, it is immediately removed from Orleans' membership. In addition, the package configures EndpointOptions and `ClusterOptions' to match the Pod's environments. Documentation and a sample project are expected in the coming weeks, and in the meantime, please see the original PR for more information: #6707.
Potentially breaking change
IStorage<TState> and IGrainState need to be updated to add a RecordExists property.)Non-breaking improvements
Non-breaking bug fixes
Improvements and bug fixes since 3.3.0-rc1.
Improvements and bug fixes since 3.3.0-rc1.
Non-breaking improvements
Non-breaking bug fixes
Improvements and bug fixes since 3.2.2.
Improvements and bug fixes since 3.2.2.
This release includes improvements to give developers additional context when a request does not return promptly. PR #6672 added these improvements. Orleans will periodically probe active grains to inspect their message queues and send status updates for certain requests which have been enqueued or executing for too long. These status messages will appear as warnings in the logs and will also be included in exceptions when a request timeout occurs. The information included can help a developer to identify what the grain is doing at the time of the request. For example, which messages are enqueued ahead of this message, and which messages are executing, how long they have been executing, how long this message has been enqueued, and the status of the grain's TaskScheduler.
Improvements and bug fixes since 3.2.1.
Improvements and bug fixes since 3.2.1.
Non-breaking improvements
Non-breaking bug fixes
Improvements and bug fixes since 3.2.0.
Improvements and bug fixes since 3.2.0.
Non-breaking improvements
Non-breaking bug fixes
We intend to bring it back as a grain directory plugin at a later time. Removal of multi-clustering is the only breaking change, and only if you used…
This feature allows to use external storage as an option for keeping grain directory information. Directory plugins can be configured for different grain classes independently, so that different consistency/availability tradeoffs can be made for different grain classes. As part of this change, we had to remove support for multi-cluster functionality. We intend to bring it back as a grain directory plugin at a later time. Removal of multi-clustering is the only breaking change, and only if you used the feature previously.
Since the initial release, Orleans has been using its own custom thread pool implementation to make up for the deficiencies in the .NET thread pool. Since then, the .NET thread pool has improved significantly, and there is no need any more for a separate solution within Orleans.
We measured a performance increase of 3.2.0 compared to 3.1.6 of 12% to 20% depending on the test scenario.
Other improvements and bug fixes since 3.1.0.
Breaking changes
Non-breaking improvements
READ COMMITTED to avoid Gap Lock issues (#6331)Non-breaking bug fixes
Improvements and bug fixes since 3.2.0-rc2
Improvements and bug fixes since 3.2.0-rc2
We intend to bring it back as a grain directory plugin at a later time. Removal of multi-clustering is the only breaking change, and only if you used…
This feature allows to use external storage as an option for keeping grain directory information. Directory plugins can be configured for different grain classes independently, so that different consistency/availability tradeoffs can be made for different grain classes. As part of this change, we had to remove support for multi-cluster functionality. We intend to bring it back as a grain directory plugin at a later time. Removal of multi-clustering is the only breaking change, and only if you used the feature previously.
Since first version, Orleans has been using its own custom thread pool implementation to make up for the deficiencies in the .NET thread pool. Since then, the .NET thread pool has improved significantly, and there is no need any more for a separate solution within Orleans.
We measured a performance increase of 3.2.0-rc1 compared to 3.1.6 of 12% to 20% depending on the test scenario.
Other improvements and bug fixes since 3.1.6.
Breaking changes
Non-breaking improvements
READ COMMITED to avoid Gap Lock issues (#6331)Non-breaking bug fixes
Improvements and bug fixes since 3.1.6.
Improvements and bug fixes since 3.1.6.
Improvements and bug fixes since 3.1.5.
Improvements and bug fixes since 3.1.5.
Non-breaking improvements
Non-breaking bug fixes
Improvements and bug fixes since 3.1.4.
Improvements and bug fixes since 3.1.4.
Non-breaking improvements
Non-breaking bug fixes
Improvements and bug fixes since 3.1.3.
Improvements and bug fixes since 3.1.3.
Non-breaking improvements
Non-breaking bug fixes
Breaking changes (for rolling upgrades from 3.1.0 and 3.1.2 running on .NET Core 3.1)
This release fixes the partial backward compatibility regression introduced in 3.1.0. See #6392 for more details.
If your application targets .NET Core 3.1, rolling upgrade to 3.1.3 can be performed from all versions except for 3.1.0 and 3.1.2 For all other .NET versions, there are no known compatibility issues with rolling upgrades to 3.1.3
Improvements and bug fixes since 3.1.2.
Breaking changes (for rolling upgrades from 3.1.0 and 3.1.2 running on .NET Core 3.1)
Non-breaking improvements
Known issue: We discovered a partial backward compatibility regression in this release. If your application targets .NET Core 3.1, a rolling upgrade f
Known issue: We discovered a partial backward compatibility regression in this release. If your application targets .NET Core 3.1, a rolling upgrade from previous versions to 3.1.2 will fail. See #6392 for more details. The regression is fixed in 3.1.3.
Improvements and bug fixes since 3.1.0.
Non-breaking improvements
Non-breaking bug fixes
Nothing published for this version
Microsoft.Orleans.OrleansCodeGenerator.Build package has been marked as deprecated in favor of Microsoft.Orleans.CodeGenerator.MSBuild. We don't plan…
Known issue: We discovered a partial backward compatibility regression in this release. If your application targets .NET Core 3.1, a rolling upgrade from previous versions to 3.1.0 will fail. See #6392 for more details. The regression is fixed in 3.1.3.
Improvements and bug fixes since 3.0.0.
In this release we enabled multi-targeting, nestandard2.0 and netcoreapp3.1, for Microsoft.Orleans.Core, Microsoft.Orleans.OrleansRuntime, and Microsoft.Orleans.Connections.Security packages to leverage some performance features available in netcoreapp3.1.
Microsoft.Orleans.OrleansCodeGenerator.Build package has been marked as deprecated in favor of Microsoft.Orleans.CodeGenerator.MSBuild. We don't plan future releases of Microsoft.Orleans.OrleansCodeGenerator.Build.
Non-breaking improvements
Non-breaking bug fixes
Improvements and bug fixes since 3.1.0-rc2.
Improvements and bug fixes since 3.1.0-rc2.
Improvements and bug fixes since 3.1.0-rc1.
Improvements and bug fixes since 3.1.0-rc1.
In this release we enabled multi-targeting, nestandard2.0 and netcoreapp3.1, for Microsoft.Orleans.Core, Microsoft.Orleans.OrleansRuntime, and Microsoft.Orleans.Connections.Security packages to leverage some performance features available in netcoreapp3.1.
Improvements and bug fixes since 3.0.2.
Improvements and bug fixes since 3.0.2.
In this release we enabled multi-targeting, nestandard2.0 and netcoreapp3.1, for Microsoft.Orleans.Core, Microsoft.Orleans.OrleansRuntime, and Microsoft.Orleans.Connections.Security packages to leverage some performance features available in netcoreapp3.1.
Non-breaking improvements
Non-breaking bug fixes
Improvements and bug fixes since 3.0.1.
Improvements and bug fixes since 3.0.1.
Non-breaking improvements
Non-breaking bug fixes
Improvements and bug fixes since 3.0.0.
Improvements and bug fixes since 3.0.0.
Non-breaking improvements
Non-breaking bug fixes
…of a running cluster. However, there are several breaking changes in the APIs that might require minor adjustments for application code to compile.
Major improvements since 2.0.0
This release is backward compatible, over the wire messaging wise, with 2.* releases, which allows for in-place upgrade of a running cluster. However, there are several breaking changes in the APIs that might require minor adjustments for application code to compile.
Tested on .NET Framework 4.7.2, .NET Core 2.2 and .NET Core 3.0.
Changes since 2.3.0:
Non-breaking improvements
Non-breaking bug fixes
…of a running cluster. However, there are several breaking changes in the APIs that might require minor adjustments for application code to compile.
This release is backward compatible, over the wire messaging wise, with 2.* releases, which allows for in-place upgrade of a running cluster. However, there are several breaking changes in the APIs that might require minor adjustments for application code to compile.
Tested on .NET Framework 4.7.2, .NET Core 2.2 and .NET Core 3.0.
This release is ready for production use.
Changes since 3.0.0-rc1:
Non-breaking improvements
Non-breaking bug fixes
…of a running cluster. However, there are several breaking changes in the APIs that might require minor adjustments for application code to compile.
This release is backward compatible, over the wire messaging wise, with 2.* releases, which allows for in-place upgrade of a running cluster. However, there are several breaking changes in the APIs that might require minor adjustments for application code to compile.
We measured significant performance gains with this release over 2.* versions, ranging from 8% to 93% depending on the test, mostly due to the network stack rewrite.
Tested on .NET Framework 4.7.2, .NET Core 2.2 and .NET Core 3.0.
This release is ready for production use.
Known issue. If you get the following run time error on .NET Core 3.0
An exception of type 'System.IO.FileNotFoundException' occurred in Orleans.Runtime.dll but was not handled in user code: 'Could not load file or assembly 'Microsoft.Bcl.AsyncInterfaces, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'.
add an explicit reference to Microsoft.Bcl.AsyncInterfaces NuGet package to your project. See #6028 for details.
Changes since 3.0.0-beta1:
Non-breaking improvements
Non-breaking bug fixes
…of a running cluster. However, there are several breaking changes in the APIs that might require minor adjustments for application code to compile.
This release is backward compatible, over the wire messaging wise, with 2.* releases, which allows for in-place upgrade of a running cluster. However, there are several breaking changes in the APIs that might require minor adjustments for application code to compile.
We measured significant performance gains with this release over 2.* versions, ranging from 8% to 93% depending on the test, mostly due to the network stack rewrite.
Changes since 2.3.0:
Non-breaking improvements
Non-breaking bug fixes
Improvements and bug fixes since 2.4.4.
Improvements and bug fixes since 2.4.4.
Non-breaking improvements
Non-breaking bug fixes
Improvements and bug fixes since 2.4.3.
Improvements and bug fixes since 2.4.3.
Non-breaking improvements
Non-breaking bug fixes
Improvements and bug fixes since 2.4.2.
Improvements and bug fixes since 2.4.2.
Non-breaking improvements
Non-breaking bug fixes
Improvements and bug fixes since 2.4.1.
Improvements and bug fixes since 2.4.1.
Non-breaking improvements
Non-breaking bug fixes
Improvements and bug fixes since 2.4.0. The most important one is #5863 that relaxes the requirements for clustering providers that do not support mem
Improvements and bug fixes since 2.4.0. The most important one is #5863 that relaxes the requirements for clustering providers that do not support membership table version. See more details on that in the release notes for 2.4.0.
Non-breaking improvements
Non-breaking bug fixes
Reduced reliance on cluster membership table and speed up clustering convergence by sending versioned snapshots of the table as part of gossip message
Important: An incompatibility was reported of 2.4.0 with clustering providers, such as MongoDB and DynamoDB, that do not implement correctly or at all membership table version. This issue has been addressed via #5863 in v2.4.1.
This release is backward compatible with 2.0.* releases, which allows for in-place upgrade of a running cluster.
Non-breaking improvements
Non-breaking bug fixes
Improvements and bug fixes since 2.3.5
Improvements and bug fixes since 2.3.5
Non-breaking improvements
Non-breaking bug fixes
Improvements and bug fixes since 2.3.4.
Improvements and bug fixes since 2.3.4.
Non-breaking improvements
Non-breaking bug fixes
Improvements and bug fixes since 2.3.3.
Improvements and bug fixes since 2.3.3.
Improvements and bug fixes since 2.3.2.
Improvements and bug fixes since 2.3.2.
Non-breaking improvements
Non-breaking bug fixes
Improvements and bug fixes since 2.3.1.
Improvements and bug fixes since 2.3.1.
Improvements and bug fixes since 2.3.0. The important change is bringing back the batch stream production API that got removed in 2.3.0 by mistake.
Improvements and bug fixes since 2.3.0. The important change is bringing back the batch stream production API that got removed in 2.3.0 by mistake.
Non-breaking improvements
Non-breaking bug fixes
All packages have been updated.
Refactored stream batch behaviors to support batch consumption. (#5425) technically a breaking change due to the changes to the batch streaming API. H…
IHostEnvironmentStatistics on Linux, which enables CPU and memory metrics as well as load shedding. Thanks to @martinothamar!This release is backward compatible with 2.0.* releases, which allows for in-place upgrade of a running cluster.
Three new NuGet packages were added:
Breaking changes
Refactored stream batch behaviors to support batch consumption. (#5425) technically a breaking change due to the changes to the batch streaming API. However, it shouldn't break any working application code because the batching functionality wasn't fully wired previously.
This release is backward-compatible with 2.x releases.Non-breaking improvements
LoadShedding. (#5387)Non-breaking bug fixes
…functionality wasn't fully wired previously. No breaking change in the wire protocol or persistence. This release is backward-compatible with 2.x rele…
Changes since 2.3.0-rc1.
Refactored stream batch behaviors to support batch consumption. (#5425) is the only change. While technically it is breaking due to the changes to the batch streaming API, it shouldn't break any working application code because the batching functionality wasn't fully wired previously. No breaking change in the wire protocol or persistence. This release is backward-compatible with 2.x releases.
Support for the ASP.NET Core hosting API (Microsoft.Extensions.Hosting).
Major improvements
Breaking changes
Non-breaking improvements
LoadShedding. (#5387)Non-breaking bug fixes
Improvements and bug fixes since 2.2.3.
Improvements and bug fixes since 2.2.3.
Non-breaking improvements
LoadShedding. (#5387)Non-breaking bug fixes
Updated packages: all but Microsoft.Orleans.Core.Abstractions.
Improvements and bug fixes since 2.2.2. The most important ones are in silo shutdown sequence (#5268 and #5276). Server side, code generation, and som
Improvements and bug fixes since 2.2.2. The most important ones are in silo shutdown sequence (#5268 and #5276). Server side, code generation, and some extension packages have been updated. Core and client stayed unchanged.
Non-breaking improvements
Non-breaking bug fixes
Updated packages:
This release includes no breaking changes and is backward compatible with 2.0.* releases, which allows for in-place upgrade of a running cluster.
This release is primarily about bringing support for ACID cross-grain transactions to production-ready quality. Other improvements and fixes are listed below.
This release includes no breaking changes and is backward compatible with 2.0.* releases, which allows for in-place upgrade of a running cluster.
Warning: If you are using Orleans with .NET Core 2.1, do not enable TieredCompilation for Orleans silo and client projects. We recently discovered a CLR bug that is breaking Orleans when TieredCompilation is enabled. See #4990 for more details.
Breaking changes
Non-breaking improvements
Non-breaking bug fixes
Major performance (up to 4x) and stability improvements in transactions compared to 2.2.0-beta1.
Major performance (up to 4x) and stability improvements in transactions compared to 2.2.0-beta1.
Breaking changes
Non-breaking improvements
Non-breaking bug fixes
Avoid lazy initialization when disposing OutboundMessageQueue
Changes since v2.1.0.
Breaking changes
Non-breaking improvements
Non-breaking bug fixes
Improvements and bug fixes since 2.1.1.
Improvements and bug fixes since 2.1.1.
This release includes no breaking changes and is backward compatible with 2.0.* releases, which allows for in-place upgrade of a running cluster.
This release includes a number of performance improvements, the biggest one being the new scheduler, that all add up in our tests to up to 30% throughput increase on the same hardware.
It also brings the support for distributed transaction to what we consider "release candidate" quality, with the new Distributed Transaction Manager at its core. We plan to declare transactions production ready in a subsequent release, after another round of testing and improvements.
Lastly, this release includes a new code generation package Microsoft.Orleans.CodeGenerator.MSBuild that can be used as an alternative to Microsoft.Orleans.OrleansCodeGenerator.Build. The new code generator leverages Roslyn Code Analysis functionality to avoid loading application binaries. As a result, it avoid issues caused by clashing dependency versions and multiple versions of the .NET Core SDK.
This release includes no breaking changes and is backward compatible with 2.0.* releases, which allows for in-place upgrade of a running cluster.
Warning: If you are using Orleans with .NET Core 2.1, do not enable TieredCompilation for Orleans silo and client projects. We recently discovered a CLR bug that is breaking Orleans when TieredCompilation is enabled. See #4990 for more details.
Major changes
Breaking changes
Non-breaking improvements
Non-breaking bug fixes
Warning: If you are using Orleans with .NET Core 2.1, *do not enable* TieredCompilation for Orleans silo and client projects. We recently discovered a
Warning: If you are using Orleans with .NET Core 2.1, do not enable TieredCompilation for Orleans silo and client projects. We recently discovered a CLR bug that is breaking Orleans when TieredCompilation is enabled. See #4990 for more details.
Major changes
Microsoft.Orleans.CodeGenerator.MSBuild NuGet package can be used instead of Microsoft.Orleans.OrleansCodeGenerator.Build. We plan to eventually retire Microsoft.Orleans.OrleansCodeGenerator.Build.Breaking changes
Non-breaking bug fixes
One column per quarter.