Bump AkkaHostingVersion from 1.5.1 to 1.5.2

[dependabot]

Bumps AkkaHostingVersion from 1.5.1 to 1.5.2.
Updates Akka.Cluster.Hosting from 1.5.1 to 1.5.2

Release notes

Sourced from Akka.Cluster.Hosting's releases.

1.5.2

• Update Akka.NET to 1.5.2 • Bump Akka.Persistence.PostgreSql to 1.5.2 • Bump Akka.Persistence.SqlServer to 1.5.2 • Persistence: Change persistence default serializer from json to null Major Changes • Persistence.Hosting default value for default serializer has been changed from json to null. This only affects persistence write and not reads. All objects with no serializer mapping will now be serialized using Akka default object serializer. If you have old persistence data where they do not have their serializer ID column populated%2C you will need to change this setting. Inherited Changes From Akka.NET Core • Persistence will now ignore the serializer setting inside journal settings when writing new events. This setting will only be used when data retrieved from the database does not have the serializer id column unpopulated. • Cluster.Hosting%2C by default%2C will have SplitBrainResolver enabled.

1.5.1.1

• Fix missing default DData configuration in cluster hosting extension

Changelog

Sourced from Akka.Cluster.Hosting's changelog.

[1.5.2] / 6 April 2023

• Update Akka.NET to 1.5.2
• Bump Akka.Persistence.PostgreSql to 1.5.2
• Bump Akka.Persistence.SqlServer to 1.5.2
• Persistence: Change persistence default serializer from json to null

Major Changes

• Persistence.Hosting default value for default serializer has been changed from json to null. This only affects persistence write and not reads. All objects with no serializer mapping will now be serialized using Akka default object serializer. If you have old persistence data where they do not have their serializer ID column populated, you will need to change this setting.

Inherited Changes From Akka.NET Core

• Persistence will now ignore the serializer setting inside journal settings when writing new events. This setting will only be used when data retrieved from the database does not have the serializer id column unpopulated.
• Cluster.Hosting, by default, will have SplitBrainResolver enabled.

[1.5.1.1] / 4 April 2023

• Fix missing default DData configuration in cluster hosting extension

Commits

• ace0870 Update RELEASE_NOTES.md for 1.5.2 release (#277)
• 20c3df5 Bump Akka.NET, Akka.Persistence.PostgreSql, and Akka.Persistence.SqlServer to...
• ee280d2 Bump Verify.Xunit from 19.12.0 to 19.12.1 (#275)
• 2347028 Change default persistence journal and snapshot store serializer to null (#274)
• bf6d79e Update RELEASE_NOTES.md for 1.5.1.1 (#273)
• fd429d4 Bump Verify.Xunit from 19.11.2 to 19.12.0 (#271)
• a4fc568 Fix missing default DData configuration in cluster hosting extension (#272)
• 8d3b804 Bump Verify.Xunit from 19.11.1 to 19.11.2 (#270)
• See full diff in compare view

Updates Akka.Hosting from 1.5.1 to 1.5.2

Release notes

Sourced from Akka.Hosting's releases.

1.5.2

• Update Akka.NET to 1.5.2 • Bump Akka.Persistence.PostgreSql to 1.5.2 • Bump Akka.Persistence.SqlServer to 1.5.2 • Persistence: Change persistence default serializer from json to null Major Changes • Persistence.Hosting default value for default serializer has been changed from json to null. This only affects persistence write and not reads. All objects with no serializer mapping will now be serialized using Akka default object serializer. If you have old persistence data where they do not have their serializer ID column populated%2C you will need to change this setting. Inherited Changes From Akka.NET Core • Persistence will now ignore the serializer setting inside journal settings when writing new events. This setting will only be used when data retrieved from the database does not have the serializer id column unpopulated. • Cluster.Hosting%2C by default%2C will have SplitBrainResolver enabled.

1.5.1.1

• Fix missing default DData configuration in cluster hosting extension

Changelog

Sourced from Akka.Hosting's changelog.

[1.5.2] / 6 April 2023

• Update Akka.NET to 1.5.2
• Bump Akka.Persistence.PostgreSql to 1.5.2
• Bump Akka.Persistence.SqlServer to 1.5.2
• Persistence: Change persistence default serializer from json to null

Major Changes

• Persistence.Hosting default value for default serializer has been changed from json to null. This only affects persistence write and not reads. All objects with no serializer mapping will now be serialized using Akka default object serializer. If you have old persistence data where they do not have their serializer ID column populated, you will need to change this setting.

Inherited Changes From Akka.NET Core

• Persistence will now ignore the serializer setting inside journal settings when writing new events. This setting will only be used when data retrieved from the database does not have the serializer id column unpopulated.
• Cluster.Hosting, by default, will have SplitBrainResolver enabled.

[1.5.1.1] / 4 April 2023

• Fix missing default DData configuration in cluster hosting extension

Commits

• ace0870 Update RELEASE_NOTES.md for 1.5.2 release (#277)
• 20c3df5 Bump Akka.NET, Akka.Persistence.PostgreSql, and Akka.Persistence.SqlServer to...
• ee280d2 Bump Verify.Xunit from 19.12.0 to 19.12.1 (#275)
• 2347028 Change default persistence journal and snapshot store serializer to null (#274)
• bf6d79e Update RELEASE_NOTES.md for 1.5.1.1 (#273)
• fd429d4 Bump Verify.Xunit from 19.11.2 to 19.12.0 (#271)
• a4fc568 Fix missing default DData configuration in cluster hosting extension (#272)
• 8d3b804 Bump Verify.Xunit from 19.11.1 to 19.11.2 (#270)
• See full diff in compare view

Updates Akka.Persistence.Hosting from 1.5.1 to 1.5.2

Release notes

Sourced from Akka.Persistence.Hosting's releases.

1.5.2

• Update Akka.NET to 1.5.2 • Bump Akka.Persistence.PostgreSql to 1.5.2 • Bump Akka.Persistence.SqlServer to 1.5.2 • Persistence: Change persistence default serializer from json to null Major Changes • Persistence.Hosting default value for default serializer has been changed from json to null. This only affects persistence write and not reads. All objects with no serializer mapping will now be serialized using Akka default object serializer. If you have old persistence data where they do not have their serializer ID column populated%2C you will need to change this setting. Inherited Changes From Akka.NET Core • Persistence will now ignore the serializer setting inside journal settings when writing new events. This setting will only be used when data retrieved from the database does not have the serializer id column unpopulated. • Cluster.Hosting%2C by default%2C will have SplitBrainResolver enabled.

1.5.1.1

• Fix missing default DData configuration in cluster hosting extension

Changelog

Sourced from Akka.Persistence.Hosting's changelog.

[1.5.2] / 6 April 2023

• Update Akka.NET to 1.5.2
• Bump Akka.Persistence.PostgreSql to 1.5.2
• Bump Akka.Persistence.SqlServer to 1.5.2
• Persistence: Change persistence default serializer from json to null

Major Changes

• Persistence.Hosting default value for default serializer has been changed from json to null. This only affects persistence write and not reads. All objects with no serializer mapping will now be serialized using Akka default object serializer. If you have old persistence data where they do not have their serializer ID column populated, you will need to change this setting.

Inherited Changes From Akka.NET Core

• Persistence will now ignore the serializer setting inside journal settings when writing new events. This setting will only be used when data retrieved from the database does not have the serializer id column unpopulated.
• Cluster.Hosting, by default, will have SplitBrainResolver enabled.

[1.5.1.1] / 4 April 2023

• Fix missing default DData configuration in cluster hosting extension

Commits

• ace0870 Update RELEASE_NOTES.md for 1.5.2 release (#277)
• 20c3df5 Bump Akka.NET, Akka.Persistence.PostgreSql, and Akka.Persistence.SqlServer to...
• ee280d2 Bump Verify.Xunit from 19.12.0 to 19.12.1 (#275)
• 2347028 Change default persistence journal and snapshot store serializer to null (#274)
• bf6d79e Update RELEASE_NOTES.md for 1.5.1.1 (#273)
• fd429d4 Bump Verify.Xunit from 19.11.2 to 19.12.0 (#271)
• a4fc568 Fix missing default DData configuration in cluster hosting extension (#272)
• 8d3b804 Bump Verify.Xunit from 19.11.1 to 19.11.2 (#270)
• See full diff 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

[Aaronontheweb]

@dependabot rebase