Beth Griggs

Actually, [windows is still unhappy](https://ci.nodejs.org/job/citgm-smoker-nobuild/nodes=win10-vs2019/1165/console): ``` 22:52:34 error: | > [email protected] prepublish 22:52:34 error: | > !(type not-in-publish) || not-in-publish || npm run prepublishOnly 22:52:34 error: | 22:52:34 error: |...

It seems to have gotten much further, but still bailing out of the job at the end on Windows 🤔 - https://ci.nodejs.org/job/citgm-smoker-nobuild/nodes=win10-vs2019/1171/consoleText

I was going to open a PR to remove Node.js 12 from [the CI workflow](https://github.com/nodejs/citgm/blob/main/.github/workflows/nodejs.yml#L39), but then realised this would be a preferable approach (IMO). +1 to doing this.

ping @nodejs/citgm on behalf of @andrewhughes101

Pipeline run: https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker-pipeline/189/ (on all platforms, but we can just looking to see if s390x now passes) Edit: properly configured the job 😅

> We are struggling to keep npm up to date > I'm really new to the Node infra and procedures so feel free to correct me, but isn't it something...

> From build call today: Potentially use as a way of retriggering the web site when a potential race condition occurs with the rebuid triggers? Refs: https://github.com/nodejs/build/issues/2792

Is it expected/intentional that the rhel8-release-sources job is not using ccache?

Oh, it wasn't obvious from the job output (comparing to how it's called in other jobs). I was just suspicious as all other platforms took 10-30 minute mark whereas that...

cc @nodejs/build (should this be moved to nodejs/build repository)