Unity Automated Semver
Project case study
A GitHub Action for keeping the version numbers in Unity projects moving with a release workflow.
- Role
- Creator and developer
- Period
- 2020 to present
- Node.js
- JavaScript
- Unity
- GitHub Actions
The job
Version numbers live in more than one place in a game project. Updating them manually during releases is repetitive, and it is easy for one of those values to drift out of step.
What I built
Unity Automated Semver is a GitHub Action that increments the relevant version numbers as part of a Unity project workflow. It turns a manual release chore into a versioned, reviewable automation step.
What came out of it
The action is public on GitHub. It connects the game-development work in my portfolio with the build and release systems that make shipping software less fragile.