casperkristiansson/CPython Patch PR Action
Automate CPython patch updates across Dockerfiles, workflows, and config files.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Maintainedlast commit Dec 5, 2025
- License
- MIT
Pinned Snippet
uses: casperkristiansson/python-version-patch-pr@5a6596151ca42db0ffd06d8410eaed7efca09b50 # v1.6.1tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| track | CPython minor series to track (for example 3.13). | no | 3.13 |
| include_prerelease | Include pre-release tags when resolving the latest patch version. | no | false |
| paths | Newline-separated glob patterns that determine which files to scan for pinned Python versions. | no | .github/workflows/**/*.yml Dockerfile **/Dockerfile **/*.python-version **/runtime.txt **/pyproject.toml |
| automerge | Attempt to automerge the pull request after required checks succeed. | no | false |
| dry_run | Skip file modifications and output the planned changes only. | no | false |
| security_keywords | Newline-separated keywords that must appear in the release notes before applying an update. | no | "" |
Outputs
| name | description |
|---|---|
| new_version | Resolved CPython patch version (for example 3.13.5). |
| files_changed | JSON array listing files that were updated. |
| change_matrix | JSON object suitable for GitHub Actions matrix with changed files and new version. |
| skipped_reason | Machine-readable reason describing why no update was applied. |