mkdir tmp
cd tmp
git clone [email protected]:geomoose/gm3.git
cd gm3
Only continue if the following completes successfully.
./install_test_deps.sh
npm test
Note: npm install
doesn't install all the packages needed for complete testing because it testing requires two packages that require being built from C modules. This causes no end of trouble for people trying to install/build GeoMoose on systems without integrated system wide compilers (looking at you Windows).
Updates package.json, creates a commit and an annotated git tag.
npm version major (or minor or patch ...)
This will trigger a build on https://demo.geomoose.org. Wait for new files in /downloads/ before continuing. Note: there is currently a race condition here if you don't wait long enough or if someone else pushes to main
before you complete the next step.
These files can also be created manually using the other scripts in this repo.
git push --tags origin HEAD
cd ..
git clone [email protected]:geomoose/gm3-demo-data.git
cd gm3-demo-data
git tag -a v3.0.0
git push --tags
git checkout v3.6.0 # checkout the version to publish
git clean -fxd # make sure don't have extra files hanging out
npm login # login into npm
npm install # install node_modules
npm publish # build and upload to npm
We don't want new dev commits overwriting our release. (package.json needs to be updated).
git checkout main
#npm version prepatch would be more standard
npm version --no-git-tag-version 3.0.1-beta
git add package.json package-lock.json
git commit -m 'Bump main branch to next dev version'
git push
Files on www.geomoose.org
- geomoose-website/source/news.rst
- geomoose-website/source/download.rst
- geomoose-website/source/releases/.rst
- Announce on geomoose-users list
- Consider announcing on discuss and/or announce lists as well although those should be more general and slightly longer with more details about the capabilities
- Create a release on github in geomoose/gm3