Set up automatic semantic release

[masakudamatsu]

5 Feb 2021: For the time being, we will manually manage the semantic versioning by following GitHub help:
https://docs.github.com/en/github/administering-a-repository/managing-releases-in-a-repository

For work-in-progress code, see the stash prefixed with the issue number

Sources:

Kent C Dodds: https://egghead.io/lessons/javascript-automating-releases-with-semantic-release

Installation

• https://github.com/semantic-release/semantic-release/blob/master/docs/usage/installation.md#installation

Configuration

npx semantic-release-cli setup

and follow the wizard. For detail, see

• https://github.com/semantic-release/semantic-release/blob/master/docs/usage/getting-started.md#getting-started
• https://github.com/semantic-release/cli#what-it-does

This will create .travis.yml.

As of Feb 2021, the semantic-release-cli does not work with GitHub. See semantic-release/cli#345

Edit package.json

Set

"version": "0.0.0-semantically-released"

• when I run npm install, npm will give me a warning if my package doesn't have a version (Kent C Dodds)

Edit .travis.yml

Add

script:
  - npm run test

How semantic-release works with Git branches:

https://github.com/semantic-release/semantic-release/blob/master/docs/recipes/distribution-channels.md

[masakudamatsu]

We cannot implement this feature at this moment.

• semantic-release-cli setup does not work, apparently because GitHub has changed its authentication system and the semantic-release-cli is not yet updated accordingly
  • [GitHub] Deprecation Notice semantic-release/cli#345
• Manual setup is hard because I fail to encrypt an authentication key by following Travis CI Docs:
  • https://docs.travis-ci.com/user/encryption-keys#usage