#21195 CI uses node 16 actions via `ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION` for Linux x86-64 & arm64 builds Issue created by huonw Describe the bug We use deprecated/unsecure node 16 to run some actions for doing a release. This isn't good and we should stop doing it. Potential options: 1. don't run the whole job in a container, just the individual steps (i.e. install/run actions on the default GHA runner, and only run specific steps within a container) 2. use Pants'

docker_environment

somehow to run the build 3. drop support for manylinux2014/glibc 2.17, i.e. increase our platform requirements Background: #21133, #21172 • Our linux releases are built within containers, to have manylinux2014 compatibility (glibc 2.17). https://github.com/huonw/pants/blob/a46b4a8fb27a4c14888bfc920b7e5f30d5f5635e/src/python/pants_release/generate_github_workflows.py#L881-L888 • These containers can run node16, but not node20 (requires glibc 2.23). • GitHub Actions now requires node20 (refs: one, two). • Thus, our actions are stuck on the versions that use node16, not the latest node20 ones. Pants version all OS Linux CI Additional info N/A pantsbuild/pants