fix: Use a lifecycle script to create dev versions automatically afte…

…r publish

bids-validator/README.md

@@ -437,7 +437,7 @@ To run the linter which checks code conventions run `npm run lint`.
 
 ### Publishing
 
-Publishing is done with [Lerna](https://github.com/lerna/lerna). Use the command `npm run lernaPublish` and follow instructions to set a new version.
+Publishing is done with [Lerna](https://github.com/lerna/lerna). Use the command `npm run lerna publish` and follow instructions to set a new version.
 
 Using lerna publish will create a git commit with updated version information and create a version number tag for it, push the tag to GitHub, then publish to NPM and PyPI. The GitHub release is manual following that.
 

package.json

@@ -9,8 +9,7 @@
     "coverage": "./node_modules/.bin/jest --coverage",
     "codecov": "./node_modules/.bin/codecov",
     "test": "node bids-validator/bin/test-submodule-exists && jest",
-    "npmPublish": "cd bids-validator && publish",
-    "lernaPublish": "./node_modules/.bin/lerna publish && ./tools/post_publish.sh",
+    "postversion": "lerna version prerelease --preid dev --ignore-scripts",
     "web-dev": "cd bids-validator-web && npm run dev",
     "web-build": "cd bids-validator-web && npm run build",
     "web-start": "cd bids-validator-web && npm run build && npm start",