chore(deps): Bump WolverineFx.Postgresql from 5.39.3 to 6.1.0#47
chore(deps): Bump WolverineFx.Postgresql from 5.39.3 to 6.1.0#47dependabot[bot] wants to merge 1 commit into
Conversation
--- updated-dependencies: - dependency-name: WolverineFx.Postgresql dependency-version: 6.0.2 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
.NET
|
Skipping auto-merge: this is a major version bump ( |
📝 WalkthroughWalkthroughUpdated the centrally managed NuGet package version for ChangesWolverine PostgreSQL Dependency Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 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 docstrings
🧪 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`:
- Line 91: The PackageVersion for WolverineFx.Postgresql is on 6.0.2 while
WolverineFx and WolverineFx.RabbitMQ are 5.39.3, causing mixed 5.x/6.x Wolverine
artifacts; update the package set so all Wolverine-related PackageVersion
entries are aligned: either change WolverineFx.Postgresql back to the 5.x series
that matches WolverineFx/WolverineFx.RabbitMQ (e.g., 5.39.3) or upgrade
WolverineFx and WolverineFx.RabbitMQ to 6.0.2 as a coordinated migration so
WolverineFx.Postgresql, WolverineFx, WolverineFx.RabbitMQ (and any
WolverineFx.RDBMS) share the same major/minor version.
🪄 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: 9b1efe4a-e914-4374-ae2b-e30effb5d154
📒 Files selected for processing (1)
Directory.Packages.props
| <PackageVersion Include="System.IdentityModel.Tokens.Jwt" Version="8.18.0"/> | ||
| <PackageVersion Include="WolverineFx" Version="5.39.3"/> | ||
| <PackageVersion Include="WolverineFx.Postgresql" Version="5.39.3"/> | ||
| <PackageVersion Include="WolverineFx.Postgresql" Version="6.0.2"/> |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify WolverineFx.Postgresql 6.0.2 declared dependencies from NuGet metadata (read-only).
set -euo pipefail
url='https://api.nuget.org/v3-flatcontainer/wolverinefx.postgresql/6.0.2/wolverinefx.postgresql.nuspec'
tmp="$(mktemp)"
curl -fsSL "$url" -o "$tmp"
echo "Dependency groups in WolverineFx.Postgresql 6.0.2:"
grep -nE '<group|<dependency' "$tmp" | sed -E 's/^[[:space:]]+//'
echo
echo "Current CPM Wolverine versions in Directory.Packages.props:"
grep -nE 'WolverineFx"|WolverineFx.Postgresql"|WolverineFx.RabbitMQ"' Directory.Packages.propsRepository: Harborline-Software/signal-bridge
Length of output: 849
Align Wolverine package major versions to prevent CPM version skew
At Line 91, WolverineFx.Postgresql is set to 6.0.2 while WolverineFx / WolverineFx.RabbitMQ remain 5.39.3 (Lines 90, 92). The NuGet nuspec for WolverineFx.Postgresql 6.0.2 declares a dependency on WolverineFx.RDBMS 6.0.2 (for net9.0/net10.0), so this change introduces mixed Wolverine 5.x + 6.x artifacts. Upgrade the Wolverine package set together (or keep all Wolverine packages on 5.x until a coordinated migration).
🤖 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` at line 91, The PackageVersion for
WolverineFx.Postgresql is on 6.0.2 while WolverineFx and WolverineFx.RabbitMQ
are 5.39.3, causing mixed 5.x/6.x Wolverine artifacts; update the package set so
all Wolverine-related PackageVersion entries are aligned: either change
WolverineFx.Postgresql back to the 5.x series that matches
WolverineFx/WolverineFx.RabbitMQ (e.g., 5.39.3) or upgrade WolverineFx and
WolverineFx.RabbitMQ to 6.0.2 as a coordinated migration so
WolverineFx.Postgresql, WolverineFx, WolverineFx.RabbitMQ (and any
WolverineFx.RDBMS) share the same major/minor version.
|
Looks like WolverineFx.Postgresql is updatable in another way, so this is no longer needed. |
dependabot
Bot
changed the title
1 participant
Updated WolverineFx.Postgresql from 5.39.3 to 6.1.0.
Release notes
Sourced from WolverineFx.Postgresql's releases.
6.1.0
Wolverine 6.1.0
Minor release. Critter Stack dependency refresh, plus the rollup of the entire post-6.0.0
6.0.xline — most significantly the AOT runtime-scanning-elimination work and a new command-line handler-discovery diagnostic.Dependencies
9.0.1→9.2.02.1.3→2.2.0(#2938)4.1.1(unchanged — already latest)5.0.0(unchanged — own 5.x line)Marten 9.2.0 now bundles
JasperFx.Events.SourceGeneratoras an analyzer, so projects referencingWolverine.Martenreceive it transitively. The previously-explicit analyzer references were dropped from the 8 Marten-referencing projects to avoid running the generator twice, which produced duplicateEvolve/*Evolverbuild errors (#2939).PolecatTestsretains its explicit reference because Polecat does not bundle the generator.New & Noteworthy
AOT: eliminate runtime assembly scanning — AOT Publishing. Static-mode apps no longer scan assemblies at startup; discovery now flows through source-generated manifests:
[WolverineHandlerModule]assemblies, with no filesystem probe — #2905 / #2935TypeQuery— #2909 / #2932GetTypes()scan — #2908 / #2936Command-line handler-discovery diagnostic — Command Line Integration · Command Line Diagnostics tutorial. New
dotnet run -- wolverine-diagnostics describe-handlers <Type>runsDescribeHandlerMatchfrom the CLI so you can troubleshoot handler discovery without editing your bootstrapping code — #2921 / #2923Build-time OpenAPI generation — Command Line Integration.
dotnet run -- openapigenerates the OpenAPI document without starting the host (no database/broker required) — #2903 / #2911SQS fair queues on standard queues — support
MessageGroupIdon standard Amazon SQS queues — #2886 / #2889SignalR
ClaimsPrincipal— the connection'sClaimsPrincipalis now exposed onSignalREnvelope— #2927 / #2937EF Core transactional outbox timing fix — the EF Core transaction and outbox flush now complete before the HTTP response is written — #2917 / #2920
Mixed-lifetime
IEnumerable<T>support; Lamar removed — handlers depending on a mixed singleton/scopedIEnumerable<T>now resolve every element correctly; Lamar is no longer used or supported, and the built-inServiceProvideris the container — #2896 / #2914Aggregate handler naming clarity — clarified and guarded the
*AggregateHandlernaming convention vs.[ReadAggregate]— #2924Production code-generation guidance — Code Generation. How to drop Roslyn from production images, with a linked
CqrsMinimalApisample — #2900 / #2912Bug fixes
Senderroutes built during description mode — #2897 / #2899What's Changed
... (truncated)
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.