Images do not support node 24, but recent conda-forge rendering requires it

[mattip]

Recently conda-forge smithy bumped the version of actions/checkout to v5.0.0 which requires node-24. This is not available in the images. It is annoying to patch rerendered recipes to use the older v4.1.4. How can the images be rebuilt with node-24?

[h-vetinari]

@jaimergp has got some WIP PRs in #72 and #73 (basically we're waiting for the return of @aktech). However, AFAICT that wouldn't yet fix the windows images, which are also affected by the same nodejs incompatibility

[mattip]

Cool, thanks. For ray we only need the linux images. I don't think the windows images come this repo?

machine_image: "/subscriptions/df033e15-d7e5-43a0-88b8-95b833d272f9/resourceGroups/cirun-runner-images-via-packer/providers/Microsoft.Compute/images/cirun-win22-dev"

[h-vetinari]

I don't think the windows images come this repo?

That was my point. I don't know where the windows images come from, probably only @aktech knows.

It'd be good to learn where and how this is changed, not least because of another problem: While debugging the libtorch upload issues, I'm running into a constraint that the npcap library I need for package capture cannot be installed (by its license) through the CLI.

FWICT, I need to install this in the image using the GUI (which is fine with the free license, because we'll only use it with Wireshark, which explicitly does not count towards the 5 concurrent users limit that we would otherwise have to enforce; we can also enforce that limit of 5 if there's any lingering doubts).

[jaimergp]

This PR (conda-forge/conda-smithy#2413) should mitigate the situation for now, once a new smithy release is out.

[h-vetinari]

It seems that v5 is now working? Saw it happen in conda-forge/tensorflow-feedstock#464, though I only realized after I had pushed the revert commit already 🤦

[mattip]

Since #73 was merged 3 days ago, I would expect the linux images to now support node-24. I don't know about other OSs though.

[jaimergp]

We probably can revert conda-forge/conda-smithy#2413 now.

[jaimergp]

Or wait, not sure if the Windows ones are fixed.

@aktech, do you know where the definitions for this image are hosted? If they are not public, maybe they can be contributed to conda-forge/.cirun?