@GetMem, can you update Indy, please? There have been 18 checkins to Indy's GitHub repository since the last time Indy was updated in OPM.
I realize this has been a manual process for you so far. So I'm considering setting up GitHub Releases for future Indy releases.
It looks like the .zip file currently in OPM is just a copy of Indy's /Lib source folder renamed to /Indy10 and pruned a little. For a seamless transition, I would have to replicate that same .zip structure, correct? I could setup new releases in GitHub with that .zip structure, but that would require making a new branch of the repository for each release, and the root folder would be /Lib, unless I rename it to /Indy10 in each branch (now, I'm starting to wonder if most of what is currently in Indy's repository is not actually needed by end users and should be moved to a separate repository just for Indy's team members).
If the JSON file used by OPM is updated to point at these GitHub releases for downloads, would that different base folder name cause issues when Lazarus users try to update their existing Indy installations? Otherwise, worst case, I suppose I could just create new .zip files manually and attach them to each GitHub release, rather than (or addition to) linking each release to the repository code.