Repository navigation
chore: bump jwt2fa to 1.1.2-rc.1 and notificationproviders to 1.1.1 - #152
Merged
dgates82 merged 1 commit intoSep 22, 2026
Conversation
|
1 task
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
One combined bump, per plan:
DGates.Identity.Jwt2Fa1.1.0→1.1.2-RC.1(temporary — will be re-pinned to the real1.1.2once that ships)DGates.Identity.NotificationProviders1.1.0→1.1.1(final)Verification
is2FaRequired: truebuild config).Next
This is the RC-testing step of the plan: verify here, then merge Jwt2Fa's
release/1.1.2tomainand cut its realv1.1.2release. Once that's live, this branch gets re-pinned to the real1.1.2before its own final release.Test plan