npm ci on Windows with Node 8

[moltar]

This isn't a problem with the code, but the Action example I think might have a fault.

It uses a matrix, and windows + Node 8 I think might not have ci yet, because the run fails:

Run npm ci && npm t

Usage: npm <command>

where <command> is one of:
    access, adduser, bin, bugs, c, cache, completion, config,
    ddp, dedupe, deprecate, dist-tag, docs, doctor, edit,
    explore, get, help, help-search, i, init, install,
    install-test, it, link, list, ln, login, logout, ls,
    outdated, owner, pack, ping, prefix, profile, prune,
    publish, rb, rebuild, repo, restart, root, run, run-script,
    s, se, search, set, shrinkwrap, star, stars, start, stop, t,
    team, test, token, tst, un, uninstall, unpublish, unstar,
    up, update, v, version, view, whoami

npm <command> -h     quick help on <command>
npm -l           display full usage info
npm help <term>  search for help on <term>
npm help npm     involved overview

Specify configs in the ini-formatted file:
    C:\Users\runneradmin\.npmrc
or on the command line via: npm <command> --key value
Config info can be viewed via: npm help config

npm@5.6.0 C:\hostedtoolcache\windows\node\8.10.0\x64\node_modules\npm

[moltar]

Settled on the following:

        run: npm i -g npm && npm ci && npm t

Can create PR with a doc fix.

[moltar]

Another tip:

        run: npx semantic-release@latest

The @latest release has a fix for using standard GITHUB_TOKEN.

So this is enough, and don't need to create a personal token:

          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

[moltar]

But, @latest if I understand correctly, is alpha, so might not be too stable.

[moltar]

And thanks for the package, highly appreciated and saved me from so much tinkering!!

[moltar]

Info re @latest: semantic-release/semantic-release#974 (comment)