[ BUG ] Cannot use built-in Updater.

[D4rkov]

Checking for updates results in an error:
{
"message": "GET https://api.github.com/repos/Vendicated/Vencord/compare/6e11973a (BetterVencord patchset built by ff8733c)...HEAD: 404 Not Found\n{"message":"Not Found","documentation_url":"https://docs.github.com/rest/commits/commits#compare-two-commits\",\"status\":\"404\"}",
"name": "Error",
"stack": "Error: GET https://api.github.com/repos/Vendicated/Vencord/compare/6e11973a (BetterVencord patchset built by ff8733c)...HEAD: 404 Not Found\n{"message":"Not Found","documentation_url":"https://docs.github.com/rest/commits/commits#compare-two-commits\",\"status\":\"404\"}\n at $t (file:///VencordPatcher:6:20)\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n at async Bt (file:///VencordPatcher:6:63)\n at async Mn (file:///VencordPatcher:6:897)\n at async file:///VencordPatcher:6:524\n at async Session. (node:electron/js2c/browser_init:2:108261)"
}

[Davilarek]

Yes... that's not new. The built in updater must be somehow patched to support the repo scheme. I'm not sure yet how to do that, but I'm working on it.

[Davilarek]

I almost finished a fix that would allow checking for updates, but updating (from the client itself) is unlikely to work.
One may ask why? Well, to do that I would have to publish Release artifacts or bake complex building algorithm into the app itself. That's doable but uhhhh really? One can argue that why not just add release artifacts? Because at the moment the project is Licenseless, which essentially means proprietary. Only way to make this work would be to make me apply GPL 3.0 to the build system, but I'm afraid of a certain social problem coming to this project, a problem that had appeared in the original repository. If I publish binaries, I become the distributor of a GPL derivative, and then I'm forced to license the whole thing under GPL. I'm willing to discuss this topic.
EDIT: To clarify. I spent last 6 years in open source communities and use open source software everyday. I heavily believe in FOSS movements, and I'm against public code-only repositories. Nonetheless, I believe (from a recent encounter related to the old repo, before diverging from Davilarek/Vencord) that this decision will help me avoid a potentially harmful (to the project, to me as a contributor and people using the project) drama that was partially caused by nature of open software where people take "help others by extending the software on your own" a step too far, which proven me wrong about the assumption that when people do expand your stuff, they feel the obligation to credit the original creator as someone actually meaningful to the project's origin.

[D4rkov]

So just git pull and rebuild and reinject everytime?

Also I see your stance, I guess if that's for the better, then so be it.

EDIT:
Also Vencord Devs could easily add your compat layer into vencord as a plugin, no?
You could reach out to them idk what the complications are.

[Davilarek]

So just git pull and rebuild and reinject everytime?

Yes.

Also I see your stance, I guess if that's for the better, then so be it.

I am not sure if that's for the better, that's why I mentioned I'm open for discussion on this topic.

Also Vencord Devs could easily add your compat layer into vencord as a plugin, no?
You could reach out to them idk what the complications are.

Yes, they could. No, they don't want to. Vencord Developers repeatedly mentioned they don't want BD plugin support. I personally believe this is a good decision on their side.

[D4rkov]

Yea I don't really know about all that. Just do whatever you're comfortable with I guess? I really don't got any insight about all that.