I had a question about UUPD. Someone wanted to change from another provider to UUPD, but they needed a specific feature. They could have coded this themselves or submitted a PR, but after some conversation, I said I would add it in the next iteration of both 2.0.x and 2.1-alpha, as I actually saw it as an omission in my original design rather than a feature request.
They needed version number sending; one of their plugins introduces total breaking changes between major versions, think 2.x to 3.x and the need to be able to separate these. The easy way to do this was to add an installed_version query parameter so the server can respond accordingly; after all, this isn’t that uncommon an issue. AutomatticCSS has just done this exact thing with version 4. So I saw this as an omission rather than a feature request and got to work. I even built testing for it in my modification to WPUPDATEServer – https://github.com/stingray82/wp-update-server-modifications
I already had this working in version 2.0.1 and the alpha.2 build but on thinking about it after I had written it it got me thinking that plugin owners may want to send other query parameters and even headers when sending update and version requests, so in the next version, I tested this using a modified wpupdateserver, and it all worked, so this was released today also as 2.0.2 and 2.1-alpha.3.
I am determined to make UUPD the most efficient, easy-to-use single-file drop-in to handle WordPress updates, and that journey continues even dozens of releases later.
UUPD 2.1-alpha.3 also includes the new signed updates feature and is testing well in real-world use.
