Upgrade usage of NodeJS from 12 to 16

[troley]

Ref. https://github.com/semestry/tasks/issues/204#issuecomment-1327291496

Proposed changes

Updates this action to the recommended NodeJS version.

Testing

N/A

Documentation

N/A

[johanwortel]

Change version in package.json? And while you're there upgrade the dependencies as well?

[troley]

Done. The amount of file changes comes from yarn upgrade. Then I also bumped the dependency versions up in the package.json.

[johanwortel]

The is no .gitignore. I suppose it was never built outside GitHub.

[johanwortel]

You better squash the commits. Now the git history contains all the ignored files.

[troley]

You better squash the commits. Now the git history contains all the ignored files.

Which commits? It will contain the ignored files anyway this once.

[MikeN123]

Uh, can we make sure that we are doing the right thing before we are throwing away half the repository?

[MikeN123]

https://docs.github.com/en/actions/creating-actions/creating-a-javascript-action#commit-tag-and-push-your-action-to-github explicitely mentions that you check in your node modules, so don't just go around throwing it away without thinking about it.

[MikeN123]

See comments.

[johanwortel]

Uh, can we make sure that we are doing the right thing before we are throwing away half the repository?

My mistake. I thought the original (master) version did not contain the node-modules. I now understand this repository is a runnable system and not a source to build artifacts from.

[Mario2804]

Can this be merged?

[johanwortel]

Can this be merged?

Yes.
I have already added tag v1.0.0 to tag the old (v1) version.
After the merge the tag v1 has to be put on the new master HEAD. From then on this will be the version used in GitHub workflows.
We can also add a v1.1.0 tag.

[MikeN123]

Merged, but it will need some tagging (add v1.1.0, add v1.0.0, move v1 tag)

[MikeN123]

VERY IN SYNC WE ARE TODAY JOHAN

[johanwortel]

I will continue.

[johanwortel]

Done.