Set up Python in mergeback workflow #3261
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
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR adds Python setup to the post-release mergeback workflow and updates the Python setup action version in the release-initialise action. The changes ensure Python is available in the workflow environment, which became necessary after ubuntu-slim runners no longer include Python by default.
Key changes:
- Added Python 3.12 setup step to the post-release mergeback workflow
- Updated Python setup action from v5 to v6 in the release-initialise action
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
.github/workflows/post-release-mergeback.yml |
Added setup-python@v6 step to ensure Python 3.12 is available |
.github/actions/release-initialise/action.yml |
Updated Python setup action to v6 and quoted version string for consistency |
mbg
previously approved these changes
Oct 30, 2025
cd79269 to
3b96745
Compare
mbg
approved these changes
Oct 30, 2025
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.
We should have been setting up Python anyway, but the workflow's now failing since
ubuntu-slimdoesn't come with Python.Risk assessment
For internal use only. Please select the risk level of this change:
Which use cases does this change impact?
Dev/test only
How did/will you validate this change?
If something goes wrong after this change is released, what are the mitigation and rollback strategies?
How will you know if something goes wrong after this change is released?
Merge / deployment checklist