Repository navigation
ci: fix the linter (no Python 3.9 on ubuntu-latest) and cut duplicate runs - #386
Merged
Merged
Conversation
ubuntu-latest is now Ubuntu 26.04, and actions/setup-python has no 3.9 build for it, so every linter run failed at the Set up Python step. black and ruff keep target-version py39 from pyproject.toml. Also trigger the linter when its own workflow file changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
ubuntu-latestis now Ubuntu 26.04.actions/setup-pythonhas no Python 3.9 build for it, so every linter run failed at Set up Python (The version '3.9' with architecture 'x64' was not found for Ubuntu 26.04). This also caused the failures on chore(deps): bump nbconvert from 7.17.1 to 7.17.2 #353 and test: cover from_processor with a stratigraphic column #297. The linter now uses Python 3.12. black and ruff still check against py39, becausetarget-versioninpyproject.tomlsets it.linter,packages,testerandqgis-compatnow have a concurrency group for each workflow and ref. A new PR run cancels the older one. Every push tomasterstill runs to the end.pushto every branch and also onpull_request, so each PR branch got linted twice. Thepushtrigger now applies tomasteronly.linter.ymlchanges.Not changed:
qgis-compat.ymlalso asks for 3.9, but it usessetup-uv, which downloads its own Python builds.Testing
🤖 Generated with Claude Code