A lot, including Umbraco’s own Hubspot integration for example have this sort of display on the versions they support.
I have not added apps to the Marketplace myself so I do not know the options provided but I have recently tried to use 6 or 7 packages and none of them actually support later versions of Umbraco.
Nearly all of them were ONLY V8 and some with SOME support for V9.
The Umbraco DX Hubspot one for example only supports .net8 and the back office components are all still Angular.
For any package with github viewable code, I have seen the similar.
How is the version done? Manually?
If so I do not think it is right or if it has a default that it just says it supports all versions because it is not true and wastes peoples time.
This is flawed and not working as intended.
I have counted 17 Packages alone right now marked as U17 supported and actually are not.
I contacted the author. He has not updated the package to support the new backoffice UI but you can clearly see it says U17.
If I had time I am pretty positive I could go through many U17 marked packages and find they do not work.
The Hubspot ones ONLY have nuget version 8.0 listed, you can not choose anything higher and the main branch and marketplace version is for the version 8.
You start a project to support later versions but not released it or is main branch
Your latest version if existing not configured for nuget
You do not have and have not worked on new versions to support those Umbraco versions
But it can still be listed as up to U17 supported.
I think there are things that need fixing with this and I think there should also be a “verify” feature for the latest version. If enough people verify it is working or Umbraco has then it shows a “Verified” tag, If there is an issue that to could be displayed.
Way to many packages not actually U17 supported basically that state they are.
I actually think the idea of some base verification of packages is a pretty good idea, and would open up another avenue for people to contribute to the community, for people who may not want to dive into doing PRs or packages.
In practicality I’m not entirely sure how you could go about it - like I can easily dream up an overly convoluted idea, because how do you verify the verifier? (turtles all the way down). What is stopping people from verifying their own packages, or verifying without checkin anything.
The complex solution could be yet another package, umbraco.community.packageverify or whatever. The person verifying a package runs umbraco with the package to be verified in question and the verifier package. It adds a little verify dashboard in umbraco where the person can submit a verification, perhaps with notes. Sign it with “Umbraco Id” and suddenly there is tracability for who said what works which should be a tall enouh fence to prevent abuse I would think.
As I said, overly convoluted and possibly a terrible idea - you just inspired me.
The issue here is related to the package not having an upper bound on the Umbraco dependency - if the package is distributed with >= 13.x, Marketplace trusts the open range, and lists the package as working on all version >= 13.x. It’s up to the package maintainers to either make that support true, or use ranged version dependencies for known supported Umbraco versions.
I think some form of package verification is a great idea, that way people can easily see if a package works and does what it says it does, and low rated packages can be raised with the authors and potentially removed or flagged.
Also, version compatibility would be a good idea, I’m pretty sure the old packages dashboard/page had that but I don’t know who rated compatibility across versions. Maybe one for discussion further with HQ?
