Repository navigation
Set up the primary Python version in the docs workflow - #208
Merged
Merged
Conversation
The docs job installed the project on the setup action's default Python, 3.11, so a project whose requires-python is newer failed to resolve its own wheel. It now asks for python_version_primary like the build job. Signed-off-by: Tim Paine <3105306+timkpaine@users.noreply.github.com>
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
1 participant
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.
The docs job set up Python without a version, so it ran on the setup action's default, 3.11. A project with
requires-python = ">=3.12"then fails at "Install from wheel" withNo solution found when resolving dependencies(dau-scheduler's first docs run). The job now passespython_version_primarythe way the build job does, in every variant that renders a docs workflow.