Bump WolverineFx and 5 others#34
Conversation
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Bumps WolverineFx from 5.36.2 to 6.0.2 Bumps WolverineFx.AzureServiceBus from 5.36.2 to 6.0.2 Bumps WolverineFx.EntityFrameworkCore from 5.36.2 to 6.0.2 Bumps WolverineFx.FluentValidation from 5.36.2 to 6.0.2 Bumps WolverineFx.Postgresql from 5.36.2 to 6.0.2 Bumps WolverineFx.SqlServer from 5.36.2 to 6.0.2 --- updated-dependencies: - dependency-name: WolverineFx dependency-version: 6.0.2 dependency-type: direct:production update-type: version-update:semver-major dependency-group: wolverine - dependency-name: WolverineFx.AzureServiceBus dependency-version: 6.0.2 dependency-type: direct:production update-type: version-update:semver-major dependency-group: wolverine - dependency-name: WolverineFx.EntityFrameworkCore dependency-version: 6.0.2 dependency-type: direct:production update-type: version-update:semver-major dependency-group: wolverine - dependency-name: WolverineFx.FluentValidation dependency-version: 6.0.2 dependency-type: direct:production update-type: version-update:semver-major dependency-group: wolverine - dependency-name: WolverineFx.Postgresql dependency-version: 6.0.2 dependency-type: direct:production update-type: version-update:semver-major dependency-group: wolverine - dependency-name: WolverineFx.SqlServer dependency-version: 6.0.2 dependency-type: direct:production update-type: version-update:semver-major dependency-group: wolverine ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
changed the title
dependabot
Bot
force-pushed
the
dependabot/nuget/wolverine-e3b7346c97
branch
from
67501b5 to
26ffe5e
Compare
WalkthroughThis PR updates centrally managed WolverineFx package versions from 5.36.2 to 6.0.2. The core WolverineFx package and all six related integration packages (Azure Service Bus, Entity Framework Core, FluentValidation, SQL Server, and PostgreSQL) are upgraded uniformly in the Directory.Packages.props file. ChangesWolverineFx Version Upgrade
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@Directory.Packages.props`:
- Around line 26-31: Wolverine 6 defaults to TypeLoadMode.Dynamic and
ServiceLocationPolicy.NotAllowed which risks runtime codegen failure; either add
the WolverineFx.RuntimeCompilation package (add PackageVersion
Include="WolverineFx.RuntimeCompilation" Version="6.0.x") or explicitly
configure Wolverine to use TypeLoadMode.Static in your startup configuration
(where Wolverine is configured), and also audit any usages that assume the
previous ServiceLocationPolicy default and update them to work with
ServiceLocationPolicy.NotAllowed or explicitly set ServiceLocationPolicy to the
desired value; finally verify you only add Newtonsoft integration packages
(WolverineFx.Newtonsoft / WolverineFx.Http.Newtonsoft) if actually needed.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: eb54aa8c-21e7-4cea-9b42-2235b58b12fc
📒 Files selected for processing (1)
Directory.Packages.props
| <PackageVersion Include="WolverineFx" Version="6.0.2" /> | ||
| <PackageVersion Include="WolverineFx.AzureServiceBus" Version="6.0.2" /> | ||
| <PackageVersion Include="WolverineFx.EntityFrameworkCore" Version="6.0.2" /> | ||
| <PackageVersion Include="WolverineFx.FluentValidation" Version="6.0.2" /> | ||
| <PackageVersion Include="WolverineFx.SqlServer" Version="6.0.2" /> | ||
| <PackageVersion Include="WolverineFx.Postgresql" Version="6.0.2" /> |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Check for TypeLoadMode.Dynamic usage that would require WolverineFx.RuntimeCompilation
echo "=== Checking for TypeLoadMode.Dynamic usage ==="
rg -n 'TypeLoadMode\.Dynamic' --type=cs
echo -e "\n=== Checking if WolverineFx.RuntimeCompilation is referenced ==="
rg -n 'WolverineFx\.RuntimeCompilation' --glob '*.csproj'
echo -e "\n=== Checking for explicit TypeLoadMode configuration ==="
rg -n 'TypeLoadMode' --type=cs -C3Repository: emeraldleaf/NextAurora
Length of output: 238
🏁 Script executed:
#!/bin/bash
# Description: Check for Newtonsoft.Json usage with Wolverine and verify target frameworks
echo "=== Checking for Newtonsoft.Json usage in Wolverine configuration ==="
rg -n 'Newtonsoft|JsonConvert' --type=cs --glob '**/Program.cs' -C3
echo -e "\n=== Checking target frameworks in consuming projects ==="
fd -e csproj --exec sh -c 'echo "File: {}" && grep -n "TargetFramework" {}'
echo -e "\n=== Checking for ServiceLocationPolicy usage ==="
rg -n 'ServiceLocationPolicy' --type=cs -C3Repository: emeraldleaf/NextAurora
Length of output: 1572
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "=== TargetFramework / TargetFrameworks in all csproj ==="
python3 - <<'PY'
import pathlib, xml.etree.ElementTree as ET, re
root = pathlib.Path(".")
paths = list(root.glob("**/*.csproj"))
def norms(v):
return [x.strip() for x in re.split(r"[;,\s]+", v.strip()) if x.strip()]
for p in sorted(paths):
try:
txt = p.read_text(encoding="utf-8", errors="ignore")
# Quick prune: skip if neither tag appears
if "TargetFrameworks" not in txt and "TargetFramework" not in txt:
continue
tree = ET.parse(p)
r = tree.getroot()
# Default namespace handling
ns = ""
if r.tag.startswith("{"):
ns = r.tag.split("}")[0][1:]
def findall(tag):
if ns:
return r.findall(f".//{{{ns}}}{tag}")
return r.findall(f".//{tag}")
vals=[]
# Prefer TargetFrameworks
for el in findall("TargetFrameworks"):
if el.text and el.text.strip():
vals += norms(el.text)
if not vals:
for el in findall("TargetFramework"):
if el.text and el.text.strip():
vals += norms(el.text)
if vals:
print(f"{p}: {','.join(vals)}")
except Exception as e:
print(f"{p}: ERROR {e}")
PY
echo "=== Any TypeLoadMode / ServiceLocationPolicy mentions anywhere (cs only) ==="
rg -n 'TypeLoadMode|ServiceLocationPolicy' --type=cs || true
echo "=== WolverineFx.RuntimeCompilation package refs ==="
rg -n 'WolverineFx\.RuntimeCompilation' --glob '*.csproj' --glob '!**/bin/**' --glob '!**/obj/**' || true
echo "=== WolverineFx.Newtonsoft package refs (Directory.Packages.props + csproj) ==="
rg -n 'WolverineFx\.(Newtonsoft|Http\.Newtonsoft)' Directory.Packages.props --glob '*.csproj' || trueRepository: emeraldleaf/NextAurora
Length of output: 403
🌐 Web query:
WolverineFx 6.0 TypeLoadMode default Static or Dynamic ServiceLocationPolicy default NotAllowed TypeLoadMode.Dynamic requires WolverineFx.RuntimeCompilation
💡 Result:
In WolverineFx 6.0, the configuration defaults are as follows: TypeLoadMode Default: The default is TypeLoadMode.Dynamic [1][2]. ServiceLocationPolicy Default: The default is ServiceLocationPolicy.NotAllowed [3][4]. WolverineFx.RuntimeCompilation Requirement: Yes, TypeLoadMode.Dynamic (as well as TypeLoadMode.Auto) requires the WolverineFx.RuntimeCompilation package [1][2]. In Wolverine 6.0, the core WolverineFx library no longer includes the Roslyn-based compiler or registers a default IAssemblyGenerator [1][2]. Referencing the WolverineFx.RuntimeCompilation package is sufficient to enable this, as it contains a [WolverineModule] that Wolverine auto-discovers at startup to register the necessary compiler [1][2]. Conversely, if you use TypeLoadMode.Static—where all generated code is pre-built into the application assembly—you do not need the WolverineFx.RuntimeCompilation package, allowing your application to ship without a dependency on Roslyn [1][2].
Citations:
- 1: https://wolverine.netlify.app/guide/codegen.html
- 2: https://wolverinefx.net/guide/codegen
- 3: https://wolverinefx.net/guide/migration
- 4: Make ServiceLocationPolicy.NotAllowed the Default in Wolverine 6 JasperFx/wolverine#2584
Fix WolverineFx 6.0 upgrade risk: default Dynamic codegen + NotAllowed service location
- No
TypeLoadModeorServiceLocationPolicyconfiguration is present in the repo, so Wolverine 6 defaults apply (TypeLoadMode.Dynamic,ServiceLocationPolicy.NotAllowed). - Wolverine 6 requires
WolverineFx.RuntimeCompilationwhen usingTypeLoadMode.Dynamic; the repo has noWolverineFx.RuntimeCompilationpackage reference, so startup/runtime codegen can fail. TargetFrameworkisnet10.0across projects, which is compatible with Wolverine 6’s supported targets.
Action:
- Add
WolverineFx.RuntimeCompilationor configure Wolverine to useTypeLoadMode.Static. - Audit/adjust any behavior relying on the old
ServiceLocationPolicydefault. - Ensure Newtonsoft integration packages are only added if needed (no
WolverineFx.Newtonsoft/WolverineFx.Http.Newtonsoftreferences found).
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@Directory.Packages.props` around lines 26 - 31, Wolverine 6 defaults to
TypeLoadMode.Dynamic and ServiceLocationPolicy.NotAllowed which risks runtime
codegen failure; either add the WolverineFx.RuntimeCompilation package (add
PackageVersion Include="WolverineFx.RuntimeCompilation" Version="6.0.x") or
explicitly configure Wolverine to use TypeLoadMode.Static in your startup
configuration (where Wolverine is configured), and also audit any usages that
assume the previous ServiceLocationPolicy default and update them to work with
ServiceLocationPolicy.NotAllowed or explicitly set ServiceLocationPolicy to the
desired value; finally verify you only add Newtonsoft integration packages
(WolverineFx.Newtonsoft / WolverineFx.Http.Newtonsoft) if actually needed.
|
Closing — Wolverine 6.0 is a major version bump with breaking changes (the runtime code generator was split into a separate `WolverineFx.RuntimeCompilation` package per GH-2876). Every integration test fails at host startup with `No IAssemblyGenerator (Roslyn) is registered`. The migration shouldn't ride on a Dependabot bump — it needs a dedicated PR that:
Reopen as a tracked issue when ready. Will also add a Dependabot ignore rule for WolverineFx major versions so future weekly runs only suggest 5.x patches. |
|
This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests. To ignore these dependencies, configure ignore rules in dependabot.yml |
Wolverine 6.0 (PR #34) split the runtime code generator into a separate WolverineFx.RuntimeCompilation package (GH-2876). Every integration test in PR #34 failed at host startup with "no IAssemblyGenerator (Roslyn) is registered" — a major-version migration, not a Dependabot pickup. Stay on 5.x until the project does a dedicated 6.0 migration PR (read release notes end-to-end, choose dynamic-compilation package vs. TypeLoadMode.Static + codegen-write CI step, verify saga + outbox + AddConcurrencyRetry paths). Dependabot will continue suggesting 5.x minor/patch bumps via the existing wolverine group. Adding majors to ignore is the pattern for any package whose major versions ship known migration surface area; add others as they break the build under a Dependabot rebase. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
1 participant
Pinned WolverineFx at 6.0.2.
Release notes
Sourced from WolverineFx's releases.
6.0.0
Wolverine 6.0.0 — Critter Stack 2026
The messaging/orchestration release completing the Critter Stack 2026 wave, on the final foundation (JasperFx 2.0 / Weasel 9.0 / Marten 9.0 / Polecat 4.0).
Highlights
net9.0;net10.0.WolverineFxno longer ships Roslyn. Apps in the defaultTypeLoadMode.Dynamicmust addWolverineFx.RuntimeCompilation, or pre-generate viacodegen write+TypeLoadMode.Static(the trimmer then drops Roslyn). See the migration guide.ServiceLocationPolicy.NotAllowedis the default (BREAKING) — restructure registrations, allow-list per type, or callopts.RestoreV5Defaults()to revert.IsAotCompatible=true(except the intentionalWolverineFx.RuntimeCompilation); Static-mode publish drops Roslyn.WolverineFx.Newtonsoft/WolverineFx.Http.Newtonsoft;IForwardsTo<T>discovery now explicit; removed[Obsolete]APIs (EventForwardingToWolverine,RedisTransport.BuildRedisStreamUri,PulsarEndpoint.UriFor).Migration guide: https://wolverinefx.net/guide/migration.html (or
docs/guide/migration.md). Master plan: wolverine#2715. Remaining release-cut comms items tracked in #2745.5.39.1
Fixed a regression problem reported here JasperFx/wolverine#2739
Full Changelog: JasperFx/wolverine@V5.39.0...V5.39.1
5.39.0
What's Changed
Fault<T>on Terminal Handler Failure by @BlackChepo in Fault Events — Auto-PublishFault<T>on Terminal Handler Failure JasperFx/wolverine#2695New Contributors
Full Changelog: JasperFx/wolverine@V5.38.0...V5.39.0
5.38.0
What's Changed
Full Changelog: JasperFx/wolverine@V5.37.2...V5.38.0
5.37.2
What's Changed
Full Changelog: JasperFx/wolverine@V5.37.0...V5.37.2
5.37.0
What's Changed
Full Changelog: JasperFx/wolverine@v5.36.1...V5.37.0
Commits viewable in compare view.
Pinned WolverineFx.AzureServiceBus at 6.0.2.
Release notes
Sourced from WolverineFx.AzureServiceBus's releases.
6.0.0
Wolverine 6.0.0 — Critter Stack 2026
The messaging/orchestration release completing the Critter Stack 2026 wave, on the final foundation (JasperFx 2.0 / Weasel 9.0 / Marten 9.0 / Polecat 4.0).
Highlights
net9.0;net10.0.WolverineFxno longer ships Roslyn. Apps in the defaultTypeLoadMode.Dynamicmust addWolverineFx.RuntimeCompilation, or pre-generate viacodegen write+TypeLoadMode.Static(the trimmer then drops Roslyn). See the migration guide.ServiceLocationPolicy.NotAllowedis the default (BREAKING) — restructure registrations, allow-list per type, or callopts.RestoreV5Defaults()to revert.IsAotCompatible=true(except the intentionalWolverineFx.RuntimeCompilation); Static-mode publish drops Roslyn.WolverineFx.Newtonsoft/WolverineFx.Http.Newtonsoft;IForwardsTo<T>discovery now explicit; removed[Obsolete]APIs (EventForwardingToWolverine,RedisTransport.BuildRedisStreamUri,PulsarEndpoint.UriFor).Migration guide: https://wolverinefx.net/guide/migration.html (or
docs/guide/migration.md). Master plan: wolverine#2715. Remaining release-cut comms items tracked in #2745.5.39.1
Fixed a regression problem reported here JasperFx/wolverine#2739
Full Changelog: JasperFx/wolverine@V5.39.0...V5.39.1
5.39.0
What's Changed
Fault<T>on Terminal Handler Failure by @BlackChepo in Fault Events — Auto-PublishFault<T>on Terminal Handler Failure JasperFx/wolverine#2695New Contributors
Full Changelog: JasperFx/wolverine@V5.38.0...V5.39.0
5.38.0
What's Changed
Full Changelog: JasperFx/wolverine@V5.37.2...V5.38.0
5.37.2
What's Changed
Full Changelog: JasperFx/wolverine@V5.37.0...V5.37.2
5.37.0
What's Changed
Full Changelog: JasperFx/wolverine@v5.36.1...V5.37.0
Commits viewable in compare view.
Pinned WolverineFx.EntityFrameworkCore at 6.0.2.
Release notes
Sourced from WolverineFx.EntityFrameworkCore's releases.
6.0.0
Wolverine 6.0.0 — Critter Stack 2026
The messaging/orchestration release completing the Critter Stack 2026 wave, on the final foundation (JasperFx 2.0 / Weasel 9.0 / Marten 9.0 / Polecat 4.0).
Highlights
net9.0;net10.0.WolverineFxno longer ships Roslyn. Apps in the defaultTypeLoadMode.Dynamicmust addWolverineFx.RuntimeCompilation, or pre-generate viacodegen write+TypeLoadMode.Static(the trimmer then drops Roslyn). See the migration guide.ServiceLocationPolicy.NotAllowedis the default (BREAKING) — restructure registrations, allow-list per type, or callopts.RestoreV5Defaults()to revert.IsAotCompatible=true(except the intentionalWolverineFx.RuntimeCompilation); Static-mode publish drops Roslyn.WolverineFx.Newtonsoft/WolverineFx.Http.Newtonsoft;IForwardsTo<T>discovery now explicit; removed[Obsolete]APIs (EventForwardingToWolverine,RedisTransport.BuildRedisStreamUri,PulsarEndpoint.UriFor).Migration guide: https://wolverinefx.net/guide/migration.html (or
docs/guide/migration.md). Master plan: wolverine#2715. Remaining release-cut comms items tracked in #2745.5.39.1
Fixed a regression problem reported here JasperFx/wolverine#2739
Full Changelog: JasperFx/wolverine@V5.39.0...V5.39.1
5.39.0
What's Changed
Fault<T>on Terminal Handler Failure by @BlackChepo in Fault Events — Auto-PublishFault<T>on Terminal Handler Failure JasperFx/wolverine#2695New Contributors
Full Changelog: JasperFx/wolverine@V5.38.0...V5.39.0
5.38.0
What's Changed
Full Changelog: JasperFx/wolverine@V5.37.2...V5.38.0
5.37.2
What's Changed
Full Changelog: JasperFx/wolverine@V5.37.0...V5.37.2
5.37.0
What's Changed
Full Changelog: JasperFx/wolverine@v5.36.1...V5.37.0
Commits viewable in compare view.
Pinned WolverineFx.FluentValidation at 6.0.2.
Release notes
Sourced from WolverineFx.FluentValidation's releases.
6.0.0
Wolverine 6.0.0 — Critter Stack 2026
The messaging/orchestration release completing the Critter Stack 2026 wave, on the final foundation (JasperFx 2.0 / Weasel 9.0 / Marten 9.0 / Polecat 4.0).
Highlights
net9.0;net10.0.WolverineFxno longer ships Roslyn. Apps in the defaultTypeLoadMode.Dynamicmust addWolverineFx.RuntimeCompilation, or pre-generate viacodegen write+TypeLoadMode.Static(the trimmer then drops Roslyn). See the migration guide.ServiceLocationPolicy.NotAllowedis the default (BREAKING) — restructure registrations, allow-list per type, or callopts.RestoreV5Defaults()to revert.IsAotCompatible=true(except the intentionalWolverineFx.RuntimeCompilation); Static-mode publish drops Roslyn.WolverineFx.Newtonsoft/WolverineFx.Http.Newtonsoft;IForwardsTo<T>discovery now explicit; removed[Obsolete]APIs (EventForwardingToWolverine,RedisTransport.BuildRedisStreamUri,PulsarEndpoint.UriFor).Migration guide: https://wolverinefx.net/guide/migration.html (or
docs/guide/migration.md). Master plan: wolverine#2715. Remaining release-cut comms items tracked in #2745.5.39.1
Fixed a regression problem reported here JasperFx/wolverine#2739
Full Changelog: JasperFx/wolverine@V5.39.0...V5.39.1
5.39.0
What's Changed
Fault<T>on Terminal Handler Failure by @BlackChepo in Fault Events — Auto-PublishFault<T>on Terminal Handler Failure JasperFx/wolverine#2695New Contributors
Full Changelog: JasperFx/wolverine@V5.38.0...V5.39.0
5.38.0
What's Changed
Full Changelog: JasperFx/wolverine@V5.37.2...V5.38.0
5.37.2
What's Changed
Full Changelog: JasperFx/wolverine@V5.37.0...V5.37.2
5.37.0
What's Changed
Full Changelog: JasperFx/wolverine@v5.36.1...V5.37.0
Commits viewable in compare view.
Updated WolverineFx.Postgresql from 5.36.2 to 6.0.2.
Release notes
Sourced from WolverineFx.Postgresql's releases.
6.0.0
Wolverine 6.0.0 — Critter Stack 2026
The messaging/orchestration release completing the Critter Stack 2026 wave, on the final foundation (JasperFx 2.0 / Weasel 9.0 / Marten 9.0 / Polecat 4.0).
Highlights
net9.0;net10.0.WolverineFxno longer ships Roslyn. Apps in the defaultTypeLoadMode.Dynamicmust addWolverineFx.RuntimeCompilation, or pre-generate viacodegen write+TypeLoadMode.Static(the trimmer then drops Roslyn). See the migration guide.ServiceLocationPolicy.NotAllowedis the default (BREAKING) — restructure registrations, allow-list per type, or callopts.RestoreV5Defaults()to revert.IsAotCompatible=true(except the intentionalWolverineFx.RuntimeCompilation); Static-mode publish drops Roslyn.WolverineFx.Newtonsoft/WolverineFx.Http.Newtonsoft;IForwardsTo<T>discovery now explicit; removed[Obsolete]APIs (EventForwardingToWolverine,RedisTransport.BuildRedisStreamUri,PulsarEndpoint.UriFor).Migration guide: https://wolverinefx.net/guide/migration.html (or
docs/guide/migration.md). Master plan: wolverine#2715. Remaining release-cut comms items tracked in #2745.5.39.1
Fixed a regression problem reported here JasperFx/wolverine#2739
Full Changelog: JasperFx/wolverine@V5.39.0...V5.39.1
5.39.0
What's Changed
Fault<T>on Terminal Handler Failure by @BlackChepo in Fault Events — Auto-PublishFault<T>on Terminal Handler Failure JasperFx/wolverine#2695New Contributors
Full Changelog: JasperFx/wolverine@V5.38.0...V5.39.0
5.38.0
What's Changed
Full Changelog: JasperFx/wolverine@V5.37.2...V5.38.0
5.37.2
What's Changed
Full Changelog: JasperFx/wolverine@V5.37.0...V5.37.2
5.37.0
What's Changed
Full Changelog: JasperFx/wolverine@v5.36.1...V5.37.0
Commits viewable in compare view.
Pinned WolverineFx.SqlServer at 6.0.2.
Release notes
Sourced from WolverineFx.SqlServer's releases.
6.0.0
Wolverine 6.0.0 — Critter Stack 2026
The messaging/orchestration release completing the Critter Stack 2026 wave, on the final foundation (JasperFx 2.0 / Weasel 9.0 / Marten 9.0 / Polecat 4.0).
Highlights
net9.0;net10.0.WolverineFxno longer ships Roslyn. Apps in the defaultTypeLoadMode.Dynamicmust addWolverineFx.RuntimeCompilation, or pre-generate viacodegen write+TypeLoadMode.Static(the trimmer then drops Roslyn). See the migration guide.ServiceLocationPolicy.NotAllowedis the default (BREAKING) — restructure registrations, allow-list per type, or callopts.RestoreV5Defaults()to revert.IsAotCompatible=true(except the intentionalWolverineFx.RuntimeCompilation); Static-mode publish drops Roslyn.WolverineFx.Newtonsoft/WolverineFx.Http.Newtonsoft;IForwardsTo<T>discovery now explicit; removed[Obsolete]APIs (EventForwardingToWolverine,RedisTransport.BuildRedisStreamUri,PulsarEndpoint.UriFor).Migration guide: https://wolverinefx.net/guide/migration.html (or
docs/guide/migration.md). Master plan: wolverine#2715. Remaining release-cut comms items tracked in #2745.5.39.1
Fixed a regression problem reported here JasperFx/wolverine#2739
Full Changelog: JasperFx/wolverine@V5.39.0...V5.39.1
5.39.0
What's Changed
Fault<T>on Terminal Handler Failure by @BlackChepo in Fault Events — Auto-PublishFault<T>on Terminal Handler Failure JasperFx/wolverine#2695New Contributors
Full Changelog: JasperFx/wolverine@V5.38.0...V5.39.0
5.38.0
What's Changed
Full Changelog: JasperFx/wolverine@V5.37.2...V5.38.0
5.37.2
What's Changed
Full Changelog: JasperFx/wolverine@V5.37.0...V5.37.2
5.37.0
What's Changed
Full Changelog: JasperFx/wolverine@v5.36.1...V5.37.0
Commits viewable in compare view.
Summary by CodeRabbit