Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CI] Python 3.7 not available in ubuntu-latest #5082

Closed
zeritti opened this issue Dec 21, 2024 · 1 comment · Fixed by #5085
Closed

[CI] Python 3.7 not available in ubuntu-latest #5082

zeritti opened this issue Dec 21, 2024 · 1 comment · Fixed by #5085
Assignees
Labels
bug Something isn't working

Comments

@zeritti
Copy link
Member

zeritti commented Dec 21, 2024

Describe the bug a clear and concise description of what the bug is.

Step actions/setup-python@5 in workflow job lint-test set with python-version=3.7 fails as this version is not available in the current image ubuntu-latest. It appears that the image has already been updated to 24.04 which does not include python 3.7 any longer:

  Error: The version '3.7' with architecture 'x64' was not found for Ubuntu 24.04.
  The list of all available versions can be found here:
  https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json

Steps with that action fail, e.g. https://github.com/prometheus-community/helm-charts/actions/runs/12444946805/job/34745736173?pr=5053

On image update to Ubuntu 24.04: Ubuntu-latest workflows will use Ubuntu-24.04 image

The affected workflow jobs may need an adjustment.

@zeritti zeritti added the bug Something isn't working label Dec 21, 2024
@zeritti zeritti changed the title [CI] Python 3.7 not availale in ubuntu-latest [CI] Python 3.7 not available in ubuntu-latest Dec 21, 2024
@dotdc dotdc self-assigned this Dec 22, 2024
@dotdc
Copy link
Member

dotdc commented Dec 22, 2024

PR to fix: #5085

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants