🩹 Issue 17: fix deprecation warning

[thomasmerz]

Node.js 12 actions are deprecated.
For more information see:
https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.

Please update the following actions to use Node.js 16: actions/checkout@v2
Using version v3, latest or master: actions/checkout#689

Please update the following actions to use Node.js 16: actions/setup-node@v2, actions/cache@v2
Using version v2.285.0, latest or master: actions/setup-node/pull/414 and actions/cache/pull/729

This PR fixes issue #17 👍🏼

[inokawa]

In my opinion, using @master can cause security issue, but thank you for this PR!

[thomasmerz]

In my opinion, using @master can cause security issue, but thank you for this PR!

Someone (you?) has to make a tradeoff between security and staying current. In my decades of (linux) system administration I got less problems by staying current than by staying on fixed versions. Even security should be better when using "master", latest, current (call it what you want), because old security leaks will or might be fixed automatically very soon.

So what are your security concerns in detail using "master"? 🤔

[inokawa]

I thought I couldn't guarantee that the master is always safe especially for this repo, so choose tagged version.
However keeping using older version is surely a risk for all...

I'm not an expert for it and I'm not sure which is suitable for this kind of gist repo, but I should choose using master if I couldn't maintain this repo well.