Skip to content

Latest commit

 

History

History
18 lines (14 loc) · 985 Bytes

PUBLISHING.md

File metadata and controls

18 lines (14 loc) · 985 Bytes

You will need the following:

  • Contributor access to elm-explorations/test
  • Able to run runhaskell from the command line

How to publish a release:

  1. Check out the master branch and make sure it is up-to-date.
  2. Run npx elm diff and make sure the version change is what you expect.
  3. Run npx elm bump.
  4. Update ./tests/elm.json, ./tests/test.sh, and ./tests/MakeTestRegistry.hs to use the new version number.
  5. Make sure the tests run npm install && npm test
  6. Running the tests should have modified ./tests/versions.dat (if not, you need to install Haskell such that you have runhaskell on your path)
  7. Commit the changes to ./elm.json, ./tests/elm.json, ./tests/test.sh, ./tests/MakeTestRegistry.hs, and ./tests/versions.dat
  8. Run npx elm publish -- it should fail complaining that the version is not tagged.
  9. Tag and push the release using the git commands that elm publish suggested.
  10. Run npx elm publish to publish the release.