Skip to content

Latest commit

 

History

History
74 lines (49 loc) · 1.27 KB

PUBLISHING.md

File metadata and controls

74 lines (49 loc) · 1.27 KB

How to publish a new version

Compile and test everything

Build and test automatically in Node.

yarn node-test

Build test website and check manually in browsers.

yarn web-test

Should check at least:

  • Chrome
  • Firefox
  • Safari

Determine new version number for Elm package

Elm enforces strict rules for incrementing version numbers for packaging, so need to ask Elm for what the next version number to be like by running elm bump.

elm bump

The command will update elm.json file with the new version number depending on the nature of the changes made.

Update version number in the code

The following files need to be updated with the new Elm package version in elm.json file:

  • package.json
  • src/TaskPort.elm (see moduleVersion)
  • js/taskport.js (see MODULE_VERSION)

Verify that version changes are successful by running Node tests again:

yarn node-test

Release Elm package

  • Check-in everything to the repo
  • Tag code in the main branch with the updated version number:
git tag <version>
  • Push the tag to the repo
git push --tags
  • Publish Elm package
elm publish

Release NPM package

yarn publish

Post-publishing

Add release notes to CHANGES.