[release/8.0] Update SignalR Redis tests to use internal Docker Hub mirror#63117
Merged
Conversation
Docker Hub is prone to rate limiting. To prevent this in dotnet builds we should use our internal container registry.
github-actions
Bot
requested review from
BrennanConroy and
halter73
as code owners
wtgodbe
approved these changes
Aug 4, 2025
sebastienros
approved these changes
Aug 4, 2025
This was referenced Sep 10, 2025
Closed
Closed
Bump Microsoft.AspNetCore.Authentication.JwtBearer from 8.0.19 to 8.0.20
LtiLibrary/LtiAdvantage#191
Closed
This was referenced Jun 22, 2026
Closed
Closed
This was referenced Jun 29, 2026
Closed
Open
This was referenced Jul 6, 2026
Merged
Merged
Merged
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
2 participants
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.
Backport of #62936 to release/8.0
/cc @wtgodbe @sebastienros
Update SignalR Redis tests to use internal Docker Hub mirror
Summary of the changes (Less than 80 chars)
Description
{Detail}
Fixes #{bug number} (in this specific format)
Customer Impact
{Justification}
Regression?
[If yes, specify the version the behavior has regressed from]
Risk
[Justify the selection above]
Verification
Packaging changes reviewed?
When servicing release/2.1