Closed jNullj closed 1 month ago
Messages | |
---|---|
:book: | :sparkles: Thanks for your contribution to Shields, @jNullj! |
Generated by :no_entry_sign: dangerJS against 5f17d1f8c1d1943e7ee65bfff0a6fe7251cba2a9
Thanks. Agree we should just get rid of this. When we need to remove a service, we initially replace it with a message that says "no longer available". That way users get some kind of explanation of what happened instead of just a in their README. Then we delete it after a year (or whenever we do a clear out).
There's docs on this in https://github.com/badges/shields/blob/master/doc/deprecating-badges.md and you could look at something like https://github.com/badges/shields/pull/10371 as an example.
My bad, didn't notice this section of the docs. Thanks for the example it saved me some time.
http://localhost:8080/hackage-deps/v/test
In the wild Github has about 2k usages of this badge
Badge will always return up to date falsely as the upstream site is closed and looking for someone to take over.
The first test if a package exist will always return 200 OK even when non existing as we get the landing page.
Then we will never get "outdated dependencies" as the landing page doesn't include that text.
I looked into the https://hackage.haskell.org/api and couldn't find a quick way to replace the current upstream.
Therefor i propose we remove this badge, this is misleading at best as it's now.