Description:
Four days ago, Python installed to /opt/hostedtoolcache, but today it installed to .../_work/_tool. This manifested as a failure to find Python.h while building the native dependencies of python-ldap. Somehow, the installation procedure of python-ldap knew to put -I/opt/hostedtoolcache/Python/3.8.10/x64/include/python3.8 on the command line, but there was nothing in the /opt/hostedtoolcache folder. I'm currently working around this by setting the AGENT_TOOLSDIRECTORY environment variable to /opt/hostedtoolcache in my workflow.

Action version:
b55428b

Platform:

• Ubuntu
• macOS
• Windows

Runner type:

• Hosted
• Self-hosted

Tools version:
3.8.10

Repro steps:

      - name: Install Python 3.8.10
        uses: actions/setup-python@b55428b1882923874294fa556849718a1d7f2ca5
        with:
          python-version: '3.8.10'

Expected behavior:
I would expect this to install Python to /opt/hostedtoolcache like it previously did.

Actual behavior:
It now installs Python to .../_work/_tool within the job's workspace.