Repository navigation
ci: upgrade actions/setup-python from v6 to v7 - #625
Merged
Merged
Conversation
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
Upgrade
actions/setup-pythonfromv6tov7(v7.1.0) at both call sites in.github/workflows/build-docs.yml(thebuildandvalidatejobs).Notes
python-version: 3.x, which is unchanged in v7.pip-installinput is not used here; dependencies are installed in a separate step.node24in both v6 and v7, so there is no runtime change.Verification
dotnet restore,dotnet build, anddotnet testpass locally (0 failures).build-docs.ymldispatched on the fork againstissues/619: https://github.com/adrianhall/CommunityToolkit-Datasync/actions/runs/42242518765buildandvalidatejobs succeeded, including "Install Python", "Install mkdocs", and the strict site build.deploywas skipped (branch dispatch), so nothing was published.Closes #619