chore: Bump the orleans group with 2 updates - #1607
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps Microsoft.Orleans.Sdk from 10.2.2 to 10.3.1 Bumps Microsoft.Orleans.Server from 10.2.2 to 10.3.1 --- updated-dependencies: - dependency-name: Microsoft.Orleans.Sdk dependency-version: 10.3.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: orleans - dependency-name: Microsoft.Orleans.Server dependency-version: 10.3.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: orleans ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
|
Superseded by #1608. |
dependabot
Bot
deleted the
dependabot/nuget/benchmarks/comparison/orleans/orleans-2f73d158a8
branch
September 20, 2026 00:40
pathosDev
added a commit
that referenced
this pull request
Sep 21, 2026
…ch group The `orleans` group exists so the two `Microsoft.Orleans.*` packages move in one PR at every update type, relying on the documented rule that a dependency joins the first group it matches. On the first run the 10.2.2 -> 10.2.3 bump opened twice: as the `orleans` group (#1607) and inside `minor-and-patch` (#1608, together with Akka), and Dependabot closed the former as superseded once the latter merged. Across `directories:` the precedence evidently does not hold — harmless this time, but two PRs for one bump is exactly the shape the group was added to prevent. `exclude-patterns` on the second group makes the split explicit and independent of precedence. For a major the `orleans` group remains the only taker, so the lockstep property holds where it matters. Refs #1597 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Updated Microsoft.Orleans.Sdk from 10.2.2 to 10.3.1.
Release notes
Sourced from Microsoft.Orleans.Sdk's releases.
10.3.1
The most significant change in this release over 10.3.0 is the format used by the version contract compatibility analyzers. The other changes are test and docs fixes.
What's Changed
Full Changelog: dotnet/orleans@v10.3.0...v10.3.1
10.3.0
Orleans 10.3.0
Orleans 10.3.0 expands the platform across clustering, streaming, persistence, integrations, serialization, and developer tooling while delivering a broad reliability and performance pass. Major outcomes include stronger distributed-directory and membership behavior, new streaming and storage providers, hardened transactions and durable jobs, incremental source generation, safer JSON storage deserialization, and new application templates. Alongside these features and fixes, the release optimizes key runtime paths, comprehensively refreshes the docs, strengthens testing and CI, and updates dependencies and repository maintenance.
Compatibility notes
$typemetadata only for types permitted by Orleans' configured type filters and manifest. Existing wire data remains readable when its types are allowed;[GenerateSerializer]types and standard permitted BCL types continue to work without changes. If persisted, streamed, or transactional JSON contains other types, reads now fail with an actionableJsonSerializationException. Prefer registering those types throughTypeManifestOptions.AllowedTypes,[GenerateSerializer],ITypeNameFilter, orITypeFilter;OrleansJsonSerializerOptions.AllowAllTypes = truerestores the former permissive JSON behavior when a narrowly scoped allow-list is not practical.rpc.system.name; Orleans-specific service, target, and source metadata move toorleans.rpc.service,orleans.rpc.target_id, andorleans.rpc.source_id. The runtime-siderpc.methodvalue is now qualified as<interface>/<method>, and affectedActivitySourceversions are incremented. Update dashboards, alerts, collectors, and queries which depend on the legacyrpc.system,rpc.service,rpc.orleans.target_id, orrpc.orleans.source_idkeys or the previous method value.IConfigureGrainContextactions before grain construction, so constructors can observe fully configured context state. CustomIGrainContextActivatorimplementations must migrate fromCreateContext(GrainAddress)toCreateContext(GrainAddress, IConfigureGrainContext[])and apply the supplied configurators before constructing the grain. Stateless-worker configurators continue to apply to the outer stateless-worker context.Highlights
Runtime, clustering & resilience
Streaming
Storage, persistence, journaling, durable jobs & transactions
Providers & integrations
DbDataSourcesupport, and improved Azure, ZooKeeper, Redis, NATS, and relational-provider behavior extend and stabilize integrations (#8462, #8699, #10326, #10429, #10381, #10437, #10835, #10422, #10505, #10276).Serialization, code generation & analyzers
Developer experience, templates, samples & docs
... (truncated)
10.3.0-rc.1
What's Changed
... (truncated)
Commits viewable in compare view.
Updated Microsoft.Orleans.Server from 10.2.2 to 10.3.1.
Release notes
Sourced from Microsoft.Orleans.Server's releases.
10.3.1
The most significant change in this release over 10.3.0 is the format used by the version contract compatibility analyzers. The other changes are test and docs fixes.
What's Changed
Full Changelog: dotnet/orleans@v10.3.0...v10.3.1
10.3.0
Orleans 10.3.0
Orleans 10.3.0 expands the platform across clustering, streaming, persistence, integrations, serialization, and developer tooling while delivering a broad reliability and performance pass. Major outcomes include stronger distributed-directory and membership behavior, new streaming and storage providers, hardened transactions and durable jobs, incremental source generation, safer JSON storage deserialization, and new application templates. Alongside these features and fixes, the release optimizes key runtime paths, comprehensively refreshes the docs, strengthens testing and CI, and updates dependencies and repository maintenance.
Compatibility notes
$typemetadata only for types permitted by Orleans' configured type filters and manifest. Existing wire data remains readable when its types are allowed;[GenerateSerializer]types and standard permitted BCL types continue to work without changes. If persisted, streamed, or transactional JSON contains other types, reads now fail with an actionableJsonSerializationException. Prefer registering those types throughTypeManifestOptions.AllowedTypes,[GenerateSerializer],ITypeNameFilter, orITypeFilter;OrleansJsonSerializerOptions.AllowAllTypes = truerestores the former permissive JSON behavior when a narrowly scoped allow-list is not practical.rpc.system.name; Orleans-specific service, target, and source metadata move toorleans.rpc.service,orleans.rpc.target_id, andorleans.rpc.source_id. The runtime-siderpc.methodvalue is now qualified as<interface>/<method>, and affectedActivitySourceversions are incremented. Update dashboards, alerts, collectors, and queries which depend on the legacyrpc.system,rpc.service,rpc.orleans.target_id, orrpc.orleans.source_idkeys or the previous method value.IConfigureGrainContextactions before grain construction, so constructors can observe fully configured context state. CustomIGrainContextActivatorimplementations must migrate fromCreateContext(GrainAddress)toCreateContext(GrainAddress, IConfigureGrainContext[])and apply the supplied configurators before constructing the grain. Stateless-worker configurators continue to apply to the outer stateless-worker context.Highlights
Runtime, clustering & resilience
Streaming
Storage, persistence, journaling, durable jobs & transactions
Providers & integrations
DbDataSourcesupport, and improved Azure, ZooKeeper, Redis, NATS, and relational-provider behavior extend and stabilize integrations (#8462, #8699, #10326, #10429, #10381, #10437, #10835, #10422, #10505, #10276).Serialization, code generation & analyzers
Developer experience, templates, samples & docs
... (truncated)
10.3.0-rc.1
What's Changed
... (truncated)
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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions