26100.2 is not listed on my local UUPDump, what do I have to update to fix this? I don't want to be dependent on an external website.
Nope, it wasn't detected even when the new build wasn't released yet. In fact, sub-versions in general aren't detected somehow anymore (only Canary). Have updated API already, no change. Main builds like 26100.1 are listed fine. Maybe I need to update the search strings in the fetchdetect?
Just out of curiosity... @Paul Mercer, even though you keep the old website, could you integrate the new features that are openly available in uupdump's gitea into the Local Server? That would be interesting for learning. Also, where can I find the list of builds to update the "uupdump-get.cmd" script? I mean the list with values of this type: "25398 287 408". I don't know what the second and third values mean and when they need to be informed.
active maintainer(s) do not want another wave of shady UUP dump clones so no new features for now 25398 is the main build 287 is LCU, the first official release 408 is SKU, you always need SKU for server builds, otherwise it will fallback to the client builds
Thanks. No need to port everything, it's entirely sufficient to act only if something really breaks. Definitely don't need eye candy. Got 26200.5001 already with my old build, maybe because I already updated the API? Yeah, some id**ts ruining it for everyone. I definitely don't want to open a shady website, and only use it locally. Too bad they won't even provide it under NDA.
There are a few Chinese and other clones, some only partially functional. In case you mean the "shady uupdump clones".