You will need the following:
- Contributor access to
elm-explorations/test - Able to run
runhaskellfrom the command line
How to publish a release:
- Check out the
masterbranch and make sure it is up-to-date. - Run
npx elm diffand make sure the version change is what you expect. - Run
npx elm bump. - Update
./tests/elm.json,./tests/test.sh, and./tests/MakeTestRegistry.hsto use the new version number. - Make sure the tests run
npm install && npm test - Running the tests should have modified
./tests/versions.dat(if not, you need to install Haskell such that you haverunhaskellon your path) - Commit the changes to
./elm.json,./tests/elm.json,./tests/test.sh,./tests/MakeTestRegistry.hs, and./tests/versions.dat - Run
npx elm publish-- it should fail complaining that the version is not tagged. - Tag and push the release using the git commands that elm publish suggested.
- Run
npx elm publishto publish the release.