Skip to content

fix(deps): move to NetDevPack.Security.Jwt 11 - #37

Merged
brunobritodev merged 2 commits into
masterfrom
fix/deps-security-jwt-11
Nov 18, 2026
Merged

brunobritodev merged 2 commits into
masterfrom
fix/deps-security-jwt-11

Conversation

@brunobritodev

@brunobritodev brunobritodev commented Nov 18, 2026 •

Copy link
Copy Markdown
Member

What

  • NetDevPack.Security.Jwt.AspNetCore 10.0.0 → 11.0.0. It targets .NET 10 only and includes the in-memory store isolation fix.
  • Removes the transitive pins for System.Security.Cryptography.Pkcs/Xml. Security.Jwt 11 already pins the patched 10.0.15 versions, and dotnet list package --vulnerable stays clean.
  • Tests run in parallel again. xunit.runner.json was only there because PersistKeysInMemory() used a static list (fixed in Security.Jwt 10.0.1).
  • Sample: NetDevPack 8.0.2 → 9.0.0 and Swashbuckle.AspNetCore 10.3.1 → 11.0.1. Both build without code changes.
  • README compatibility table: 9.x → Security.Jwt 11.x.

Supersedes #34, #35 and #36 (Dependabot).

Release

fix(deps) → 9.0.1.

Validation

  • Build: 0 errors, no new warnings.
  • Tests: 17/17, 5 runs in a row in parallel.

NetDevPack.Security.Jwt 11 targets .NET 10 only and already pins the
patched System.Security.Cryptography.Pkcs/Xml, so the transitive pins
here are no longer needed.

Its in-memory store is now isolated per service provider (10.0.1), so
the tests run in parallel again and xunit.runner.json is gone.

Sample: NetDevPack 9.0.0 and Swashbuckle.AspNetCore 11.0.0.
@brunobritodev
brunobritodev merged commit 4840e68 into master Nov 18, 2026
2 checks passed
@brunobritodev
brunobritodev deleted the fix/deps-security-jwt-11 branch November 18, 2026 02:30
github-actions Bot pushed a commit that referenced this pull request Nov 18, 2026
## [9.0.1](v9.0.0...v9.0.1) (2026-11-18)

### Bug Fixes

* **deps:** move to NetDevPack.Security.Jwt 11 ([#37](#37)) ([4840e68](4840e68))
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 9.0.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant