Repository navigation
chore: Bump Akka from 1.5.74 to 1.5.75 - #1850
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
--- updated-dependencies: - dependency-name: Akka dependency-version: 1.5.75 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: minor-and-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/nuget/benchmarks/comparison/akka-net/minor-and-patch-bd4a1458f2
branch
from
November 18, 2026 05:12
d9ce0c6 to
694b00f
Compare
pathosDev
added a commit
that referenced
this pull request
Nov 18, 2026
…nd-patch-bd4a1458f2' into features/dependabot-round-2026-11-18 PR #1850: Akka 1.5.74 -> 1.5.75 in the Akka.NET comparison arm. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
pathosDev
added a commit
that referenced
this pull request
Nov 18, 2026
Dependabot round 2026-11-18: #1815 #1816 #1837 #1847 #1848 #1849 #1850, all reviewed and merged (completions: UiAssets.ts for #1849, example bun.lock sync and a source-map-js audit fix for #1837). Plus the fix for the six open CodeQL alerts (6f31f3c). Gates: typecheck(s), bun test 23803 pass / 1 timing flake under load (CompressionLiveness, 5/5 green alone), coverage 96.66 %, smoke, examples, typecheck:bench, bench:smoke, check:ui, frozen installs, six frontend builds. Closes #539 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Author
|
Looks like Akka is no longer updatable, so this is no longer needed. |
dependabot
Bot
deleted the
dependabot/nuget/benchmarks/comparison/akka-net/minor-and-patch-bd4a1458f2
branch
November 18, 2026 15:42
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 Akka from 1.5.74 to 1.5.75.
Release notes
Sourced from Akka's releases.
1.5.75
1.5.75 November 16th, 2026
Akka.NET v1.5.75 adds restart-free TLS certificate rotation for the DotNetty transport, fixes two certificate-validation gaps that silently disabled security checks, backports two Akka.Persistence ordering fixes, and brings Akka.Reminders to the 1.5 line as
Akka.Reminders.*packages.Upgrading from
Aaron.Akka.Reminders? The package IDs are nowAkka.Reminders,Akka.Reminders.Sql,Akka.Reminders.SqlServer,Akka.Reminders.PostgreSqlandAkka.Reminders.Sqlite, and the module shares the Akka.NET version number. Change your package references; stored data is read-compatible, proven by a golden-database spec against data written by the releasedAaron.Akka.Reminders1.5.73 packages.Two behavior changes to check before upgrading.
CertificateValidation.ValidateHostname(expectedHostname)andSslOptions.CustomValidatornow actually enforce what they were configured to enforce. Both were silently no-ops in earlier versions, so a peer that used to connect may now fail the TLS handshake. See the Akka.Remote / TLS section below.Akka.Remote / TLS
akka.remote.dot-netty.tcp.ssl.certificate.common-nameto find the certificate in a store by name, or pointssl.certificate.pathat a folder of PKCS#12/PEM files, and place the renewed certificate beside the old one. New connections use it within about 10 seconds; open connections keep the certificate they started with. In code, useDotNettySslSetup.FromSourcewithTlsCertificateSource, orSslOptions.CertificateSourcein Akka.Hosting. Existing TLS setups are unchanged. Behavior change: a certificate source checks that the certificate is allowed for the role. Withrequire-mutual-authentication = true(the default) the certificate must allow both client and server authentication.X509Certificate, a single-filePathand aThumbprintare not checked this way, so a certificate that worked before may be skipped with a warning when moved to a source, and a node with no other usable certificate does not start.TlsCertificateSourcefor TLS certificate rotation - The newAkka.IO.TlsCertificateSourceresolves a certificate from a store common name, a thumbprint, a single file, or a folder of files, and re-checks it once a minute. A certificate that cannot be used is judged again at the next look-up, so granting access to a private key later is picked up. The source never disposes a certificate it has published. PEM files need thenet6.0target; thenetstandard2.0build skips them and logs why.CertificateValidation.ValidateHostname(expectedHostname)now enforces the expected hostname - In v1.5.74 and earlier this validator logged a warning and did not compareexpectedHostnamewith the certificate, so a node that used it to check inbound client certificates accepted every client certificate. It now rejects any certificate that does not match the name, by the rules of .NET'sX509Certificate2.MatchesHostname. Behavior change: a certificate that does not match now fails the TLS handshake, and on the dialing side that shuts theActorSystemdown with exit code 79. Only nodes that opt in are affected:validate-certificate-hostnamedefaults tofalse. A certificate whose subject alternative name extension holds a malformed entry is rejected, as in 1.6.ValidateHostname()without an argument is unchanged.SslOptions.CustomValidatorin Akka.Remote.Hosting now applies when the certificate is set by file path or thumbprint - In earlier versions the validator only ran whenSslOptions.X509Certificatewas set, and was otherwise ignored without a warning. Behavior change: the validator now runs, so a peer it rejects fails the TLS handshake. ACustomValidatorwith no certificate in the options now fails at startup with aConfigurationException, and the certificate loads whenWithRemotingruns rather than when theActorSystemstarts.Akka.Reminders
netstandard2.0andnet10.0so it reaches .NET Framework 4.8 through .NET 10. This is a port rather than a backport: the module is new to 1.5, so the whole thing was re-targeted onto the branch. It ships five packages —Akka.Reminders,Akka.Reminders.Sql,Akka.Reminders.SqlServer,Akka.Reminders.PostgreSqlandAkka.Reminders.Sqlite— renamed fromAaron.Akka.Reminders*and now sharing the Akka.NET version number. A golden-database spec proves the new packages read data written by the releasedAaron.Akka.Reminders1.5.73 packages. AOT is not supported on Akka.NET 1.5, so the module carries no AOT annotations here. The module ships noreference.confand no MultiNode specs; serializer registration goes through the Akka.Hosting API, so HOCON-only users have no configuration surface for it.MaxSlippageand its shard region was missing for a while and then came back. The recipient got the newer occurrence and then the older one, and both acknowledgements succeeded. When the newest occurrence of a series moves toAwaitingAck, every older live occurrence of that series now expires in the same storage commit. Fixes #8965.ceil(earliness / interval)older occurrences per early send with no upper bound, and Reminders accepts any interval above zero. A 1 ms interval put about 5,000 expiries in one commit, and a sub-millisecond interval could put millions into the scheduler's memory. The cap is 256 per send, nearest first. No interval of about 20 ms or more at the default 5 sMaxSlippagecan reach it. Below that, during a shard region outage, an older occurrence more than 256 intervals back can still be sent after a newer one;failure-modes.mddocuments the limit.Akka.Persistence
PersistAllcompletion callback when the journal rejects the batch - The completion callback of aPersistAllorPersistAllAsynccall ran even when the journal rejected the batch, so an actor could act on a write that never happened. The defect was present since 1.5.57. Fixes #8948.Persisthandler, or the async completion ofPersistAll, did not complete synchronously: two calls unstashed in the same turn. These overloads first shipped in 1.5.57. Fixes #8942.Docs
security.mdnow says which certificate options can rotate without a restart, and no longer claims that revocation is checked, which the DotNetty transport does not do. A follow-up (#8970) corrected the article's note aboutCustomValidator, which does apply to thumbprint and single-file certificates since #8963.Build and tests
netstandard2.0build, whereHalfClosefalls back to a full close. When both sides disassociate at once, one side can close while the other's frames are still unread and its kernel sends an RST, so the spec failed intermittently. The two sibling "no reset" tests in the class already skip on .NET Framework for the same reason. This changes no product code.net_tests_reminders_linuxlane with its own Incrementalist config, becauseAkka.Reminders.Migration.Testsstarts SQL Server and PostgreSQL containers unconditionally and the Windows agents have no Docker.src/contrib/reminders/**is excluded from the Windows test configs.1 contributor since release 1.5.74
To see the full set of changes in Akka.NET v1.5.75, click here.
Commits viewable in compare view.