Repository navigation
feat!: target .NET 10 and update dependencies - #8
Merged
Merged
Conversation
- Target net10.0 only; drop netstandard2.1 (pulled vulnerable ASP.NET Core 2.1 packages: Microsoft.AspNetCore.Http 2.1.1, Newtonsoft.Json 10.0.1, System.Security.Cryptography.Xml 4.5.0), net8.0 and net9.0; tests drop net6/net7 - Central Package Management, NuGet Audit as errors, global.json, .editorconfig, dependabot - JwtBearer 10.0.15, System.IdentityModel.Tokens.Jwt 8.23.0 - Samples/tests: stale NetDevPack.Security.Jwt.Core 8.2.2 replaced by NetDevPack.Security.Jwt 10.0.0; pin patched System.Security.Cryptography.Xml/Pkcs - Tests: xunit.v3 on Microsoft.Testing.Platform, AwesomeAssertions, fix xUnit1051 - CI: actions/checkout v7, setup-dotnet v6, publish now runs the tests, vulnerable package check, semantic-release 24, pack/push only on new release - Rename README.MD to README.md (the package references README.md; case matters on Linux) - Fix RepositoryBranch (master) BREAKING CHANGE: the package now targets .NET 10 only. Stay on 9.x for .NET Standard 2.1, .NET 8 or .NET 9. The public API did not change.
Each test created its own JWKS server (new keys), while the API under test is a class fixture that reads JWKS_URL once and AuthMiddleware cached the first token in a static field. Results depended on test order, which changed with xunit.v3 and fails on Linux CI.
nuget.org API keys expire and the org key already did, which made the last releases fail with 403. Publish with NuGet/login (OIDC) instead: the job gets a short-lived key from the trusted publishing policy for this repository and workflow file. Also adds a workflow_dispatch input to publish an existing release tag again, since re-running the job skips the push once the release exists.
Member
Author
|
Added NuGet trusted publishing (OIDC) to the publish workflow, since the org API key expired. Same change as NetDevPack/NetDevPack#71: |
github-actions Bot
pushed a commit
that referenced
this pull request
Nov 18, 2026
## [10.0.0](v9.0.1...v10.0.0) (2026-11-18) ### ⚠ BREAKING CHANGES * the package now targets .NET 10 only. Stay on 9.x for .NET Standard 2.1, .NET 8 or .NET 9. The public API did not change. * ci: use conventionalcommits release preset * test: share the JWKS server across the test class Each test created its own JWKS server (new keys), while the API under test is a class fixture that reads JWKS_URL once and AuthMiddleware cached the first token in a static field. Results depended on test order, which changed with xunit.v3 and fails on Linux CI. * ci: publish to NuGet with trusted publishing nuget.org API keys expire and the org key already did, which made the last releases fail with 403. Publish with NuGet/login (OIDC) instead: the job gets a short-lived key from the trusted publishing policy for this repository and workflow file. Also adds a workflow_dispatch input to publish an existing release tag again, since re-running the job skips the push once the release exists. ### Features * target .NET 10 and update dependencies ([#8](#8)) ([6779aee](6779aee))
|
🎉 This PR is included in version 10.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Modernizes NetDevPack.Security.JwtExtensions for .NET 10 (LTS). .NET 8 and .NET 9 reached end of support on 2026-11-10.
Breaking change (release 10.0.0)
net10.0only.netstandard2.1,net8.0andnet9.0were removed. Consumers who need them stay on 9.x.Security
netstandard2.1target depended on ASP.NET Core 2.1 packages with high severity advisories:Microsoft.AspNetCore.Http2.1.1,Newtonsoft.Json10.0.1 andSystem.Security.Cryptography.Xml4.5.0. Dropping that target removes all of them.NetDevPack.Security.Jwt10.0.0 (the version on nuget.org) depends onSystem.Security.Cryptography.Xml/Pkcs10.0.12, which now have high severity advisories. The tests and samples here pin 10.0.15 through Central Package Management transitive pinning untilNetDevPack.Security.Jwt11 (feat!: target .NET 10 only Security.Jwt#81) ships. The JwtExtensions package itself does not depend on them.Dependencies
Directory.Packages.props). NuGet Audit with NU1901-NU1904 as errors. Addedglobal.json,.editorconfigand Dependabot.Microsoft.AspNetCore.Authentication.JwtBearer10.0.15,System.IdentityModel.Tokens.Jwt8.23.0.NetDevPack.Security.Jwt.Core8.2.2 package ID is no longer published. It was replaced byNetDevPack.Security.Jwt10.0.0, and the other Security.Jwt packages are on 10.0.0.Tests
ApiTests(the test host) no longer targets net6/net7/net8/net9.CI
actions/checkout@v7andactions/setup-dotnet@v6, with the SDK taken fromglobal.json.Housekeeping
README.MD→README.md. The csproj packsREADME.md, and file names are case-sensitive on Linux runners.RepositoryBranchwasmainand is nowmaster.Test plan
dotnet build -c Release: 0 errors. The remaining warnings already existed (CS1591, nullable, obsoleteWebHostBuilderin the test host).dotnet test -c Release: 4/4 passeddotnet list package --vulnerable --include-transitive: no vulnerable packagesdotnet pack: a singlenet10.0group (JwtBearer 10.0.15, IdentityModel 8.23.0), README and icon includedFollow-up
NetDevPack.Security.Jwt11 is published, bump it here and remove the two transitive pins.WebHostBuilder.