Security Notice: GitLab has uncovered a widespread malicious npm supply-chain attack that potentially can destroy user data. All teams are required to audit packages. Further information can be found under the Computer Security Report for November 2025 and the original blog post in https://about.gitlab.com/blog/gitlab-discovers-widespread-npm-supply-chain-attack/

Follow-up from "Support alma9 containers"

The following discussion from !84 (merged) should be addressed:

@clemenci started a discussion: (+4 comments)
I think we need a different approach, based on the target platform, so
- x86_64_v3-centos7-gcc11-opt+g -> /cvmfs/cernvm-prod.cern.ch/cvm4
- x86_64_v2-el9-gcc12-opt -> .../os-base/alma9-devel/prod/amd64
- armv8.1_a-el9-gcc12-opt -> .../os-base/alma9-devel/prod/arm64v8
Then you can use inspection of the host CPU to decide which platforms you can run, e.g. if the CPU is x86_64_v3 capable or is compatible with armv8.1_a.