Marketplace upper bound version
# package-development
w
I get the problem @Jacob Overgaard with no upper bounds set - but it gives for a hell of a confusing experience to see what is actually OK to try out on V14.
j
Yes, but the alternative would be to force you to specify exactly which versions your package supports, and as you see, some packages are left from V10 and haven't been touched since, and they could potentially work for the versions released since then including V14
I know there's been a bit back and forth whether to specify a range or not. There will always be advantages and disadvantages one way or another.
s
Personally I think there's a only a few packages that will still work, while a lot of packages will definitely not work. I'd rather a few people would have to do a bit of extra work than all the people having to do releases to opt-out.
j
Didn't it used to be like that, @Sebastiaan , though? And then people didn't want to keep updating it every 6 months
s
I think we need probably need to make a split for v14 and then business as usual.. it might be ugly and we might need to hardcode some stuff but it's unrealistic to think that multiple dozens of people are going to re-release packages only to note that they do not support v14
s
I'm on team no-upper-bound, and I'm not going to re-release. But maybe umbraco-marketplace.json could have some information, like tested and works in version X, Y, Z etc.
IIRC umbraco-marketplace.json is fetched regularly from the source repository instead of nuget, right?
w
Yeh does seem a pain to realistically get all the versions that are incorrectly listing as v14 ready to do an update to restrict the upper bound. Following along for updates… 👀
h
I spent a bit of time just updating the version and adding upper bounds for the umbraco bits and pushed them to nuget, so hopefully mine will disappear from the v14 filter till I have time to check them and update where necessary. Am a little busy right now getting everything sorted for our hopeful relocation to Spain
m
I would prefer to “override” this default behavior using the marketplace JSON file
l
Hey folks. We are working to resolve this issue without you having to do anything. I'll report back soon hopefully 🤞
w
@Lotte any updates at all, just curious if I need to bump a patch version of packages so it depends solely on 14.0 release
s
More tomorrow @Warren Buckley ! 🙂 We've had a long day
l
Well it appears we didn't have to wait until tomorrow! https://marketplace.umbraco.com/search/?supportsUmbracoVersionNumber=14.0 is now showing only the packages that have opted in on v14. There are few showing up that shouldn't be there but that's because they have accidentally set the upper bound too high. So apart from those folks (who have been told) no-one needs to do anything 🎉
There are more plans being hatched about how to control the supported versions on the marketplace but this is good enough for now we think!
w
Any reason I didn't make the cut @Lotte ?
ExaminePeek and IconNoir pack missing from that page
l
I've been looking for your packages on the marketplace Warren and actually couldn't find them at all
Oh now I can, if I search by "Warren". It's been a long day
w
No worries Lotte
l
Congratulations Warren, I think you are the only person who has released a package only for v14+. I'm sure that's the issue. I'll pass it on!
w
Probably as its targeting the RC's
I have bumped ExaminePeek and will get marketplace to relist
And go turn off and enjoy a decent drink to celebrate v14 day or whatever
Nope bumping to 1.0.1 to depend on v14.0.0 hasn't made it appear here https://marketplace.umbraco.com/all/?supportsUmbracoVersionNumber=14.0 Suppose its the only package so far that is v14 only and not had prior versions for v13 etc... One to pass onto Andy or someone else, when this is seen tomorrow.
Do you know if there was any feedback or anything I needed to do to get these two tiny packages listed @Lotte correctly?
l
I've passed it on to Andy. There are a few edge cases that he's aware of - e.g. Bjarke's Open Street Map not showing up in search results either. Sorry pal, I know you want to see your hard work showing up in the list. Surely soon! 🤗
Fixes deployed to the marketplace. Apart from the DragonFly packages (that are there because the upper bound is incorrect, and needs new releases to fix), hopefully this is the correct list of packages now. Including Examine Peek @Warren Buckley 🎉
2 Views