fix/current version

[urwrstkn8mare]

it doesn't really matter that the zips aren't in the releases yet imo

we should probably think about the security implications of being able to edit the release after the fact. the only real solution is to find a file hosting provider provides a url that depends on the contents of the file (url changes if file changes). we could do this by just hosting the files in a repo. but tbh if the members of the repo are trusted it should be alr

[UncleGoogle]

IMO lets focus now on:

• finishing release action (yea, that on me, but if you have time to help, please create dummy repo with plugin-like structure and currenct_version.json file to test it live)
• add sync action to .github here (not blocked, we can streamline updates to this repo this way)

[ABaumher]

Let me get the release up there so it actually works, lol.

[ABaumher]

some files are part of the repo from the rebase that should not be. They aren't breaking, but if we are doing fixes, may as well do all of it.

[ABaumher]

The orig file in protobuf_files just sort of magically appeared and can be removed. It does not affect anything. But it's not blocking so you can merge this in.

[ABaumher]

nvm, i just made it a branch on my repo and dealt with it there. See #3

Edit: All of this started because i was going to make the zips for the Nebula release based on the rebase code and wanted to make sure i didn't break anything. (I didn't) Holy Toledo, Batman!