Skip to content

chore: bump AndreGoepel.Marten.Identity.Blazor to 1.3.3#101

Merged
andregoepel merged 1 commit into
mainfrom
chore/bump-marten-identity-blazor-1.3.3
Jul 18, 2026
Merged

chore: bump AndreGoepel.Marten.Identity.Blazor to 1.3.3#101
andregoepel merged 1 commit into
mainfrom
chore/bump-marten-identity-blazor-1.3.3

Conversation

@andregoepel

Copy link
Copy Markdown
Owner

Dependabot missed the AndreGoepel.Marten.Identity.Blazor 1.3.1 → 1.3.3 upgrade; this does it manually.

Collateral (required, not scope creep)

1.3.3 transitively requires Marten.AspNetCore >= 9.16.0. With CentralPackageTransitivePinningEnabled (added in #98), the central Marten.AspNetCore pin is enforced, so it had to move up too — restore fails with NU1109 otherwise.

Dependabot had also missed Marten.AspNetCore, leaving it at 9.14.1 while Marten core was already bumped to 9.16.0 (via #99). Raising it to 9.16.0 restores Marten / Marten.AspNetCore parity.

  • AndreGoepel.Marten.Identity.Blazor 1.3.1 → 1.3.3
  • Marten.AspNetCore 9.14.1 → 9.16.0 (aligns with Marten core 9.16.0)

Verification

  • dotnet restore succeeds; MIB resolves to 1.3.3, Marten and Marten.AspNetCore both 9.16.0.
  • dotnet build succeeds; 57/57 bUnit tests pass.
  • dotnet list package --vulnerable --include-transitive reports no vulnerable packages.
  • Lockfile changes are limited to the affected packages, so --locked-mode restore stays reproducible.

Dependabot missed this upgrade. 1.3.3 transitively requires
Marten.AspNetCore >= 9.16.0, and with central transitive pinning enabled
the central Marten.AspNetCore pin has to move up with it. Dependabot had
missed that one too, leaving it at 9.14.1 behind Marten core (already
9.16.0 via #99); bumping it to 9.16.0 restores Marten/Marten.AspNetCore
parity.

Build, the 57 bUnit tests and `dotnet list package --vulnerable` are green.
@andregoepel
andregoepel merged commit 5bace3c into main Jul 18, 2026
4 checks passed
@andregoepel
andregoepel deleted the chore/bump-marten-identity-blazor-1.3.3 branch July 18, 2026 04:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant