chore(deps): Bump WolverineFx and WolverineFx.RabbitMQ#48
Conversation
Bumps WolverineFx from 5.39.3 to 6.0.2 Bumps WolverineFx.RabbitMQ from 5.39.3 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-name: WolverineFx.RabbitMQ dependency-version: 6.0.2 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
|
Skipping auto-merge: this is a major version bump ( |
📝 WalkthroughWalkthroughThis PR updates the centralized package management configuration in ChangesWolverineFx Dependency Updates
Estimated code review effort🎯 2 (Simple) | ⏱️ ~5 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
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 90-92: The PackageVersion entries mix WolverineFx v6.0.2 with
WolverineFx.Postgresql at 5.39.3—update the PackageVersion
Include="WolverineFx.Postgresql" to Version="6.0.2" to align major versions;
after upgrading, verify whether your code uses TypeLoadMode.Dynamic and if so
add/restore the WolverineFx.RuntimeCompilation package and adjust
ServiceLocationPolicy (or call RestoreV5Defaults()) as needed to preserve prior
behavior—check for references to WolverineFx, WolverineFx.Postgresql,
WolverineFx.RabbitMQ, TypeLoadMode.Dynamic, ServiceLocationPolicy, and
RestoreV5Defaults to make the required changes.
🪄 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: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: a930e127-a58f-4ec0-9a43-94d16bf55c13
📒 Files selected for processing (1)
Directory.Packages.props
| <PackageVersion Include="WolverineFx" Version="6.0.2"/> | ||
| <PackageVersion Include="WolverineFx.Postgresql" Version="5.39.3"/> | ||
| <PackageVersion Include="WolverineFx.RabbitMQ" Version="5.39.3"/> | ||
| <PackageVersion Include="WolverineFx.RabbitMQ" Version="6.0.2"/> |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Check if WolverineFx.Postgresql 6.0.2 is available on NuGet
curl -s "https://api.nuget.org/v3-flatcontainer/wolverinefx.postgresql/index.json" | jq -r '.versions[]' | grep "^6\."Repository: Harborline-Software/signal-bridge
Length of output: 159
Align WolverineFx.Postgresql to v6.x to avoid major-version skew
Directory.Packages.props (lines 90-92) mixes WolverineFx v6.0.2 with WolverineFx.Postgresql still pinned to 5.39.3. NuGet has WolverineFx.Postgresql 6.0.2 available, so aligning the versions should prevent potential incompatibilities—especially across v6 breaking changes.
- <PackageVersion Include="WolverineFx.Postgresql" Version="5.39.3"/>
+ <PackageVersion Include="WolverineFx.Postgresql" Version="6.0.2"/>Also confirm whether v6 changes require adding WolverineFx.RuntimeCompilation (if TypeLoadMode.Dynamic is used) and whether ServiceLocationPolicy needs configuration/RestoreV5Defaults() to match current expectations.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| <PackageVersion Include="WolverineFx" Version="6.0.2"/> | |
| <PackageVersion Include="WolverineFx.Postgresql" Version="5.39.3"/> | |
| <PackageVersion Include="WolverineFx.RabbitMQ" Version="5.39.3"/> | |
| <PackageVersion Include="WolverineFx.RabbitMQ" Version="6.0.2"/> | |
| <PackageVersion Include="WolverineFx" Version="6.0.2"/> | |
| <PackageVersion Include="WolverineFx.Postgresql" Version="6.0.2"/> | |
| <PackageVersion Include="WolverineFx.RabbitMQ" Version="6.0.2"/> |
🤖 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 90 - 92, The PackageVersion entries
mix WolverineFx v6.0.2 with WolverineFx.Postgresql at 5.39.3—update the
PackageVersion Include="WolverineFx.Postgresql" to Version="6.0.2" to align
major versions; after upgrading, verify whether your code uses
TypeLoadMode.Dynamic and if so add/restore the WolverineFx.RuntimeCompilation
package and adjust ServiceLocationPolicy (or call RestoreV5Defaults()) as needed
to preserve prior behavior—check for references to WolverineFx,
WolverineFx.Postgresql, WolverineFx.RabbitMQ, TypeLoadMode.Dynamic,
ServiceLocationPolicy, and RestoreV5Defaults to make the required changes.
Updated WolverineFx from 5.39.3 to 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.Commits viewable in compare view.
Updated WolverineFx.RabbitMQ from 5.39.3 to 6.0.2.
Release notes
Sourced from WolverineFx.RabbitMQ'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.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 this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Summary by CodeRabbit