Hi @lucas.stern,
I second that. We would love to see it work, but I think it is a chicken and egg issue. Cannot update projectVersion if the project is not packed and if it is packed then the repo is one change behind both in local and remote repos.
This occurs across all project / library / object repository types. Since the projectVersion key changes values under packing, the new file version (of project.json) needs to be committed again.
For now, we are used to this double commits. In short, we have become de-sensitized. Hopefully there is a solution for this 