chore: bump action versions in README examples and docker image to v9#437
Merged
chore: bump action versions in README examples and docker image to v9#437
Conversation
## What Updated all GitHub Action version references in README.md examples and the Docker image tag in action.yml to their latest major versions. ## Why The documented examples and action definition referenced outdated action versions. Bumping to current versions ensures users get security fixes, performance improvements, and new features from upstream dependencies. ## Notes - `actions/checkout` bumped from v4 to v6 with `persist-credentials: false` added for security hardening - `peter-evans/create-issue-from-file` bumped from v5 to v6 - `actions/github-script` bumped from v6 to v8 - The `action.yml` Docker image tag change from v7 to v9 means this is a breaking release boundary — consumers pinned to v7 will not pick up this change until they update their workflow references Signed-off-by: jmeridth <jmeridth@gmail.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR bumps version references for GitHub Actions used in README example workflows and updates the Docker image tag in action.yml to align with the repository's latest release (v9). It also adds persist-credentials: false to actions/checkout steps in the README examples for security hardening.
Changes:
- Updated all
github-community-projects/stale-reposaction references fromv7tov9across all README examples - Updated
actions/checkoutfromv4tov6withpersist-credentials: falsein two README example workflows - Updated
peter-evans/create-issue-from-filefromv5tov6andactions/github-scriptfromv6tov8in README examples, and updated the Docker image tag fromv7tov9inaction.yml
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
action.yml |
Docker image tag updated from v7 to v9 |
README.md |
All example action version references bumped to their claimed latest versions |
zkoppert
approved these changes
Feb 28, 2026
zkoppert
reviewed
Feb 28, 2026
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.
What
Our latest release is v9, we need the references of stale-repos to be v9, especially the action.yml
Updated all GitHub Action version references in README.md examples and the Docker image tag in action.yml to their latest major versions.
Why
The documented examples and action definition referenced outdated action versions. Bumping to current versions ensures users get security fixes, performance improvements, and new features from upstream dependencies.
Notes
actions/checkoutbumped from v4 to v6 withpersist-credentials: falseadded for security hardeningpeter-evans/create-issue-from-filebumped from v5 to v6actions/github-scriptbumped from v6 to v8action.ymlDocker image tag change from v7 to v9 means this is a breaking release boundary — consumers pinned to v7 will not pick up this change until they update their workflow referencesPull Request
Proposed Changes
Readiness Checklist
Author/Contributor
make lintand fix any issues that you have introducedmake testand ensure you have test coverage for the lines you are introducing