Skip to content

Latest commit

 

History

History
57 lines (41 loc) · 2.09 KB

RELEASING.md

File metadata and controls

57 lines (41 loc) · 2.09 KB

📦 Let's package a release!

All platform precursor

To be able to publish a release you'll need to generate a GitHub access token by going to https://github.com/settings/tokens/new. The access token should have the repo scope/permission. Once you have the token, assign it to an environment variable (on macOS/linux):

export GH_TOKEN="<YOUR_TOKEN_HERE>"

macOS

In order to build a signed copy with working auto-update, you will need to join the Apple developer program and get a certificate. The Electron docs have a document on submitting your app to the app store, you only have to get through to the certificate step.

Release Process

  1. Make sure the release is working by running npm run dist and testing the built app inside the ./applications/desktop/dist/ folder. You can build for all platforms using npm run dist:all.

  2. Double check that publish will really work by running npm run verifyBeforePublish first

  3. Run lerna publish to publish everything, which also runs the verification steps. You will have to pick versions for everything.

  4. Run the following to ship the built desktop app

lerna run ship --scope nteract --stream
  1. From GitHub go to nteract's releases, verify everything works and edit the release notes. The name should follow our naming guidelines, namely that we use the last name of the next scientist in the list with an adjective in front. Example:
Last release: Avowed Avogadro
Next Scientist: Babbage
Next release: Babbling Babbage

My favorite way to pick the alliterative adjectives is using the local dictionary and our friend grep:

$ cat /usr/share/dict/words | grep "^babb"
babbitt
babbitter
babblative
babble
babblement
babbler
babblesome
babbling
babblingly
babblish
babblishly
babbly
babby
  1. Once you're ready click "Publish release". On Mac and Windows the update will be automatically downloaded and installed.