no such option: --root-user-action

[HKongCC]

Description:
Unable to setup-python@v4. Fails on downloading pip packages, was working yesterday, but the same workflow fails today.

Update: Also appears that yesterday it successfully upgraded pip to 24.0 so it had the --root-user-action argument available, but today the upgrade isn't happening and stays on 22.0.4 properly so the --root-user-action argument is throwing an error.

Action version:
setup-python@v4

Platform:

• Ubuntu
• macOS
• Windows

Runner type:

• Hosted
• Self-hosted

Tools version:
Python 3.9.13

Repro steps:
Use actions/setup-python@v4, with python version 3.9.13, and x64 architecture

Expected behavior:
Setup python successfully

Actual behavior:
Fails on pip install with the following message
no such option: --root-user-action

[forgingdestiny]

+1 seeing similar issue on v2 and v4

[benterem]

+1 same

[nikita-malininn]

Try to change to Python versions older than 12h ago in actions - https://github.com/actions/python-versions/releases
(found it spontaneously)
upd. For example, switch from broken 3.8.10 to 3.8.18 solves the issue.

[HKongCC]

Good eye @KodiaqQ , looks like this is the breaking PR for those versions actions/python-versions#259

[nikita-malininn]

Good eye @KodiaqQ , looks like this is the breaking PR for those versions actions/python-versions#259

Yeah. We've found this PR earlier than a solution with a version switch.

[tblom]

Same on v5

[forgingdestiny]

Does anyone know if there will be a new release or something similar to fix? Using a different python version isn't an option for most production builds without going through an upgrade process. 🤔 thinking through alternatives here. the pinned version should prevent this fwiw.

[Rjevski]

@HKongCC had a quick look and doesn't seem like that's the case unfortunately - I don't see any parameter here that would allow to override it. I temporarily switched my affected projects to use 3.9.19 version which seems unaffected. Obviously hoping that upstream will yank the broken 3.9.13 build so I can roll back my workaround.

[v-HarithaVattikuti]

Hello @HKongCC
Thank you for creating this issue. We will investigate it and get back to you as soon as we have some feedback.

[aram-eskandari]

i can confirm what @Rjevski already stated: upgrading from my old version of 3.9.13 to 3.9.19 worked. Whenever this issue is resolved i will revert my project back to 3.9.13.

[goharShoukat]

Do we have an ETA on this? Moving Production builds to a newer version is not quite as straightforward!

[Rjevski]

@goharShoukat you could look into using PyEnv in the meantime? A bit of manual work but should be doable if it's time-critical.