Investigate the Many Actions Related Failures about create-html5-boilerplate

[roblarsen]

Eslint, Tests and Coverage and Release all seem to be perpetually red.

[roblarsen]

It's weird because npm ci fails repeatedly even after the package-lock.json has been rebuilt manually. I am pushing dependency updates with freshly generated dependency information and npm ci still fails. It's something to go on, but it doesn't make sense, on the surface.

[roblarsen]

Okay!

So, in the "Test and Coverage" build for chore(deps): bump npm from 8.13.1 to 8.13.2 it fails with the following:

npm ERR! `npm ci` can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with `npm install` before continuing.

But running npm ci on the same branch in codespaces is nicey nicey

@roblarsen ➜ /workspaces/create-html5-boilerplate (dependabot/npm_and_yarn/npm-8.13.2) $ npm ci

added 854 packages, and audited 1055 packages in 20s

112 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
@roblarsen ➜ /workspaces/create-html5-boilerplate (dependabot/npm_and_yarn/npm-8.13.2) $ 

I'm confused, but I've been confused before!

[roblarsen]

Okay! So it looks like it's a mismatch between versions of node. Using a package-lock generated in a lower version of node caused the issues in the Eslint job. I'll continue to investigate in #305

[roblarsen]

It's definitely a mismatch between the version numbers. "tests and coverage" actually fails now, because it's failing. It's actually run however. It just used to die.