Actor name, version, buildTag, and environmentVariables are currently only used when you deploy your Actor using the Apify CLI and not when deployed, for example, via GitHub integration. There, it serves for informative purposes only.
The apify push command should only really be used for quickly pushing and testing Actors on the platform during development. If you are ready to make your Actor public, use a Git repository instead, as you will reap the benefits of using Git and others will be able to contribute to the project.
Creating a new build increments the PATCH version, but i also want to set the MAJOR and MINOR versions. Is there a way I'm missing?
You can specify a custom major and minor build version when you "fork" your build on the platform, from the Source tab. Every build automatically increases the patch version: this behavior cannot be customized. On the other hand, you are free to manage the actor version as you prefer.
I guess there is no simpler way to bump the version and rebuild automatically, keeping the same env variables and so on? (this endpoint requires passing everything again in the payload