Since it is hard to enforce consistant commit messages across multiple contributors, we will let them follow the place holder version number as mentioned in Contribution Guide as long as they don't push to master branch directly. This also means whoever is merging the pull request (PR) needs to do a number of steps before merging to ensure that the version numbers, commit messages and codes are in the right format and working properly without brokages and conflicts. Follow the steps below if you are a reviewer who is going to merge a PR to the master.
Of course, if you already know the process and have already been commiting directly to the master branch, then you may continue as long as you continue to pay attention to ensure that the version numbers, commit messages and codes are in the right format and working properly without brokages and conflicts.
Check if the update works as intended.
Check if the update does not break existing code.
Update version number in package.json.
Squash and merge PR with commit message of the format vw.x.y[-beta.z]: Write commit message. where w, x, y, z are integers and [this means optional as needed for beta].