Python 3.11 missing?

[samjarrett]

Hello!

Hopefully I've got the right repo to report this in. We use renovate via the github action. We configure it like this:

    - id: renovate-scan
      name: Renovate
      uses: renovatebot/[email protected]
      with:
        renovate-version: full
        token: ${{ secrets.GITHUB_TOKEN }}
      env:
        RENOVATE_REPOSITORIES: ""  # repo path
        LOG_LEVEL: debug

When it encounters python 3.11 in use, it adds the following comment:

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Pipfile.lock

Command failed: pipenv lock
Warning: Python 3.11 was not found on your system...
Neither 'pyenv' nor 'asdf' could be found to install Python.
You can specify specific versions of Python with:
$ pipenv --python path/to/python

This is only an issue with python 3.11. 3.10 and below work without issue.

[viceice]

https://github.com/renovatebot/base-image

is the base image which uses python 3.12, so your error is expected.

why do you use the full image instead of the slim / normal image which can install required versions on the fly.

[samjarrett]

Hello! I'm unsure why 3.8/3.9 etc have no issue then?

We use the full image because we had a lot of issues with the normal image installing things on the fly .....not being able to install a different version of a different language, but the full had it/has it bundled in.

[viceice]

maybe because the other projects allow python 3.12?

[samjarrett]

yeah.. I'm not sure. I tried replicating it with the default image again and it seems to no longer be a problem (this was a few months ago that we saw this - may've been a transient issue?). Thanks for the chat/help :)