Caleb Cartwright

> I'd be happy to track this for upstream changes of direction and inform here if that does happen. But based on what I'm seeing upstream, changes to the registries...

@jauderho as per last comments, we are waiting on you to share relevant upstream issues

> FWIW, I'm chasing down "invalid" in DockerHub pulls right now, where running the server locally works fine. I found this issue in search results and: current HEAD works fine,...

No worries! The above next steps still stand if anyone's able to help fill in the gaps. I also want to reiterate that I view those previously outlined questions/considerations as...

Thanks for continuing to investigate @philpennock, but as you alluded to, there's more that'll be needed than the minimal diff to get one passing badge. Part of the argument for...

> @chris48s if there is still a need here, I'd like to contribute. I should also mention that I'm new here, but am eager to help out. That's fabulous to...

Thanks for the PR! > it sadly requires an api token to work for which the process for acquiring can be found here Do you know how the authorization is...

The process for requesting an api key looks notably more involved and complicated than what we typically have to go through. What was your experience like?

> I used the game developer api key which just requires a google account login Gotcha. We're going to need some time to talk this over amongst the core team,...

Could we clarify the scope of what, if anything, is being requested of Shields here? For example, I would assume this is specifically targeted at the json/yaml badges, but the...