vpre not working for feedz

[bradwilson]

Are you experiencing an issue with...

shields.io

🐞 Description

I'm updating my URLs to the new format for feedz, and the vpre version is pulling the release version, rather than the pre-release version.

According to https://feedz.io/org/xunit/repository/xunit/packages/xunit.v3 the latest version of 4.0.0-pre.11:

But when I try to retrieve the tag via Shields, this is what I see:

🔗 Link to the badge

https://img.shields.io/feedz/vpre/xunit/xunit/xunit.v3?logo=nuget&color=f58142

💡 Possible Solution

No response

[github-actions]

Badge tested using npm run badge https://img.shields.io/feedz/vpre/xunit/xunit/xunit.v3?logo=nuget&color=f58142
Output is available here

[PyvesB]

Hello @bradwilson 👋🏻

Thanks for reporting this. We're hitting the following API, and unfortunately, it's not returning any version more recent than 3.2.2: https://f.feedz.io/xunit/xunit/nuget/v3/registration/xunit.v3/index.json

I also tried adding the ?prerelease=true as a query parameter as this is what we do in our other Nuget v3 badge, to no avail.

Unless someone else with more expertise on this service has any ideas, I'd suggest opening an issue upstream.

[bradwilson]

Happy Saturday. 😀

I had been previously using:

https://img.shields.io/badge/endpoint.svg?url=https://f.feedz.io/xunit/xunit/shield/xunit.v3/latest&logo=nuget&color=f58142

This recently started giving back strange results:

I've had URLs like this for quite a while, long enough that I presume it predates your explicit support for feedz.io, but I don't recall when that was or how I came upon this URL concoction. It was when I went back to your docs to see if feedz was officially supported, and swapped all my usage over, that I noticed the resulting version was release rather than prerelease.

---

The embedded URL is interesting, because it seems to imply that it is something that's provided explicitly for use with shields.io or similar services (since it has /shield/ in its path).

Hitting that URL, it does show the correct latest version (as of the posting of this message):

{
  "schemaVersion": 1,
  "label": "feedz.io",
  "message": "4.0.0-pre.11",
  "color": "#0899c1",
  "logoSvg": "<svg xmlns=\"http://www.w3.org/2000/svg\" viewBox=\"0 0 197 197\"><g fill=\"#0899c1\"><rect x=\"60\" y=\"10\" width=\"46\" height=\"46\"/><rect x=\"10\" y=\"10\" width=\"46\" height=\"46\"/><rect x=\"10\" y=\"60\" width=\"46\" height=\"46\"/></g><g fill=\"white\"><rect x=\"113\" y=\"33\" width=\"74\" height=\"74\"/><rect x=\"113\" y=\"113\" width=\"74\" height=\"74\"/><rect x=\"32\" y=\"113\" width=\"74\" height=\"74\"/></g></svg>"
}

(Note: The logoSvg value is actually the feedz.io logo, which I presume is meant to be embedded inside the resulting shield in absence of a logo= query parameter. It is not the package logo.)

I'm not sure what changed about how the endpoint.svg URLs are supposed to be used on shields.io. Whether they're actually official or not, or have ever been, I honestly don't know. I assume the shift in content for these URLs was intended and not a bug, presumably because I was using the wrong URL (or using it in a way that you hadn't originally intended/expected). 😄

This does at least, I think, give you a potential way to craft a URL that could be parsed for vpre requests. I'm not sure if you have official contacts with feedz.io, but it might also be worth discussing with feedz whether the APIs you're currently using are correctly implemented.

In the meantime, I'm leaving all my changes in place to use official vpre URLs for shields.io for feedz, and hoping that one day soon they will start to light up with the correct versions. In the meantime, having them show release versions is better than the erroneous image above. 😉

[PyvesB]

Oh okay, I got it, the problem is way simpler than it sounds!

This is a side effect of #11583. As shown in the table there, you simply need to change /badge/endpoint to /endpoint in path of your badge URL. This should give what you're looking for:

https://img.shields.io/endpoint.svg?url=https://f.feedz.io/xunit/xunit/shield/xunit.v3/latest&logo=nuget&color=f58142

[bradwilson]

So, I updated a couple dozen repos and I'm hoping not to do it again. 😂 Should I expect a fix for vpre or is this a problem with feedz.io?

[PyvesB]

So, I updated a couple dozen repos and I'm hoping not to do it again. 😂

Shields.io, boosting your open-source contribution statistics since 2014 😎

As far as the "official" badges are concerned, it seems to be a problem with feedz.io. It would be great to open an issue upstream. Feel free to do so and report back here, otherwise I'll take care of it sometime during the weekend!

[bradwilson]

Shields.io, boosting your open-source contribution statistics since 2014 😎

🤣

I'll take care of it sometime during the weekend!

Thanks, I appreciate it! I'll let you own the issue with feedz. 😉