create-release VS PixelVision8

is it possible to write a GitHub Action that would compile my Rust binary for 3 different systems (Mac, Linux and Windows), create a new release on GitHub and upload those binaries to it? I've found this action, and also this one. Those seem to be able to do what I need, but they are both archived and not actively maintained for quite a while. Is it even safe to use those? I know that Actions can be used to compile my binaries as I've already been using them to run tests on all three systems, but I want to know if it is possible upload those binaries and create release with them. Also, is it possible to read version number from a file in my repository with GitHub Actions to set that as a name for a new release?

The thing you're trying to do is generate a release: https://github.com/actions/create-release

Creates a new release and tag ( actions/create-release@v1 )

Sprites in Power Vision 8 are all 8x8 pixels in size, when your game starts up the file "sprites.png" is loaded and chopped up in to 8x8 images. Each of these images is then loaded into the memory of the sprite chip until it runs out of space. Each sprite is given an index number at load time (starting from 0) and you can use that index to fetch a particular sprite.

We don't talk enough about how much it "costs" to work on large open-source projects by yourself. I summed up my experiences building Pixel Vision 8 for the past 6 years in "The Dark Side of Supporting an Open-Source Project" on u/hashnode - https://jessefreeman.hashnode.dev/the-dark-side-of-supporting-an-open-source-project

Space Station 8 is a Micro Platformer created in 72 hours for Ludum Dare 49 based on a game I used to play on my original Macintosh called Spacestation Pheta. Space Station 8 is also heavily inspired by Bitsy and my Fantasy Console, Pixel Vision 8, which I used to create the game.

I have been working on my game engine, Pixel Vision 8, for the better part of 6 years now. One of the challenges of working on any sizeable open source project is writing all the documentation and tutorials. I've always been fascinated with designing automated build systems, and it occurred to me that I could create a tool to help me streamline this entire process. The idea was straightforward, could I analyze a code file and break it down into individual steps?