Bump System.IdentityModel.Tokens.Jwt from 8.19.2 to 8.22.0 - #75
Merged
bgard68 merged 1 commit intoAug 2, 2026
Conversation
--- updated-dependencies: - dependency-name: System.IdentityModel.Tokens.Jwt dependency-version: 8.22.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
bgard68
deleted the
dependabot/nuget/src/TodoApp.Infrastructure/System.IdentityModel.Tokens.Jwt-8.22.0
branch
August 2, 2026 15:51
bgard68
added a commit
that referenced
this pull request
Aug 2, 2026
main's container build has been failing since #75 merged. Dependabot updated TodoApp.Infrastructure's lock to System.IdentityModel.Tokens.Jwt 8.22.0 and left WebApi, UnitTests and IntegrationTests on 8.19.2, so restore refuses in locked mode with NU1004. Nothing caught it, because 'Build API image & scan' was path-filtered and no pull request since then touched src/. Removing that filter in this same branch is what surfaced it — on the first run, which is the argument for the change.
bgard68
added a commit
that referenced
this pull request
Aug 2, 2026
* build(ci): let the build checks report on every pull request A path-filtered check never reports on a pull request that misses its paths, and a required check that never reports blocks the merge for ever. So 'Build & Test' and 'Build API image & scan' could not be required — which is how auto-merge landed two dependency bumps today while the container build was failing, and left dapper unable to build its image. The filter is removed from pull_request only. The push trigger keeps it: there is no reason to rebuild and redeploy on a docs edit, and nothing gates on a push. The cost is a build on every pull request, roughly a minute. The alternative is a required-checks list that omits the checks that matter, which is the shape of protection this review has spent the day removing. * fix(deps): regenerate the lock files a bump left half-updated main's container build has been failing since #75 merged. Dependabot updated TodoApp.Infrastructure's lock to System.IdentityModel.Tokens.Jwt 8.22.0 and left WebApi, UnitTests and IntegrationTests on 8.19.2, so restore refuses in locked mode with NU1004. Nothing caught it, because 'Build API image & scan' was path-filtered and no pull request since then touched src/. Removing that filter in this same branch is what surfaced it — on the first run, which is the argument for the change.
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.
Updated System.IdentityModel.Tokens.Jwt from 8.19.2 to 8.22.0.
Release notes
Sourced from System.IdentityModel.Tokens.Jwt's releases.
8.22.0
What's Changed
Full Changelog: AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet@8.21.0...8.22.0
8.21.0
Performance Improvements
Bug Fixes
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)